[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] PV drivers on HVM opensuse 10.3

  • To: "jim burns" <jim_burn@xxxxxxxxxxxxx>
  • From: "Emre ERENOGLU" <erenoglu@xxxxxxxxx>
  • Date: Sat, 31 May 2008 15:56:01 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Daniel Schwager <Daniel.Schwager@xxxxxxxx>
  • Delivery-date: Sat, 31 May 2008 06:56:31 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=E8IgLhCg0hP+Xf9Igb+s2AjnE+DnJI9b5FusmH84PvD8CNj+ZPB6u/ddPnDFvPCzj8aE/nXih2S5ZDj5IDykmHM7WT30uLY/LONo1LrSAKl47m2DqTxqPLVH9lu0t0p8xx4UR0AKQdRQBGSlYtpu2OSMj5vdUq84tLbk5lY+7NI=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

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> wrote:
On Thursday May 29 2008 11:55:24 pm Daniel Schwager wrote:
> > > 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 ?

Old style, still works in my hvm configs on Fedora 8:

# 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=, vncunused=1' ]
vfb=[ 'type=vnc, keymap=en-us, vnclisten=, 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

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.