Back to the PV Drivers issue, I guess I'm facing similar problem on a 2.6.24 HVM kernel for building unmodified_drivers.
- Are those unmodified_drivers only for 2.6.18 kernel?
- If not, what are the prerequisites?
Besides, when running the ./mkbuildtree command, the command references "../../linux-2.6.18-xen.hg/drivers/xen/" , which makes me surprised and I don't have a clue why... For example, James' PV Drivers for Windows doesn't require to have any 2.6.18 kernel anywhere...
I was thinking that these PV unmodified_drivers for HVM Linux DomUs would be "kernel independent" as long as the kernel is from 2.6 tree.
On Fri, May 30, 2008 at 11:20 AM, jim burns <jim_burn@xxxxxxxxxxxxx
On Thursday May 29 2008 11:55:24 pm Daniel Schwager wrote:Old style, still works in my hvm configs on Fedora 8:
> > > You can certainly connect to PV & HVM domains alike with vnc.
> How to configure? I thought a PV domain has no BIOS and therefore i can
> connect only with the "xm console" command ?
# set VNC display number, default = domid
# try to find an unused port for the VNC server, default = 1
New style (xen 3.1.2 and up) which I use in pv domains:
#vfb=[ 'type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=1' ]
vfb=[ 'type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=0, vncdisplay=4' ]
Note, on Fedora, I can never get the vnc window to come up automatically on
issuing 'xm create', despite the vncconsole statement (which doesn't work
inside the vfb= clause). This shouldn't be a problem for your admin colsole
function, which would do the equivalent of a manual vnc connect. Also note,
on recent xens, the vncdisplay=n statement selects port # 5900+n to connect
with, despite the comments in the xmexample* files, that say it should be the
Emre - thanx for the correction on the usage of the unmodified drivers.
Xen-users mailing list