Summary: | app-emulation/xen-tools-3.1.2: doesn't support XENFB_TOOLS build option for VNC access to paravirtualized domU's | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Josh West <jwest> |
Component: | New packages | Assignee: | Gentoo Xen Devs <xen> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | luckyluke, sven.koehler |
Priority: | High | Keywords: | Inclusion |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to ebuild which provides XENFB_TOOLS=y support |
Description
Josh West
2007-11-29 07:44:11 UTC
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 |