Re: NetBSD DOMU Xen 4.2 xl lvm disk

[Mike <miguelmclara%gmail.com@localhost>]

On 07/12/2012 11:44, Mike wrote:
> On 07/12/2012 11:32, Roger Pau Monné wrote:
> > On 07/12/12 12:19, Mike wrote:
> > > On 07/12/2012 10:56, Roger Pau Monné wrote:
> > > > On 07/12/12 11:48, Mike wrote:
> > > > > I'm testing Xen 4.2, I've compiled successfully, following the 
> > > > > guide at
> > > > > http://wiki.xen.org/wiki/Compiling_Xen_From_Source_on_NetBSD
> > > > >
> > > > >
> > > > > Since xend is now deprecated I was trying to use XL, but its seems 
> > > > > its
> > > > > still not working for LVM devices?
> > > > >
> > > > > My config file:
> > > > >
> > > > > =========
> > > > > cat nbsd6.cfg
> > > > > name = "netBSD6"
> > > > >
> > > > > #kernel = "/home/miguelc/xen-data/kernels/netbsd-XEN3_DOMU.gz"
> > > > > kernel = "/home/miguelc/xen-data/kernels/netbsd-INSTALL_XEN3_DOMU.gz"
> > > > >
> > > > > memory = 1024
> > > > >
> > > > > disk = [ '/dev/mapper/vgXen-lvNBSD,,hda,rw',
> > > > I'm not sure if this syntax will work correctly, I think you are at
> > > > least missing the "phy:/" prefix, this line should look like:
> > > >
> > > > 'phy:/dev/mapper/vgXen-lvNBSD,xvda,w'
> > > >
> > > > > '/home/miguelc/xen-data/iso/NetBSD-6.0-amd64.iso,,hdc,cdrom'
> > > > And this:
> > > >
> > > > 'file:/home/miguelc/xen-data/iso/NetBSD-6.0-amd64.iso,xvdc:cdrom,r'
> > > >
> > > > There are many ways in which to specific block devices, take a look 
> > > > at:
> > > >
> > > > http://xenbits.xen.org/docs/unstable/misc/xl-disk-configuration.txt
> > > "These might be specified in the domain config file like this:
> > >
> > >     disk = [ '/dev/vg/guest-volume,,hda', 
> > > '/root/image.iso,,hdc,cdrom' ]"
> > >
> > > The syntax seams correct... I did use the instructions in that same 
> > > link.
> > > My previous configuration (for xend) had the "phy:" and "file:" syntax
> > > and I got the same results with that!
> > >
> > > In any case changing the config:
> > > ....
> > >
> > > disk = [ 'phy:/dev/mapper/vgXen-lvNBSD,hda,w',
> > > 'file:/home/miguelc/xen-data/iso/NetBSD-6.0-amd64.iso,hdc,cdrom'
> > >           ]
> > >
> > > vif = [ 'mac=00:18:5e:5f:db:ee, bridge=bridge0' ]
> > >
> > > vcpus = 2
> > > ......
> > >
> > > I get the exact same result:
> > >
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > > xenbus: can't get state for device/suspend/event-channel (2)
> > >
> > >
> > >
> > >
> > > Also removing the lvm disk (with or without the "phy" syntax) boots the
> > > Guest machine into the install kernel has expected!
> > When you are in this state (DomU running, no install screen), could you
> > switch to the Dom0 and post the output of xenstore-ls -fp?
> >
> > Thanks
> Sure, I've attached it, since its a bit long :)
I also notice this on dmesg (dom0 ofc):

xbdback backend/vbd/6/51712: can't DIOCGWEDGEINFO device 0xa902: 25 
<----------------------------
vnd0: unable to open device, error = 16
xbd backend: attach device vnd0d (size 675884) for domain 6
xvif6i0: Ethernet address 00:18:5e:60:db:ee
xbd backend domain 6 handle 0x1600 (5632) using event channel 30, 
protocol x86_64-abi
xbd backend domain 6 handle 0xca00 (51712) using event channel 31, 
protocol x86_64-abi