Vmware 3d svga


Virtual Machine Graphics Acceleration Deployment Guide

%PDF-1.6 % 1 0 obj > /Metadata 2 0 R /Names 3 0 R /Outlines 4 0 R /Pages 5 0 R /StructTreeRoot 6 0 R /Type /Catalog /ViewerPreferences > >> endobj 7 0 obj > endobj 2 0 obj > stream

  • Virtual Machine Graphics Acceleration Deployment Guide - White Paper: VMware, Inc.
  • VMware, Inc.
  • This white paper explains the various types of virtual machine graphics acceleration available and also provides knowledge around the benefits offered by each technology.
  • endstream endobj 3 0 obj > endobj 4 0 obj > endobj 5 0 obj > endobj 6 0 obj > endobj 8 0 obj 1290 endobj 9 0 obj > endobj 10 0 obj >> endobj 11 0 obj >> endobj 12 0 obj > endobj 13 0 obj > endobj 14 0 obj > endobj 15 0 obj > endobj 16 0 obj > endobj 17 0 obj > /A10 > /Pa10 > /Pa11 > /Pa12 > /Pa13 > /Pa14 > /Pa15 > /Pa16 > /Pa17 > /Pa18 > /Pa19 > /Pa2 > /Pa20 > /Pa21 > /Pa22 > /Pa23 > /Pa25 > /Pa3 > /Pa5 > /Pa6 > /Pa7 > /Pa8 > /Pa9 > >> endobj 18 0 obj > endobj 19 0 obj > endobj 20 0 obj > endobj 21 0 obj > endobj 22 0 obj > endobj 23 0 obj > endobj 24 0 obj > endobj 25 0 obj > endobj 26 0 obj > endobj 27 0 obj >> endobj 28 0 obj > endobj 29 0 obj >> endobj 30 0 obj > /XObject > >> /Rotate 0 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 31 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 4 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 32 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 48 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 33 0 obj > /Font > /ProcSet [/PDF /Text] /Properties > >> /Shading > /XObject > >> /Rotate 0 /StructParents 5 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 34 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 94 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 35 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 95 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 36 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 96 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 37 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 97 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 38 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 100 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 39 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 105 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 40 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 106 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 41 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 107 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 42 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 108 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 43 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 111 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 44 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 112 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 45 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 114 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 46 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 117 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 47 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 118 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 48 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 119 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 49 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 121 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 50 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 122 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 51 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 123 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 52 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 124 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 53 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 125 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 54 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 126 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 55 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 128 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 56 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 130 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 57 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 131 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 58 0 obj > /Font > /ProcSet [/PDF /Text] /XObject > >> /Rotate 0 /StructParents 132 /TrimBox [0.0 0.0 612.0 792.0] /Type /Page >> endobj 59 0 obj > endobj 60 0 obj > endobj 61 0 obj > endobj 62 0 obj > endobj 63 0 obj > endobj 64 0 obj > endobj 65 0 obj >> endobj 66 0 obj > endobj 67 0 obj >> endobj 68 0 obj >> endobj 69 0 obj > stream H*2P0P034R04R(J W*w6PH/w5Pp B

    www.vmware.com

    vmware svga 3d Drivers Download for Windows 7, 8, XP, Vista

    Home  »  vmware svga 3d

    In our share libs contains the list of vmware svga 3d drivers all versions and available for download. To download the proper driver by the version or Device ID.

    If not found in our garage driver you need, please contact us, we will help you in time, and updates to our website.

    All Versions

    Version:

    10.0.10240.16384

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    Version:

    10.0.10547.0

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    Version:

    10.0.10586.0

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    Version:

    10.0.9926.0

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    Version:

    6.0.6001.18000

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows Vista

    Version:

    6.1.7600.16385

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 7

    Version:

    6.2.9200.16384

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows XP

    Version:

    6.3.9369.0

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows XP

    Version:

    6.3.9600.16384

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    Version:

    6.4.9841.0

    Release Date:

    6-21-2006

    Provider:

    Microsoft

    HardwareIDs:

    Supported OS:

    Windows 8

    driverlibs.com

    3D ускорение VDI на практике. Часть 1 / Блог компании ИТ-ГРАД / Хабрахабр

    3D ускорение VDI на практике.
    Часть 1 — vSGA и vDGA

    Отсутствие аппаратного ускорения графики является существенным препятствием при внедрении технологий виртуализации в компаниях, работающих в сфере дизайна, проектирования, конструкторских разработок и пр. Рассмотрим, какие новые возможности появились с выходом NVIDIA GRID.

    Виртуализация рабочих мест (VDI) уже прочно вошла в нашу жизнь, в первую очередь в корпоративном сегменте рынка, и уверенно пробивает путь в остальные сегменты, в том числе и в виде публичных облачных сервисов (Desktop as a Service). Отсутствие же аппаратного ускорения графики сдерживает использование данной технологии в тех отраслях, которые могли бы оценить такие преимущества использования VDI как удаленную доступность, безопасность данных и упрощение аутсорсинга персонала.

    Первые шаги к использованию 3D ускорения в VDI были сделаны достаточно давно и заключались в пробросе PCI устройств в виртуальные машины, что позволяло выдавать для VDI видеокарты, установленные в сервер или подключенные к серверу с помощью внешних PCIe корзин, например, таких как Dell PowerEdge C410x. Недостатки такого решения очевидны — повышенное использование электроэнергии, места в стойках и высокая стоимость.

    Коротко о технологии NVIDIA GRID
    С анонсом технологии NVIDIA GRID (NVIDIA VGX на момент анонса) в прошлом году интерес к использованию 3D ускоренных VDI значительно возрос. Суть технологии GRID, которая исходно предназначена именно для 3D ускорения в виртуальных средах, достаточно проста и включает в себя следующие принципы:
    • Агрегация на базе одной PCIe карты нескольких графических ускорителей;
    • Возможность виртуализации графических ускорителей на уровне гипервизора;
    • Возможность виртуализации графических ускорителей средствами технологии GRID Virtual GPU.
    На данный момент компанией NVIDIA выпущено две видеокарты построенных на базе архитектуры NVIDIA Keppler — NVIDIA GRID K1 и K2. Характеристики данных карт следующие:
                     GRID K1                                                                GRID K2                            
    Число GPU 4 Kepler GPU начального уровня 2 Kepler GPU высокого класса
    Ядра CUDA 768 3072
    Общий размер памяти 16 ГБ DDR3 8 ГБ GDDR5
    Максимальная мощность 130 Вт 225 Вт
    Длина Карты 26,7 см 26,7 см
    Высота Карты 11,2 см 11,2 см
    Ширина Карты Dual Slot Dual Slot
    Отображение

     ввода/вывода данных

    Нет Нет
    Дополнительное питание Разъем 6-pin Разъем 8-pin
    PCIe x16 x16
    Поколение PCIe Gen3 (совместим с Gen2) Gen3 (совместим с Gen2)
    Охлаждение Пассивное Пассивное     
    Технические спецификации Спецификации платы GRID K1 Спецификации платы GRID  K2
    Фактически, GRID K1 представляет собой интегрированные на одной PCIe карте четыре карты уровня QUADRO K600, карты GRID K2 — две карты уровня QUADRO K5000. Это позволяет даже без использования виртуализации существенно увеличить плотность графических адаптеров в серверах.

    Включение в платформу GRID серверов различных вендоров, обеспечивающих установку до 4 карт GRID в один сервер избавляет от необходимости применять внешние PCIe корзины.

    ПО, поддерживающее технологию GRID — это гипервизоры VMware, Citrix и Microsoft, а также системы виртуализации рабочих станций VMware и Citrix (и Microsoft, если рассматривать варианты общего доступа к серверу).

    Описание нашего тестового стенда
    Для нашего тестового стенда мы решили использовать 1U сервер SuperMicro 1027GR-TRFT. Его основные особенности:
    • Dual socket R (LGA 2011) supports Intel® Xeon® processor E5-2600 and E5-2600 v2 family
    • Up to 512GB ECC DDR3, up to 1866MHz; 8x DIMM sockets
    • 3x PCI-E 3.0 x16 slots (support GPU/Xeon Phi cards), 1x PCI-E 3.0 x8 (in x16) low-profile slot
    • Intel® X540 10GBase-T Controller
    • 4x Hot-swap 2.5" SATA3 Drive Bays
    • 1800W Redundant Power Supplies Platinum Level (94%+)
    Такой выбор был обусловлен высокой плотностью (до 3 видеокарт GRID в 1U) и наличию встроенных 10GBase-T сетевых интерфейсов.

    SATA корзина позволяет использовать недорогие SSD диски для Host Based кэширования доступа к данных, столь полезного при VDI нагрузках, с характерными пиками дисковой активности в начале и окончании рабочего дня.

    При современных же ценах на модули памяти восьми DIMM-слотов оказывается вполне достаточно в ситуации, когда плотность VM на сервер ограничивается CPU и GPU ресурсами.

    В данный сервер мы установили карту NVIDIA GRID K1. Приводим фото сервера с готовой к установке видеокартой:

    В качестве платформы виртуализации была выбрана привычная нам VMware vSphere. Забегая вперед, отмечу, что во второй части данной статьи нам придется использовать Citrix XenServer, поскольку на данный момент только он и только в статусе Tech Preview поддерживает технологию GRID Virtual GPU.

    Гипервизор ESXi определяет видеокарту как 4 устройства NVIDIAGRID K1, подключённые через PCI/PCI bridge, что делает ускорители доступными для раздельного использования как passthrough устройства, подключаемые к ВМ, или как основу для виртуализации на уровне гипервизора.

    В гипервизор инсталлируется драйвер от NVIDIA:

    ~ # esxcli software vib list | grep NVIDIANVIDIA-VMware_ESXi_5.1_Host_Driver 304.76-1OEM.510.0.0.802205 NVIDIA VMwareAccepted 2013-03-26

    Все устройства, которые не переведены в режим passthrough, при загрузке инициализируются и используются драйвером от NVIDIA:

    2013-10-28T06:12:42.521Z cpu7:9838)Loading module nvidia ...2013-10-28T06:12:42.535Z cpu7:9838)Elf: 1852: module nvidia has license NVIDIA2013-10-28T06:12:42.692Z cpu7:9838)module heap: Initial heap size: 8388608, max heap size: 684769282013-10-28T06:12:42.692Z cpu7:9838)vmklnx_module_mempool_init: Mempool max 68476928 being used for module: 772013-10-28T06:12:42.693Z cpu7:9838)vmk_MemPoolCreate passed for 2048 pages2013-10-28T06:12:42.693Z cpu7:9838)module heap: using memType 22013-10-28T06:12:42.693Z cpu7:9838)module heap vmklnx_nvidia: creation succeeded. id = 0x4100370000002013-10-28T06:12:42.943Z cpu7:9838)PCI: driver nvidia is looking for devices2013-10-28T06:12:42.943Z cpu7:9838)PCI: driver nvidia claimed device 0000:86:00.02013-10-28T06:12:42.943Z cpu7:9838)PCI: driver nvidia claimed device 0000:87:00.02013-10-28T06:12:42.943Z cpu7:9838)PCI: driver nvidia claimed 2 devicesNVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.76 Sun Jan 13 20:13:01 PST 20132013-10-28T06:12:42.944Z cpu7:9838)Mod: 4485: Initialization of nvidia succeeded with module ID 77.2013-10-28T06:12:42.944Z cpu7:9838)nvidia loaded successfully. После загрузки гипервизора

    В качестве платформы для создания инфраструктуры VDI используется продукт Citrix XenDesktop 7, который в настоящий момент используется и в нашей production инфраструктуре, предоставляющей сервисы VDI для наших заказчиков. На тестовых машинах используется технология HXD 3D Pro, осуществляющая эффективную упаковку и проброс на клиента отрендеренного GPU изображения. Тестовый виртуальный сервер имеет следующую конфигурацию: 4vCPU 2GHz, 8GB RAM, 60GB HDD.

    Тестирование vSGA
    vSGA — это технология VMware, обеспечивающая виртуализацию ресурсов GPU, установленных в сервера под управлением гипервизора VMware ESXi, и последующее использование данных GPU для обеспечения 3D ускорения для виртуальных видеокарты, выданных для виртуального сервера.

    Технология обладает множеством ограничений по производительности и функционалу виртуальных видеокарт, однако позволяет максимизировать плотность виртуальных машин на один GPU.

    Фактически, нам удалось запустить машины с близким к двухкратному превышением количества виртуальной видеопамяти в сравнении с количеством физической видеопамяти на используемых GPU.

    Функциональность виртуальной видеокарты следующая:

    • поддерживаемые API: DirectX 9, OpenGL 2.1
    • максимальный объем видеопамяти: 512MB
    • производительность графического ядра: динамическая, не управляется.
    В случае использование VMware View такую конфигурацию виртуальных машин можно осуществить непосредственно из интерфейса управления View, в нашем же случае для активации аппаратного ускорения для виртуальной видеокарты необходимо произвести два действия:
    1. включить поддержку 3D,
    2. установить размер видеопамяти в свойствах видеокарты в редактировании машины:

    и добавить параметр mks.use3dRenderer = hardware в ее параметры:

    В гостевой ОС такая виртуальная видеокарта определяется как «VMware SVGA 3D». Она отличается от обычной виртуальной видеокарты только объемом памяти и поддержкой аппаратного ускорения вышеперечисленных API.

    Результаты выполнения теста FurMark на такой VDI машине однозначно говорят, что играть на ней не придется (при этом необходимо отметить, что во время тестирования физической видеокартой пользовалась одна виртуальная машина, то есть все вычислительные ресурсы видеокарты, с учетом накладных расходов виртуализации, были доступны тесту):

    С точки зрения AutoCad 2014 возможности видеокарты выглядят следующим образом:

    Enhanced 3D Performance: Available and onSmooth display: Available and offGooch shader: Available and using hardwarePer-pixel lighting: Available and onFull-shadow display: Available and onTexture compression: Available and offAdvanced material effects: Available and onAutodesk driver: Not CertifiedEffect support:Enhanced 3D Performance: AvailableSmooth display: AvailableGooch shader: AvailablePer-pixel lighting: AvailableFull-shadow display: AvailableTexture compression: AvailableAdvanced material effects: Available

    Как видно, формально все параметры аппаратного ускорения поддерживаются драйвером. Предполагается, что проблемы с поддержкой мы можем увидеть только при использовании более тяжелых продуктов, использующих, например, архитектуру CUDA.

    Результаты выполнения теста Cadalyst Benchmark:

    Результаты не впечатляю, однако использовать данное ПО можно, а если большой производительности и работы со сложными моделями не требуется — например, в учебном классе, то высокая плотность и низкая стоимость таких машин может оказаться полезной.

    Тестирование vDGA
    vDGA — это название, используемое VMware для обозначения проброса физической видеокарты в виртуальную машину.

    Фактически, для данной технологии NVIDIA GRID дала одно единственное преимущество — высокую плотность GPU, которая позволяет отказаться от использования внешних PCIe корзин.

    Например, в используемый на тестовом стенде сервер возможно установить три видеокарты NVIDIA GRID K1, что даст нам 12 независимых ускорителей класса QUADRO K600. Это позволяет запустить на сервере 12 виртуальных серверов, что позволяет загрузить мощности сервера, а в зависимости от профиля нагрузки — и дает запас по GPU ресурсам по сравнению с CPU ресурсами.

    Для проброса видеокарты в виртуальный сервер необходимо включить режим passthrough для данного PCIe устройства в конфигурации хоста и добавить PCI устройство в конфигурацию виртуальной машины:

    Также, требуется установить полное резервирование памяти для данной виртуальной машины

    и провести настройку pci hole. На этот счет существуют различные мнения, мы выбрали значения от 1200 до 2200:

    В гостевой ОС в таком случае видеокарта видится полноценным устройство от NVIDIA и требует установки драйверов для семейства видеокарт GRID.

    Результаты FurMark близки к результатам, полученным в тесте vSGA, что говорит об относительной эффективности уровня виртуализации для этого теста:

    При использовании AutoCad 2014 картина следующая:

    Current Effect Status:Enhanced 3D Performance: Available and on Smooth display: Available and offGooch shader: Available and using hardwarePer-pixel lighting: Available and onFull-shadow display: Available and onTexture compression: Available and offAdvanced material effects: Available and onAutodesk driver: Not CertifiedEffect support:Enhanced 3D Performance: AvailableSmooth display: AvailableGooch shader: AvailablePer-pixel lighting: AvailableFull-shadow display: AvailableTexture compression: AvailableAdvanced material effects: Available

    Все возможности также ожидаемо поддерживаются, однако карточка не является сертифицированной. Из серии GRID для AutoCad сертифицирована только K2.

    Результаты выполнения бенчмарка Cadalyst 2012:

    Как мы видим, проброшенная видеокарта показывает фактически результаты в 4 раза большие, чем виртуализированная. В данном случае, использовать для работы проектировщика такую машину уже возможно.

    Если же производительности карты K1 не достаточно, можно установить K2 и получить top range видеокарту внутри виртуального сервера.

    Во второй части статьи

    Мы подробно расскажем о возможности виртуализации GPU посредством технологий NVIDIA, которые обещают нам поддержку всех доступных физической карте API и производительность, достаточную для уверенной работы с CAD, покажем тестовый стенд, замеры производительности таких видеокарт и подведем итоги. Продолжение следует.

    habrahabr.ru

    Fix the Windows 10 VMware SVGA 3D Compatibility Issue

    With Windows 10, Microsoft aims to make it as easy as possible — perhaps too easy — for Windows 7 and 8 users to upgrade. But some users who attempt to upgrade their Windows 7 and 8 virtual machines in VMware Workstation and Fusion may encounter a problem when using the “Get Windows 10” app, with the app informing users that their virtual “PC” doesn’t meet the minimum technical specifications for Microsoft’s latest operating system.

    Specifically, users are informed that their VMware SVGA 3D virtual graphics hardware isn’t compatible with Windows 10. Thankfully, this isn’t actually the case, as Windows 10 runs just fine in a VMware-based virtual machine, but in order to successfully update your Windows 7 or 8 VM to Windows 10, you’ll need to take a different route from the much-maligned Get Windows 10 app in order to bypass this arbitrary compatibility check. Here’s how to do it.

    First, from within your Windows 7 or 8 virtual machine, head over to the Windows 10 download page. Look under the section labeled “Need to create a USB, DVD or ISO?” and click Download Tool Now.

    This will download the Windows 10 Media Creation Tool, which is a utility that allows you to download the complete set of Windows 10 installation files and then choose to either initiate and upgrade directly on the same system, or create a bootable USB or DVD to install Windows 10 on another system.

    If you want to upgrade other PCs to Windows 10 in addition to your VMware virtual machine, or if you want to have a Windows 10 USB installer on hand for performing clean installs on new hardware, run the Media Creation Tool and select “Create installation media for another PC.” If, however, you’re just interested in getting your current VM to upgrade, click “Upgrade this PC now” and click Next.

    The Media Creation Tool will begin to download the required files to upgrade your current version of Windows 7 or 8 to the corresponding version of Windows 10. The tool must download installation files which are about 3GB in size, so this process may take some time depending on the speed of your Internet connection and the current load on Microsoft’s servers.

    Once the download is complete, choose what you would like to keep after the upgrade — your files and apps, just your files, or nothing (i.e., a fresh install) — and complete the process. Windows 10 should install without issuing a compatibility warning about your VMware SVGA 3D virtual display hardware.

    After the installation is complete, be sure to re-install VMware Tools to ensure the best performance and stability of your virtual machine.

    Want news and tips from TekRevue delivered directly to your inbox? Sign up for the TekRevue Weekly Digest using the box below. Get tips, reviews, news, and giveaways reserved exclusively for subscribers.

    www.tekrevue.com

    VMware Workstation unrecoverable error: (svga) |VMware Communities

    Firstly, thanks a million for such a helpful reply.

     

    You are right that my system has two video cards, and the default graphics card is not the nVidia card; it's an Intel HD 4600.I have been using the nVidia Control Panel to associate the nVidia Quadro card with the vmware-vmx.exe process and to that end, specifying the hardware vendor in the *.vmx did not help, since it seems that part of things was already working correctly.

     

    I spent quite a bit of time investigating the effects of using the options you suggested and ran a series of tests using both the Intel HD 4600 and nVidia Quadro cards and also using Workstation hardware v10 and v12. To reduce the number of combinations of settings I stuck to testing using a Windows 7 x64 guest.

     

    The executive summary of said tests is that your option #2 (mks.enableGLRenderer = "TRUE") was the most successful. I still encounter some issues with it (detailed below) and the performance is still pretty ordinary (not a huge amount better than running with software rendering alone), but it is WAY better than the performance I was seeing with 3D enabled and HW v10 and also avoids the crash when using HW v12. So for both of these things I am really thankful. (Oh, and since I didn't mention it, my SVGA 3D driver was up to date in all guests).

     

    In case you are interested in the full details, also for any other interested reader, these are the main tests that I performed (I have left out tests that went off the beaten track or don't add any significant value to this response), with notable differences in input and outcome highlighted.

     

    The constants in this set of tests are:

    Guest: Windows 7 x64

    SVGA 3D Driver: 8.15.1.50

    Host: Win 8.1 x64 with Intel HD 4600 and nVidia Quadro K2100M

    Workstation version: 12.5.7

     

    Test#1

    HW10 (hardware version 10)

    mks.enable3d = "FALSE"

    (all other mks entries removed)

    No nVidia GPU activity (recorded by host)

    Display in OpenGL app looks good, which is contrary to what I have been used to in the past (using 3D rendering generally results in some rendering issues). Performance is slow, but usable. Better performance than the experience that lead me to post the original post.

     

    Test#2

    HW10

    mks.enable3d = "TRUE"

    (all other mks entries removed)

    Host records activity on the nVidia GPU

    Display in OpenGL app is characteristic of problems with 3D rendering in a VM. Certain presentation features do not work properly. Performance is back to very poor (worse than software rendering). This is the problem that I was running into and that which prompted me to try HW v12 as a potential solution. I do not recall Workstation 11.1.x having such poor 3D performance.

     

    Test#3

    HW12

    mks.enable3d = "TRUE"

    (all other entries removed)

    Host records activity on the nVidia GPU

    Application crashes as per original post. VMware Workstation unrecoverable error: (svga) -- DETECTED D3D11 DEVICE REMOVAL --

        nVidia display driver crashes (and recovers) on host.

    This is the problem that prompted the original post.

     

    Test#4

    HW12 (repeat test, but using different OpenGL application start up approach** that avoids the crash)

    mks.enable3d = "TRUE"

    (all other entries removed)

    Host records activity on the nVidia GPU

    Display in OpenGL app is characteristic of problems with 3D rendering in a VM. Certain presentation features do not work properly. Performance is worse than with HW10. It's unusable.

    ** (In testing different things I found that a particular set of steps when running the OpenGL application could avoid the crash when using HW v12).

     

    Test#5

    HW12 (using Intel HD 4600)

    mks.enable3d = "TRUE"

    mks.enableGLBasicRenderer = "FALSE"     (added since I was tinkering with this setting at one point; ensured that it's disabled).

    mks.enableGLRenderer = "TRUE"

    mks.enableDX11Renderer = "FALSE"

    mks.enableD3DRenderer = "FALSE"

    Host records no activity on the nVidia GPU.

    Application openGL pane draws completely black.

    Application possesses other graphical artefacts (e.g., in WPF UI).

    Log file contains:

    2017-08-21T14:04:41.440+09:30| mks| I125: GLHostWin32: : Created context with GL 2.1, core: 0, robust: 0

    2017-08-21T14:04:41.456+09:30| mks| I125: GLHostWin32: : Created context with GL 4.0, core: 0, robust: 1

    2017-08-21T14:04:41.456+09:30| mks| I125: OpenGL Version: "4.0.0 - Build 10.18.14.4414" (4.0.0)

    2017-08-21T14:04:41.456+09:30| mks| I125: GLSL Version: "4.00 - Build 10.18.14.4414" (4.0.0)

    2017-08-21T14:04:41.456+09:30| mks| I125: OpenGL Vendor: "Intel"

    2017-08-21T14:04:41.456+09:30| mks| I125: OpenGL Renderer: "Intel(R) HD Graphics 4600"

         ...later the log file fills up with this line over and over

    2017-08-21T14:05:52.058+09:30| svga| W115: GLShader: No vertex shader bound.

    If I repeat the above test (say test 5a), but use the same work around (different application start up process) that avoids the crash when not using the GLRenderer, the application does draw correctly. Performance is better, but still significantly well below that when compared to running directly on the host.

     

    Test#6

    HW12 (using nVidia)

    mks.enable3d = "TRUE"

    mks.enableGLBasicRenderer = "FALSE"

    mks.enableGLRenderer = "TRUE"

    mks.enableDX11Renderer = "FALSE"

    mks.enableD3DRenderer = "FALSE"

    Host records activity on the nVidia GPU.

    Application draws completely black.

    Vmware log contains:

    2017-08-21T13:51:14.431+09:30| mks| I125: GLHostWin32: : Created context with GL 2.1, core: 0, robust: 0

    2017-08-21T13:51:14.465+09:30| mks| I125: GLHostWin32: : Created context with GL 4.0, core: 0, robust: 1

    2017-08-21T13:51:14.465+09:30| mks| I125: OpenGL Version: "4.5.0 NVIDIA 382.05" (4.5.0)

    2017-08-21T13:51:14.465+09:30| mks| I125: GLSL Version: "4.50 NVIDIA" (4.50.0)

    2017-08-21T13:51:14.465+09:30| mks| I125: OpenGL Vendor: "NVIDIA Corporation"

    2017-08-21T13:51:14.465+09:30| mks| I125: OpenGL Renderer: "Quadro K2100M/PCIe/SSE2"

         ...later the log file fills up with this line over and over

    2017-08-21T13:53:00.567+09:30| svga| W115: GLShader: No vertex shader bound.

    If I repeat the above test (say test 6a), but use the same work around (different application start up process) that avoids the crash when not using the GLRenderer, the application does draw correctly. Performance is better again (best of all tests), but still significantly well below that when compared to running directly on the host. This restores the performance to something like I remember it used to be on previous Workstation versions (though I admit that I can only provide anecdotal evidence on that without going back to Workstation 1.11.x and doing more tests, which is something I really don't want to do for now).

     

    Using the configuration from Test6 (and the OpenGL application work around), this is becomes workable, since the crash no longer occurs and the performance is restored to something usable. If I forget to apply the steps to get the OpenGL app to draw correctly it's just a few mouse clicks without even needing to close the application to rectify this. So, for me this is a good enough work around and gets me trucking once again!

     

    Finally, I tried these "best" settings using a Windows 10 guest and get very similar results with the exception that I notice some graphical artefacts in some additional portions of the application that I am testing. These are only minor issues, but a noticeable difference between Windows 7 and Windows 10.

    communities.vmware.com

    VMware guest GL driver

    This page describes how to build, install and use the VMware guest GL driver (aka the SVGA or SVGA3D driver) for Linux using the latest source code. This driver gives a Linux virtual machine access to the host's GPU for hardware-accelerated 3D. VMware Workstation running on Linux or Windows and VMware Fusion running on MacOS are all supported.

    With the August 2015 Workstation 12 / Fusion 8 releases, OpenGL 3.3 is supported in the guest. This requires:

    • The VM is configured for virtual hardware version 12.
    • The host OS, GPU and graphics driver supports DX11 (Windows) or OpenGL 4.0 (Linux, Mac)
    • On Linux, the vmwgfx kernel module must be version 2.9.0 or later.
    • A recent version of Mesa with the updated svga gallium driver.

    Otherwise, OpenGL 2.1 is supported.

    OpenGL 3.3 support can be disabled by setting the environment variable SVGA_VGPU10=0. You will then have OpenGL 2.1 support. This may be useful to work around application bugs (such as incorrect use of the OpenGL 3.x core profile).

    Most modern Linux distros include the SVGA3D driver so end users shouldn't be concerned with this information. But if your distro lacks the driver or you want to update to the latest code these instructions explain what to do.

    For more information about the X components see these wiki pages at x.org:

    Components

    The components involved in this include:
    • Linux kernel module: vmwgfx
    • X server 2D driver: xf86-video-vmware
    • User-space libdrm library
    • Mesa/gallium OpenGL driver: "svga"

    All of these components reside in the guest Linux virtual machine. On the host, all you're doing is running VMware Workstation or Fusion.

    Prerequisites

    • Kernel version at least 2.6.25
    • Xserver version at least 1.7
    • Ubuntu: For ubuntu you need to install a number of build dependencies. sudo apt-get install git-core sudo apt-get install automake libtool libpthread-stubs0-dev sudo apt-get install xserver-xorg-dev x11proto-xinerama-dev libx11-xcb-dev sudo apt-get install libxcb-glx0-dev libxrender-dev sudo apt-get build-dep libgl1-mesa-dri libxcb-glx0-dev
    • Fedora: For Fedora you also need to install a number of build dependencies. sudo yum install mesa-libGL-devel xorg-x11-server-devel xorg-x11-util-macros sudo yum install libXrender-devel.i686 sudo yum install automake gcc libtool expat-devel kernel-devel git-core sudo yum install makedepend flex bison

    Depending on your Linux distro, other packages may be needed. The configure scripts should tell you what's missing.

    Getting the Latest Source Code

    Begin by saving your current directory location: export TOP=$PWD
    • Mesa/Gallium master branch. This code is used to build libGL, and the direct rendering svga driver for libGL, vmwgfx_dri.so, and the X acceleration library libxatracker.so.x.x.x. git clone git://anongit.freedesktop.org/git/mesa/mesa
    • VMware Linux guest kernel module. Note that this repo contains the complete DRM and TTM code. The vmware-specific driver is really only the files prefixed with vmwgfx. git clone git://anongit.freedesktop.org/git/mesa/vmwgfx
    • libdrm, a user-space library that interfaces with drm. Most distros ship with this but it's safest to install a newer version. To get the latest code from git: git clone git://anongit.freedesktop.org/git/mesa/drm
    • xf86-video-vmware. The chainloading driver, vmware_drv.so, the legacy driver vmwlegacy_drv.so, and the vmwgfx driver vmwgfx_drv.so. git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-vmware

    Building the Code

    • Determine where the GL-related libraries reside on your system and set the LIBDIR environment variable accordingly.

      For 32-bit Ubuntu systems:

      export LIBDIR=/usr/lib/i386-linux-gnu For 64-bit Ubuntu systems: export LIBDIR=/usr/lib/x86_64-linux-gnu For 32-bit Fedora systems: export LIBDIR=/usr/lib For 64-bit Fedora systems: export LIBDIR=/usr/lib64
    • Build libdrm: cd $TOP/drm ./autogen.sh --prefix=/usr --libdir=${LIBDIR} make sudo make install
    • Build Mesa and the vmwgfx_dri.so driver, the vmwgfx_drv.so xorg driver, the X acceleration library libxatracker. The vmwgfx_dri.so is used by the OpenGL libraries during direct rendering, and by the Xorg server during accelerated indirect GL rendering. The libxatracker library is used exclusively by the X server to do render, copy and video acceleration: The following configure options doesn't build the EGL system. cd $TOP/mesa ./autogen.sh --prefix=/usr --libdir=${LIBDIR} --with-gallium-drivers=svga --with-dri-drivers=swrast --enable-xa --disable-dri3 --enable-glx-tls make sudo make install Note that you may have to install other packages that Mesa depends upon if they're not installed in your system. You should be told what's missing.
    • xf86-video-vmware: Now, once libxatracker is installed, we proceed with building and replacing the current Xorg driver. First check if your system is 32- or 64-bit. cd $TOP/xf86-video-vmware ./autogen.sh --prefix=/usr --libdir=${LIBDIR} make sudo make install
    • vmwgfx kernel module. First make sure that any old version of this kernel module is removed from the system by issuing sudo rm /lib/modules/`uname -r`/kernel/drivers/gpu/drm/vmwgfx.ko* Build and install: cd $TOP/vmwgfx make sudo make install sudo depmod -a If you're using a Ubuntu OS: sudo update-initramfs -u If you're using a Fedora OS: sudo dracut --force Add 'vmwgfx' to the /etc/modules file: echo vmwgfx | sudo tee -a /etc/modules Note: some distros put DRM kernel drivers in different directories. For example, sometimes vmwgfx.ko might be found in /lib/modules/{version}/extra/vmwgfx.ko or in /lib/modules/{version}/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko.

      After installing vmwgfx.ko you might want to run the following command to check that the new kernel module is in the expected place:

      find /lib/modules -name vmwgfx.ko -exec ls -l '{}' \; If you see the kernel module listed in more than one place, you may need to move things around.

      Finally, if you update your kernel you'll probably have to rebuild and reinstall the vmwgfx.ko module again.

    Now try to load the kernel module by issuing sudo modprobe vmwgfx Then type dmesg to watch the debug output. It should contain a number of lines prefixed with "[vmwgfx]".

    Then restart the Xserver (or reboot). The lines starting with "vmwlegacy" or "VMWARE" in the file /var/log/Xorg.0.log should now have been replaced with lines starting with "vmwgfx", indicating that the new Xorg driver is in use.

    Running OpenGL Programs

    In a shell, run 'glxinfo' and look for the following to verify that the driver is working:

    OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE; OpenGL version string: 2.1 Mesa 8.0

    If you don't see this, try setting this environment variable:

    export LIBGL_DEBUG=verbose

    then rerun glxinfo and examine the output for error messages.

    If OpenGL 3.3 is not working (you only get OpenGL 2.1):

    • Make sure the VM uses hardware version 12.
    • Make sure the vmwgfx kernel module is version 2.9.0 or later.
    • Check the vmware.log file for errors.
    • Run 'dmesg | grep vmwgfx' and look for "DX: yes".

    www.mesa3d.org

    VMware SVGA 3D (Microsoft Corporation - WDDM)

    DOWNLOAD NOW Driver updating utility for official VMware hardware drivers (Free Scan).

    New Windows Version?Upgrade Smoothly!

    Driver Genius will automatically scan and find the official VMware SVGA 3D (Microsoft Corporation - WDDM) driver matching your needs - no matter what windows version you're using. Now you can finally use the same driver update tools used by PC technicians and eliminate any guess work and time waste in the process of updating your drivers. No more headache and no more countless hours looking for help in hardware manufacturer sites.

    The 1 mistake you don't want to be making

    Caution: in order to prevent hard drive crashes, device driver conflicts and fatal error messages - you should make sure the VMware SVGA 3D (Microsoft Corporation - WDDM) driver you install on your system - is the proper driver matching your hardware needs.

    To download the correct VMware SVGA 3D (Microsoft Corporation - WDDM) driver matching your hardware - we strongly recommend using a reputable driver update utility such as Driver Genius which can instantly scan your system and detect any hardware device you've installed, while matching each of them with the most current official manufacturer driver.

    This automatic update tool will let you run a free scan, while listing all drivers found to be missing or out of date (not only the missing VMware SVGA 3D (Microsoft Corporation - WDDM) driver you are currently worried about). Next - it will instantly locate the proper VMware SVGA 3D (Microsoft Corporation - WDDM) hardware driver, and any other driver you need, download and install it onto your system - giving you optimum performance & speed. This entire process takes under 2 minutes.

    Why should I keep my drivers up-to-date?

    Usually, we only bother ourselves with updating our system's device drivers - only when something wrong happens, stops working, not responding etc etc... but although it may sound like a reasonable behavior, in reality - making sure all our device drivers are always up-to-date also guarantees that we really make the most out of our system's hardware devices

    You should know that hardware companies are always in the run for new technologies, upgrades and refining of their devices' performance and you will not be able to enjoy the full power potential of the hardware you once bought - unless you make sure all your drivers are being updated on a regular basis. Now if you're the kind of geek that's willing to spend hours upon hours, sifting through bad-looking and not-so-user-friendly manufacturer sites, trying to make sure your system's device drivers are always up to date - well good luck! But if you're the kind of person that wants peace of mind and really cares for his time - then using a driver update software like Driver Genius can really make the entire process a breeze, as with just little effort on your side (a few clicks here and there) - in a matter of minutes all your hardware devices will now start working at their optimum level of performance. Sometimes, you may find that although certain devices you installed are working just fine by themselves - they are not responding so well when they interact with other hardware devices. The reason for that may well be that the other device's drivers are not quite up-to-date. Problems like these arise quite often and are also another reason why many people find using an automatic update tool like Driver Genius - as very effective. Since it constantly monitors all device drivers in your system and updates them on a regular basis - you can keep enjoying the full potential of your entire system, as it keeps running smoothly even when you upgrade, remove or change any of it's hardware components.

    DOWNLOAD NOW - driver updater tool

    To download Driver Genius simply click the green "Download Now" button above or click here.

    Driver Genius automatically updates:

    • AC97 drivers
    • Bios Drivers
    • Bluetooth Drivers
    • Camera Drivers
    • Card Reader Drivers
    • CD & DVD Drivers
    • Chipset Drivers
    • Ethernet Drivers
    • FireWire Drivers
    • Network Drivers
    • Printer Drivers
    • Router Drivers
    • SCSI Drivers
    • Sound & Audio Drivers
    • Scanner Drivers
    • Storage Drivers
    • USB drivers
    • Video card Drivers
    • Webcam Drivers
    • Wireless Drivers
    • Game Controller Drivers
    • IDE Drivers
    • Input Drivers
    • Modem Drivers
    • Monitor Drivers
    • Motherboard Drivers
    • Windows XP Drivers
    • Windows Vista Drivers
    • Windows 2007 Drivers

    Bottom line - why should I use Driver Genius for updating my system's drivers?

    Most accurate and thorough scan around

    One of the smoothest running driver updater programs we have come across - Driver Genius really learns and gets to "KNOW" your system's needs before it decides on the proper drivers to install on your system. Driver Genius scans your machine and looks up more than 30,000 official manufacturer drivers to find the matching and most updated driver for your specific device needs matching your current windows version. Rather than having to guess and waste countless hours looking for the proper drivers to match a device with an unknown serial number - or having to deal with devices that can't be recognized by your OS - Driver Genius will do all that tedious work for you in under 2 min.

    2009 & 2010 award winning software

    Regardless of our own rigorous testing, after doing a thorough research and looking all over the web for the most recommended driver updating utilities, It seems that we weren't the only ones to give this software by the Avanquest team - a whooping 5 star rating. Brands like: GeekFiles, Softpedia, Tucows, Onekit, BumperSoft, SubmitFile and many others - gave Driver Genius an impressive 5/5 star rating - leaving dust to many other veteran tools available on the market. Moreover - more and more IT managers and PC technicians reported that by using this software on a daily basis - they are able to slash their working time and be much more productive. If it's good enough for these guys - it's good enough for you!

    Very fast and easy to use!

    Driver Genius is one of those programs that even your grandma could manage with. Very simple 1-2-3 process. No technical skills needed what so ever. Nothing to think about. Just point-click a few times and process is over. You can also set up the software to run on autopilot every week or so and thus make sure that your drivers are always up-to-date, even without your intervention.

    Get only official drivers - Spyware & Malware free
    Driver Genius downloads all drivers directly from the original manufacturer's website and not from any other dubious source - so you are always sure to get the most up-to-date original driver. This process prevents you from accidently downloading spyware or other potentially malicious software that can severely endanger your system.
    Step 1: Initial System Scan

    After you download the software and allow it to run, Driver Genius will first assess your PC's hardware devices, type, age, important identifiable information about any device checked, and also the current drivers installed on your machine, their relevancy and accuracy and it will scan and pinpoint all the missing and outdated drivers in your system. This entire process usually takes between 1-2 minutes.

       
    Step 2: Detailed Scan Report

    At this second phase of the process, Driver Genius will let you know the results of the initial scan, listing all missing and outdated drivers that needs to be corrected, and will ask your permission to automatically fix the situation and fetch the correct and updated versions of the drivers your system needs - right from the official manufacturer's websites.

       
    Step 3: Driver Download and installation

    After you clicked "GET DRIVERS" - the program will then start actively searching and updating your system with all the correct official drivers needed for your system. Just sit and watch your system as it comes back to life - This final process is very fast (Usually under 30 sec).

    Q: How safe is it to use these driver updating utilities?

    A: If you use a reputable and well rated tool like Driver Genius, Driver Reviver and some other reputable tools out there - you have nothing to worry about. We personally checked Driver Genius and found it to be 100% clean of any virus, malware, spyware or any other malicious software. Since the drivers come straight from the manufacturer - you remain on the safe side.

    Q: What happens if I want to restore my older drivers?

    A: No Problem. Driver Genius lets you back up all your current drivers (for any future use) and also create a system restore point before you install new drivers, so you get to enjoy the best of both worlds - updated system and backup of older files. Reinstalled your operating system? with just a few clicks all your older drivers will get back to action. Moreover, Driver Genius keeps a log of all your driver update history, so if you ever need to look back on things for any given reason - there really is no problem.

    Q: What OS is the software compatible with?

    A: Windows XP, Windows XP 64-bit, Windows Vista 32-bit, Windows Vista 64-bit, Windows 7 32-bit, Windows 7 64-bit, Windows Server 2003, Windows Server 2003 64-bit, Windows Server 2008, Windows Server 2008 64-bit.

    Q: Can the software run by itself every so often?

    A: Yep. Driver Genius really made it easy with it's driver scan scheduler, so that you can use it to set up daily, weekly and monthly autopilot scans - set and forget, ensuring you always have the most recent drivers installed, even without your active intervention.

    Q: Can the software really find any driver out there?

    A: No. As every other software - don't expect automatic applications to find 100% of the drivers out there. From what we tested and compared, Driver Genius proved to be very effective in finding all types of drivers, even for very old peripherals, but you still have to expect that sometimes these driver update tools will not find the specific driver you where looking for.

    Installing Driver Genius on your PC

    Installing driver genius on your PC is a very simple process ans is 100% reversible if you'll want to uninstall at a later date. Just follow these steps and you're all set: 1) Click on the following link: Driver Genius (executable, 6.5MB), then click "Run" and wait until the setup file is finished downloading. 2) Follow the installation instructions in the "welcome" window, agree to the "End User Agreement", click "Next" a few times and wait for the installation process to finished. 3) After the installation process is finished - Driver Genius will ask your permission to start scanning your system for missing and outdated drivers. Click "OK", let the software do what it knows best and go get some coffee -

    Removing Driver Genius from your PC

    If for any reason you decided that you want to uninstall Driver Genius and completely remove it from your PC - it is very easy to do so and should take no more than 40 seconds. Here is how to do it: Click the "Start" menu, go to "All Programs" and find the folder named "Driver Genius". Then you will notice a label that's called "Uninstall". Simply click it and the un-installation process will immediately begin. It will take no more than a minute or so and Driver Genius will become history and will be 100% removed from your machine, as if it was never there.

    driversfinder.net


    Смотрите также