Xen tools can be built with the XENFB_TOOLS=y option (e.g. XENFB_TOOLS=y make tools) to build the /usr/lib/xen/bin/xen-vncfb binary, which is responsible for setting up VNC listeners to paravirtualized domU's (virtual machines). Unfortunately, the app-emulation/xen-tools-3.1.2 does not support this ability at this time. Reproducible: Always Steps to Reproduce: 1. Emerge app-emulation/xen-tools-3.1.2 2. Look for /usr/lib/xen/bin/xen-vncfb or try to create a paravirtualized domU (virtual machine) with the appropriate VNC directives (see Additional Information). Actual Results: VNC consoles for paravirtualized guests is not available. Expected Results: Supported this feature... but hey, its an easy one to miss. One can leverage the XENFB_TOOLS functionality (once its available in the xen-tools ebuild) by entering directives such as the following in one's VM configuration file: vfb = [ 'type=vnc' ] extra = "xencons=ttyS0 console=ttyS0 video=xenfb" The above will spawn a VNC listener for your guest.
Created attachment 137298 [details, diff] Patch to ebuild which provides XENFB_TOOLS=y support I have written a patch to the ebuild which adds a "xenfb" USE flag and adjusts the build appropriately to support XENFB_TOOLS. Hope this helps.
What the current status? (xen-tools-3.2.1) Is vnc support offered now? I can's see any vnc dependencies in the ebuilds. I can't tell, if that's necessary. Actually, i'm trying to use it on a non-multilib amd64 system and so the hvm use-flag is disabled. I'm only using paravirtualized systems and since new linux domU kernels support a Xen framebuffer device, i'd like to use it.
The xenfb tool has been removed in 3.2.0, per this commit: http://xenbits.xensource.com/xen-3.2-testing.hg?rev/1ed990bc8da9 It's now built as part of the hvm, but that setup changed a lot and I'm not sure our current ebuild reflects that correctly.
Suggest that this bug should be closed won't fix due to: a) Xen 3.1 is very old b) VNC for PV guests is available and working with the ioemu use flag in latest 4.0.1
(In reply to comment #4) I agree with Spooky and I'll add that the VNC console works correctly also in Xen-3.4.*, if you don't want to upgrade to 4.x.
Xen 4.1 in tree. Please test with it and reopen if it doesnt work
