Manuel Bouyer wrote:
On Mon, Nov 09, 2009 at 05:33:17PM +0000, Hugo Silva wrote:Hello everyone,I've been, during the past few days, trying to run domUs backed by LVMs, so far without success.Here's what I get:# xm create -c /usr/pkg/xen/conf/netbsd50.confUsing config file "/usr/pkg/xen/conf/netbsd50.conf". Started domain netbsd-pv : Intel 686-class, 2405MHz, id 0x6fb xenbus0 at hypervisor0: Xen Virtual Bus Interface xencons0 at hypervisor0: Xen Virtual Console Driver xencons0: using event channel 2 xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface xennet0 at xenbus0 id 0: Xen Virtual Network Interface xennet0: MAC address aa:aa:00:c4:aa:f4 (domU becomes unresponsive)If I replace "disk = [ 'phy:/dev/mapper/vg00-lv0,0x1,w' ]" with disk = [ 'file:/usr/pkg/xen/netbsd.img,0x1,w' ], it will boot perfectly.Nothing interesting in the logs.. (xend.log)Anything in the xenbackendd.log or dmesg output ?
xenbackendd.log and dmesg (relevant part) after removing all xen logs, rebooting, reactivating the LVs (lvm vgchange -a y) and launching domU:
# lvm vgchange -a y# pwd && wc -c xenbackendd.log
/var/log
0 xenbackendd.log
# xm create
/usr/pkg/xen/conf/netbsd50.conf
Using config file "/usr/pkg/xen/conf/netbsd50.conf". Started domain netbsd-pv dmesg:xbdback backend/vbd/1/1: can't DIOCGPART device 0xa901: 12 // <------- ?
xvif1.0: Ethernet address aa:aa:00:c5:aa:f4 sysctl_createv: sysctl_create(xvif1.0) returned 22 xvif1.0: could not attach sysctl nodes xbd backend 0x1 for domain 1 using event channel 17, protocol x86_64-abi# cat xenbackendd.log Failed to read /local/domain/0/backend/console/1/0/script (No such file or directory)
# xm list && xm destroy netbsd-pvName ID Mem VCPUs State Time(s) Domain-0 0 256 1 r----- 183.7 netbsd-pv 1 512 1 -b---- 0.9