cannot boot domU

cannot boot domU

[Stephan Böni]

[-- Attachment #1.1: Type: text/plain, Size: 2775 bytes --]

I cannot boot domU:
 
# xm create inhouse
Using config file "inhouse".
Started domain inhouse
# xm list
Name              ID  Mem(MiB)  CPU  VCPUs  State   Time(s)
Domain-0           0       123    0      1  r-----     27.4
inhouse            8      2048    0      1  ------     11.4
# xm console inhouse
Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)
 (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005
kernel direct mapping tables upto 80000000 @ 7ba000-bbd000
Built 1 zonelists
Kernel command line:  root=/dev/sda1 3
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 3200.108 MHz processor.
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 2050304k/2097152k available (1682k kernel code, 46344k reserved, 561k da
ta, 136k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Hyper-Threading is disabled
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1129473172.510:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 128Kbytes
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
#
# cat inhouse | grep -v ^#
kernel = "/boot/vmlinuz-2.6.12.6-xenU"
memory = 2048
name = "inhouse"
disk = [ 'phy:xenvg/inhouse-root,sda1,w' ]
root = "/dev/sda1"
extra = "3"
 
Does anyone know what the problem is?
 
Stephan
 

[-- Attachment #1.2: Type: text/html, Size: 4770 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: cannot boot domU

[stoeni]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi stephan,

Stephan Böni schrieb:
> #
> # cat inhouse | grep -v ^#
> kernel = "/boot/vmlinuz-2.6.12.6-xenU"
> memory = 2048
> name = "inhouse"
> disk = [ 'phy:xenvg/inhouse-root,sda1,w' ]

looks like a missing /dev on the disk parameter. it should look like this:

disk = ['phy:/dev/xenvg/inhouse-root,sda1,w','

> root = "/dev/sda1"
> extra = "3"


- --
Tschaw/2,
Stoeni!

++ Please remember: rm -rf means "read mail -really fast" ++
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDUmkRjhe+lWpwo40RAoCoAJ9z0sRxXhYu2GsOldIq04Y0hvb5IACdFnAK
iCSW6+8WPlW3qghCegXMRA0=
=CB8d
-----END PGP SIGNATURE-----

Re: cannot boot domU

[Nicholas Lee]

On 10/17/05, Stephan Böni <boeni@bpm.ch> wrote:
> # xm console inhouse
> Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 20050901
> (prerelease)
>  (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005


I've not heard if Xen works with gcc 4.0. That might be worth checking.

Otherwise I suggest sending though logs from xm dmesg, vgdisplay and
anything else that might be useful.

Not sure what else I can suggest, pretty much told you everything I've
figured out so far. :)

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: cannot boot domU

[Ted Kaczmarek]

On Mon, 2005-10-17 at 23:30 +1300, Nicholas Lee wrote:
> On 10/17/05, Stephan Böni <boeni@bpm.ch> wrote:
> > # xm console inhouse
> > Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 20050901
> > (prerelease)
> >  (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005
> 
> 
> I've not heard if Xen works with gcc 4.0. That might be worth checking.
Unstable works as well for me with gcc 4.0.1 as 3.4.3.
> 
> Otherwise I suggest sending though logs from xm dmesg, vgdisplay and
> anything else that might be useful.
> 
> Not sure what else I can suggest, pretty much told you everything I've
> figured out so far. :)

xen_changeset : Sun Oct 16 12:25:15 2005 +0100 7396:9b51e763767

This changeset appears to have less issues with respect to creating the
disk device for the domU, but I am having lots of problems with vifs
being mapped to the bridges, manually mapping them doesn't help. This
may be specific to the present setup I am using, eth0 is used for the
domU's and eth1 is the egress interface. 

Regards,
Ted






> 
> --
> Nicholas Lee
> http://stateless.geek.nz
> gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: cannot boot domU

[Stephan Böni]

> > #
> > # cat inhouse | grep -v ^#
> > kernel = "/boot/vmlinuz-2.6.12.6-xenU"
> > memory = 2048
> > name = "inhouse"
> > disk = [ 'phy:xenvg/inhouse-root,sda1,w' ]
> 
> looks like a missing /dev on the disk parameter. it should 
> look like this:
> 
> disk = ['phy:/dev/xenvg/inhouse-root,sda1,w','
> 
> > root = "/dev/sda1"
> > extra = "3"

No, same problem with additional /dev.  :-(

Stephan

Re: cannot boot domU

[Nicholas Lee]

Two things.

Make sure hotplug is install in dom0.

Make sure the disk block device name in domU, sda1 in your case, does
not conflict with a device block in active use in dom0.  ie. change it
to something like sdb1 or sba10.

There are a few threads about this last week.

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: cannot boot domU

[Stephan Böni]

> Two things.
> 
> Make sure hotplug is install in dom0.

It is.

> Make sure the disk block device name in domU, sda1 in your case, does
> not conflict with a device block in active use in dom0.  ie. change it
> to something like sdb1 or sba10.

I've changed now to hda1. (There is no hda device in my system.) But it
does still not boot.

Linux version 2.6.12.6-xenU (root@xen1) (gcc version 4.0.2 20050901 (prerelease)
 (SUSE Linux)) #1 SMP Sun Oct 16 15:40:12 CEST 2005
kernel direct mapping tables upto 80000000 @ 7ba000-bbd000
Built 1 zonelists
Kernel command line:  root=/dev/hda1 3
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
Xen reported: 3200.104 MHz processor.
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
Memory: 2050304k/2097152k available (1682k kernel code, 46344k reserved, 561k da
ta, 136k init)
Mount-cache hash table entries: 256
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 1024K
CPU: Hyper-Threading is disabled
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1129538349.597:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 128Kbytes
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Stephan

Re: cannot boot domU

[Nicholas Lee]

On 10/17/05, Stephan Böni <boeni@bpm.ch> wrote:
> > Two things.
> I've changed now to hda1. (There is no hda device in my system.) But it
> does still not boot.

Change it to sda10 or sdb1 or something else. I think even with hda it
might have issues.

Note there is no need to include /dev/ in disk = [...].

--
Nicholas Lee
http://stateless.geek.nz
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Re: cannot boot domU

[Stephan Böni]

> > > Two things.
> > I've changed now to hda1. (There is no hda device in my 
> system.) But it
> > does still not boot.
> 
> Change it to sda10 or sdb1 or something else. I think even with hda it
> might have issues.
> 
> Note there is no need to include /dev/ in disk = [...].
> 
It does not work with or without it.

Stephan