Hide Forgot
Created attachment 484779 [details] VM log & vdsm log Description of problem: When using spice console, qemu process is run with parameter -global qxl-vga.vram_size=67108864 which is considered as invalid option and due to this parameter VM won't start Version-Release number of selected component (if applicable): qemu-kvm-0.12.1.2-2.150.el6.x86_64 vdsm-4.9-53.el6.x86_64 libvirt-0.8.7-11.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a new VM (in my case RHEL 6 x64, with virtio disk) 2. Set console as Spice 3. Run VM Actual results: run fails due to bad qemu parameters Expected results: VM is running Additional info: vnc works critical parameters qemu is run with: -vga qxl -global qxl-vga.vram_size=67108864 Parameters passed from vdsm: <model heads="1" type="qxl" vram="65536"/> </video> <channel type="spicevmc"> <target name="com.redhat.spice.0" type="virtio"/> </channel> <graphics autoport="yes" keymap="en-us" listen="0" passwd="*****" passwdValidTo="1970-01-01T00:00:01" port="-1" tlsPort="-1" type="spice"> <channel mode="secure" name="main"/> <channel mode="secure" name="inputs"/> </graphics> VM log and vdsm log is attached
Looks like VDSM should ask libvirt for vram=64 (as libvirt translates it from megs to bytes).
Lovely. Is this an intended change in libvirt-0.8.7-11?
Dan, I don't believe that's intentional. We do not change the units of the XML fields. Assuming that's the case, it will be fixed along with https://bugzilla.redhat.com/show_bug.cgi?id=673578#c18 in -12.
(In reply to comment #6) > Dan, I don't believe that's intentional. We do not change the units of the XML > fields. Assuming that's the case, it will be fixed along with > https://bugzilla.redhat.com/show_bug.cgi?id=673578#c18 in -12. Cool. If vram= attribute is to be specified in KiB as it used to, there's nothing for vdsm to do here. *** This bug has been marked as a duplicate of bug 673578 ***
(In reply to comment #7) > (In reply to comment #6) > > Dan, I don't believe that's intentional. We do not change the units of the XML > > fields. Assuming that's the case, it will be fixed along with > > https://bugzilla.redhat.com/show_bug.cgi?id=673578#c18 in -12. > > Cool. If vram= attribute is to be specified in KiB as it used to, there's > nothing for vdsm to do here. Actually, the field *is* in KiB, and this bug is precisely a dup of 673578; qemu isn't barfing on the value (67108864 / 1024 = 65536, which is what was specified in the XML) it's barfing on the mangling of the field name, which is verified in -12 now and you should be good to go.
vram is documented as being in KiB at: http://libvirt.org/formatdomain.html#elementsVideo