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

[Xen-users] NetBSD dom0 / LVM backed


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Ben C <ben@xxxxxxxx>
  • Date: Wed, 26 May 2010 15:47:48 -0400
  • Delivery-date: Wed, 26 May 2010 12:50:09 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok, I am successful in getting a NetBSD dom0 (using 3.3.2) to install & boot Linux PV domu's .. but only using file backed disks.

From the NetBSD site:
# VDEV doesn't really matter for a NetBSD guest OS (it's just used as an index),
# but it does for Linux.
# Worse, the device has to exist in /dev/ of domain0, because xm will
# try to stat() it. This means that in order to load a Linux guest OS
# from a NetBSD domain0, you'll have to create /dev/hda1, /dev/hda2, ...
# on domain0, with the major/minor from Linux :(
# Alternatively it's possible to specify the device number in hex,
# e.g. 0x301 for /dev/hda1, 0x302 for /dev/hda2, etc ...

I absolutely and utterly do not understand this. I'm using NetBSD HEAD with LVM backed paritions, so with HVMs this has been fairly successful:

disk = [
        'phy:/dev/mapper/rvg00--Xen--Pool-Domu01,ioemu:hda,w',
]

But when trying with a pv, it fails to load the xenblk driver. (I guess, .. something goes wrong).

Any thoughts/clues/ideas? I'm curious on how to get the "hex" for the device? Or what my next steps should be.

Thanks, Ben

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

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