2:03 a.m.
Hi Liran,
On 11/23/21 17:16, Liran Rotenberg wrote:
On Tue, Nov 23, 2021 at 2:36 PM Laszlo Ersek
<lersek(a)redhat.com>
wrote:
> Based on feedback from Liran and Arik, here:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1976607#c3
> https://bugzilla.redhat.com/show_bug.cgi?id=1976607#c4
>
> I should use
>
> <Device>vga</Device>
>
> not
>
> <rasd:Device>vga</rasd:Device>
>
> and then ovirt-engine already has code to handle that.
>
> Liran: in comment 3 on the above BZ, you provide the snippet
>
> <Item>
> <rasd:Caption>Graphical Controller</rasd:Caption>
>
<rasd:InstanceID>2834786b-e9d0-4419-8e6a-c4843fed2f9c</rasd:InstanceID>
> <rasd:ResourceType>32768</rasd:ResourceType>
> <rasd:VirtualQuantity>1</rasd:VirtualQuantity>
> <rasd:SinglePciQxl>false</rasd:SinglePciQxl>
> <Type>video</Type>
> <Device>vga</Device>
> <rasd:Address></rasd:Address>
> <BootOrder>0</BootOrder>
> <IsPlugged>true</IsPlugged>
> <IsReadOnly>false</IsReadOnly>
> <Alias></Alias>
> <SpecParams>
> <vram>16384</vram>
> </SpecParams>
> </Item>
>
> From these, virt-v2v does not provide the following at all:
> - rasd:SinglePciQxl
> - rasd:Address
> - BootOrder
> - IsPlugged
> - IsReadOnly
> - Alias
> - SpecParams (with child node "vram")
>
> Are any of these required, in addition to <Device>vga</Device>?
>
It will auto set some of the values on import.
For being extra careful I checked a VM that I exported omitting these
values from the VGA item and it got imported back well(+ran).
This was the snippet for the device:
<Item>
<rasd:Caption>Graphical Controller</rasd:Caption>
<rasd:InstanceID>2834786b-e9d0-4419-8e6a-c4843fed2f9c</rasd:InstanceID>
<rasd:ResourceType>32768</rasd:ResourceType>
<rasd:VirtualQuantity>1</rasd:VirtualQuantity>
<Type>video</Type>
<Device>vga</Device>
</Item>
this XML fragment doesn't seem to have the intended effect. After I
updated this patch as discussed:
https://bugzilla.redhat.com/show_bug.cgi?id=1961107#c33
<Item>
<rasd:Caption>Graphical Controller</rasd:Caption>
<rasd:InstanceId>10bc4924-6875-4c18-89d3-8263d589abd1</rasd:InstanceId>
<rasd:ResourceType>32768</rasd:ResourceType>
<Type>video</Type>
<rasd:VirtualQuantity>1</rasd:VirtualQuantity>
<Device>vga</Device>
</Item>
Ming Xie tested it, with rhv-4.4, and the following error was reported:
https://bugzilla.redhat.com/show_bug.cgi?id=1961107#c32
-->
1.2 Check guest on rhv after v2v conversion, found video type of
guest still shows qxl on rhv4.4, try to power on guest but guest
can't power on with error "VM esx7.0-rhel8.5-x86_64 is down with
error.
Exit message: unsupported configuration: ram attribute only
supported for video type qxl."
1.3 Check the video type of guest in vdsm.log, the video type is
vga, so need to fix the ram attribute problem for vga type
<video>
<model type="vga" vram="32768" heads="1"
ram="65536" vgamem="16384"></model>
<alias
name="ua-67a23513-ff93-4663-bae8-5330116642b9"></alias>
</video>
This patch (after the update) does not generate any video RAM related
attributes, so I think those must be ovirt-engine defaults.
For reference, the libvirt patch in this series ("output: handle
Standard_VGA in the libvirt XML and QEMU cmdline formats") generates the
following libvirt XML, for the libvirt output mode:
<video>
<model type='vga' vram='16384' heads='1'/>
</video>
(It was successfully tested by Ming Xie in
<https://bugzilla.redhat.com/show_bug.cgi?id=1961107#c24>.)
Thanks,
Laszlo