[
https://issues.apache.org/jira/browse/CLOUDSTACK-9211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109341#comment-15109341
]
ASF GitHub Bot commented on CLOUDSTACK-9211:
--------------------------------------------
Github user nvazquez commented on the pull request:
https://github.com/apache/cloudstack/pull/1310#issuecomment-173350754
Thanks @cristofolini
I've tryied writing a marvin test for testing this feature which would be:
* Select (or create) a vm (id=XXXX) which is already running and stop it.
* For vm with id=XXXX do the following:
<code>INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES
('XXXX', 'mks.enable3d', 'true');</code>
<code>INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES
('XXXX', 'mks.use3dRenderer', 'automatic');</code>
<code>INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES
('XXXX', 'svga.autodetect', 'false');</code>
<code>INSERT INTO cloud.user_vm_details (vm_id, name, value) VALUES
('XXXX', 'svga.vramSize', 'ZZZZ');</code>
</code>
Where <code>ZZZZ</code> is the ram size in KB
* Start vm XXXX again
In previous behaviour, it all worked except vram size, which was always set
to 64MB, ignoring size <code>ZZZZ</code> provided. With this fix, vram size is
set to <code>ZZZZ</code> when provided.
I couldn't be able to write a marvin test which follows these steps,
however I wrote a unit test for this new method, which is only accessed through
<code>execute(StartCommand)</code> method.
Nicolas
> Support passing vRAM size over to Esxi hypervisor to support 3D GPU on Vmware
> -----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9211
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9211
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.8.0
> Reporter: Nicolas Vazquez
> Fix For: 4.8.0
>
>
> CS support passing hypervisor options by creating entries in
> {{vm_template_details}} or {{user_vm_details}}
> To enable software 3D GPU 4 options needs to be added:
> ||name||value||
> |mks.enable3d|true|
> |mks.use3dRenderer|automatic|
> |svga.autodetect|false|
> |svga.vramSize|(size in KB) e.g. 131072|
> Currently all options except {{svga.vramSize}} works, VMs always get
> configured with default 64Mb videoRAM instead of the one provided on the
> option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
