Hi again :)
OK we're making good progress. Dom0 booted with 2.6.16-xen kernel,
Steve's wonderful xen-create-image has done the biz for me with
debootstrap and created a sid disk image+swap, and I can start the
created 'joltpg1' OK.. but when I go to connect to the console, I see this:
jolt:/dev# xm console joltpg1
xenconsole: Could not read tty from store: No such file or directory
And that's the end of it. Dom0 is using the x86_64 binary release of Xen
3.0.2,
I've not found much help on the web with this other than 'this must be a
bug' from Nov 2005 - just wondered if anyone had more timely pearls of
wisdom to impart? ;)
The interesting part of xm log reports...
[2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:178)
XendDomainInfo.create([\047vm\047, [\047name\047, \047joltpg1\047],
[\047memory\047, 2048], [\047vcpus\047, 1], [\047image\047,
[\047linux\047, [\047kernel\047, \047/boot/vmlinuz-2.6.16-xen\047],
[\047ip\047, \047:1.2.3.4::::eth0:dhcp\047], [\047root\047,
\047/dev/sda1 ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047,
\047file:/root/xen/domains/joltpg1/disk.img\047], [\047dev\047,
\047sda1\047], [\047mode\047, \047w\047]]], [\047device\047,
[\047vbd\047, [\047uname\047,
\047file:/root/xen/domains/joltpg1/swap.img\047], [\047dev\047,
\047sda2\047], [\047mode\047, \047w\047]]]])
[2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:284)
parseConfig: config is [\047vm\047, [\047name\047, \047joltpg1\047],
[\047memory\047, 2048], [\047vcpus\047, 1], [\047image\047,
[\047linux\047, [\047kernel\047, \047/boot/vmlinuz-2.6.16-xen\047],
[\047ip\047, \047:1.2.3.4::::eth0:dhcp\047], [\047root\047,
\047/dev/sda1 ro\047]]], [\047device\047, [\047vbd\047, [\047uname\047,
\047file:/root/xen/domains/joltpg1/disk.img\047], [\047dev\047,
\047sda1\047], [\047mode\047, \047w\047]]], [\047device\047,
[\047vbd\047, [\047uname\047,
\047file:/root/xen/domains/joltpg1/swap.img\047], [\047dev\047,
\047sda2\047], [\047mode\047, \047w\047]]]]
[2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:380)
parseConfig: result is {\047ssidref\047: None, \047uuid\047: None,
\047on_crash\047: None, \047on_reboot\047: None, \047image\047:
[\047linux\047, [\047kernel\047, \047/boot/vmlinuz-2.6.16-xen\047],
[\047ip\047, \047:1.2.3.4::::eth0:dhcp\047], [\047root\047,
\047/dev/sda1 ro\047]], \047on_poweroff\047: None, \047cpus\047: None,
\047name\047: \047joltpg1\047, \047backend\047: [], \047vcpus\047: 1,
\047cpu_weight\047: None, \047vcpu_avail\047: None, \047memory\047:
2048, \047device\047: [(\047vbd\047, [\047vbd\047, [\047uname\047,
\047file:/root/xen/domains/joltpg1/disk.img\047], [\047dev\047,
\047sda1\047], [\047mode\047, \047w\047]]), (\047vbd\047, [\047vbd\047,
[\047uname\047, \047file:/root/xen/domains/joltpg1/swap.img\047],
[\047dev\047, \047sda2\047], [\047mode\047, \047w\047]])],
\047bootloader\047: None, \047cpu\047: None, \047maxmem\047: None}
[2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:1164)
XendDomainInfo.construct: None 0
[2006-04-28 12:35:40 xend.XendDomainInfo] DEBUG (XendDomainInfo:1196)
XendDomainInfo.initDomain: 10 1.0
[2006-04-28 12:35:40 xend] DEBUG (balloon:126) Balloon: free 2050; need
2049; done.
[2006-04-28 12:35:40 xend] INFO (image:135) buildDomain os=linux dom=10
vcpus=1
[2006-04-28 12:35:40 xend] DEBUG (image:173) dom = 10
[2006-04-28 12:35:40 xend] DEBUG (image:174) image =
/boot/vmlinuz-2.6.16-xen
[2006-04-28 12:35:40 xend] DEBUG (image:175) store_evtchn = 1
[2006-04-28 12:35:40 xend] DEBUG (image:176) console_evtchn = 2
[2006-04-28 12:35:40 xend] DEBUG (image:177) cmdline =
ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro
[2006-04-28 12:35:40 xend] DEBUG (image:178) ramdisk =
[2006-04-28 12:35:40 xend] DEBUG (image:179) vcpus = 1
[2006-04-28 12:35:40 xend] DEBUG (image:180) features =
[2006-04-28 12:35:40 xend] DEBUG (blkif:24) exception looking up device
number for sda1: [Errno 2] No such file or directory: \047/dev/sda1\047
[2006-04-28 12:35:40 xend] DEBUG (DevController:103) DevController:
writing {\047virtual-device\047: \0472049\047, \047backend-id\047:
\0470\047, \047state\047: \0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/10/2049\047} to
/local/domain/10/device/vbd/2049.
[2006-04-28 12:35:40 xend] DEBUG (DevController:105) DevController:
writing {\047domain\047: \047joltpg1\047, \047frontend\047:
\047/local/domain/10/device/vbd/2049\047, \047dev\047: \047sda1\047,
\047state\047: \0471\047, \047params\047:
\047/root/xen/domains/joltpg1/disk.img\047, \047mode\047: \047w\047,
\047frontend-id\047: \04710\047, \047type\047: \047file\047} to
/local/domain/0/backend/vbd/10/2049.
[2006-04-28 12:35:40 xend] DEBUG (blkif:24) exception looking up device
number for sda2: [Errno 2] No such file or directory: \047/dev/sda2\047
[2006-04-28 12:35:40 xend] DEBUG (DevController:103) DevController:
writing {\047virtual-device\047: \0472050\047, \047backend-id\047:
\0470\047, \047state\047: \0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/10/2050\047} to
/local/domain/10/device/vbd/2050.
And amongst all the \047 noise, there's:
[2006-04-28 12:35:40 xend] DEBUG (blkif:24) exception looking up device
number for sda1: [Errno 2] No such file or directory: /dev/sda1
I've checked the contents of the rootfs and it is indeed referencing
/dev/sda1 - any ideas why Xen is not 'providing' this device? Are
major/minor nodes needed in the rootfs image itself?
Cheers,
Gavin.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home