Red Hat Bugzilla – Bug 211928
No way to specific VNC graphics & use a bootloader in SEXPR protocol
Last modified: 2007-11-30 17:07:35 EST
Description of problem:
The VNC graphics configuration option for paravirt guests is within the (image
(linux ...)) part of the SEXPR given to XenD. When creating guests using an
explicit kernel & initrd, this works fine. If using a bootloader such as pygrub
though, there is no (image) block specified at all, instead a (bootloader ...)
block is used. If one specifies both a (bootloader) and (image) block, XenD will
only look at the (image) block and thus not run the bootloader. This makes it
impossible to create a guest domain using VNC & a bootloader from libvirt.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Feed a piece of SEXPR data to XenD such as
(image (linux (vnc 1)))
(device (vbd (dev 'xvda')(uname 'phy:/dev/HostVG/XenGuest1')(mode 'w')))
(device (vif (mac '00:16:3e:1e:7c:a6')(bridge 'xenbr0')(script 'vif-bridge')))
Xend complains about missing kernel & refuses to create the domain
Xend runs the bootloader to extract the kernel & creates a domain with VNC active
Created attachment 139264 [details]
Make VNC graphics & bootloader play nice
This patch makes xend use the bootloader in cases where an (image...) block is
set but with no (kernel) nested-block. This allows VNC to play nice with
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release. Product Management has requested further review
of this request by Red Hat Engineering. This request is not yet committed for
inclusion in release.
Witholding QE ack until we get resolution on the inactive domain management.
And on that note, I thought we were feature complete.
The new generation paravirt framebuffer patches included in recent RHEL-5 xen
packages completely changed the config file format. As such the problem
described in this bug no longer exists.