[Xen-devel] virtual domain partial boot then crash

[xen@xxxxxxxxxx]

Hi all,

I have a configuration problem and could use some help.  I read every single 
posting in the xen-devel archives and can't figure this out.

Xen boots xenolinux fine.  Full RH9.  uname shows the xeno-2.4.22 kernel.  
xenctl domain list shows domain0.  This all looks ok to me.

I'm using a drive with 4 partitions and 2 redhats:
1:
        hdb5 swap
        hdb6 redhat9 with xen and xenolinux
2:
        hdb7 swap
        hdb8 redhat9 with xenolinux

hdb6 and hdb8 can be booted natively.  hdb6 cleanly loads xen and boots 
xenolinux.

The mount points in /etc/fstab are correct for each.  On hdb8 /etc/initab 
initial runlevel is set to 4.

Here's how I invoke the guest.

$xen_nat_enable
$xen_read_console | tee /var/log/xen &
$xenctl script -f/etc/xen-mydom

xen-mynewdom contains:
        physical grant -phdb7   #swap
        physical grant -phdb8   #root
        domain start
        domain new

xenctl.xml contains:

        <?xml version="1.0"?>
        <domctl_defaults>
        <domain_name>XenoLinux</domain_name>
        <domain_size_kb>98304</domain_size_kb>
        <domain_image>/boot/xenolinux.gz</domain_image>
        <domain_vifs>1</domain_vifs>
        <root_device>/dev/hdb8</root_device>
        <root_args>ro</root_args>
        <args>DOMID=1</args>
        <nw_ip>10.0.0.31</nw_ip>
        <nw_gw>10.0.0.252</nw_gw>
        <nw_mask>255.255.255.0</nw_mask>
        <nw_nfs_server>169.254.1.0</nw_nfs_server>
        <max_domain_number>10</max_domain_number>
        <xi_tools_dir>/usr/local/bin/</xi_tools_dir>
        </domctl_defaults>

Here is the part of the boot sequence around where the errors occur:

...
[1] Kernel command line: 
ip=10.0.0.31:169.254.1.0:10.0.0.252:255.255.255.0::eth0:off DOMID=1  
root=/dev/hdb8 ro
...
[1] XenoLinux Virtual Network Driver installed as eth0
[1] IP-Config: Complete:
[1]       device=eth0, addr=10.0.0.31, mask=255.255.255.0, gw=10.0.0.252,
[1]      host=10.0.0.31, domain=, nis-domain=(none),
[1]      bootserver=169.254.1.0, rootserver=169.254.1.0, rootpath=
[1] ip_conntrack version 2.1 (768 buckets, 6144 max) - 292 bytes per conntrack
[1] ip_tables: (C) 2000-2002 Netfilter core team
[1] NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
[1] root_device_name = hdb8
[1] Can't write to read-only device 03:48
[1] kjournald starting.  Commit interval 5 seconds
[1] Can't write to read-only device 03:48
[1] EXT3-fs: mounted filesystem with ordered data mode.
[1] VFS: Mounted root (ext3 filesystem) readonly.
[1] Freeing unused kernel memory: 60k freed
[1] ^MINIT: version 2.84 booting^M^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty1: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty2: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty3: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty4: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty5: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 39: /dev/tty6: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 43: /dev/tty7: No such device^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] /etc/rc.d/rc.sysinit: line 44: /dev/tty8: No such device^M
[1]     Welcome to Red Hat Linux^M
[1]     Press 'I' to enter interactive startup.^M
[1] Mounting proc filesystem:  [  OK  ]^M^M
[1] Configuring kernel parameters:  [  OK  ]^M^M
[1] modprobe: modprobe: Can't locate module char-major-10-135^M^M
[1] modprobe: modprobe: Can't locate module char-major-4^M^M
[1] hwclock is unabl

At this point it looks dead but I can ping it.  The only public service on it 
is sshd but that  gives connection refused.  Its log files are empty.  Its 
iptables is off so it's not blocking traffic.  I hacked /etc/rc.d/rc.sysinit to 
make the modprobe errors go away but things became very erratic and would 
appear to halt randomly during the boot.  When put back it errs like int the 
log above every time.

Any ideas or pointers on what to try next?

All help appreciated,
Mike Wright




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel