Re: NetBSD DOMU Xen 4.2 xl lvm disk

[Roger Pau Monné <roger.pau%citrix.com@localhost>]

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

> ]
> 
> vif = [ 'mac=00:18:5e:5f:db:ee, bridge=bridge0' ]
> 
> vcpus = 2
> 
> boot="dc"
> 
> vnc=1

boot and vnc don't have any meaning in PV guests, so you can just remove
them.

> 
> =======
> 
> And here is the output while trying to create the domain.
> 
> # xl create -c nbsd6.cfg
> Parsing config from nbsd6.cfg
> Daemon running with PID 2202
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
> 2006, 2007, 2008, 2009, 2010, 2011, 2012
> The NetBSD Foundation, Inc. All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
> 
> NetBSD 6.0 (INSTALL_XEN3_DOMU)
> total memory = 1024 MB
> avail memory = 978 MB
> mainbus0 (root)
> hypervisor0 at mainbus0: Xen version 4.2.1-rc1
> vcpu0 at hypervisor0: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz, id 0x2065
> 2
> vcpu1 at hypervisor0: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz, id 0x2065
> 2
> xenbus0 at hypervisor0: Xen Virtual Bus Interface
> xencons0 at hypervisor0: Xen Virtual Console Driver
> xenbus: can't get state for device/suspend/event-channel (2)
> xbd0 at xenbus0 id 768: Xen Virtual Block Device Interface
> xbd1 at xenbus0 id 5632: Xen Virtual Block Device Interface
> xennet0 at xenbus0 id 0: Xen Virtual Network Interface
> xennet0: MAC address 00:18:5e:5f:db:ee
> balloon0 at xenbus0 id 0: Xen Balloon driver
> balloon0: current reservation: 1048576 KiB
> xennet0: using RX copy mode
> xenbus: can't get state for device/suspend/event-channel (2)
> balloon0: current reservation: 262144 pages => target: 262145 pages
> balloon0: memory 'hot-plug' unsupported - clipping reservation 1 => 0 pages.
> balloon0: WARNING: balloon could not reach target 262145 (current 262144)
> ignore shutdown request:
> 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)...
> 
> 
> Am I missing something or is this a bug?
> 
> NOTE: I've tried to use the raw device but xl doesn't seam to support 
> this, I get:
> libxl: error: libxl_device.c:250:libxl__device_disk_set_backend: Disk 
> vdev=xvda phys path is not a block dev or file: /dev/mapper/rvgXen-lvNBSD
> 
> I see nothing else in /var/log/xen/....
> 
>