Re: [Xen-devel] virtual domain partial boot then crash

[xen@xxxxxxxxxx]

Ian Pratt wrote:
> I'm afraid I haven't read your failure report in detail, but
> please can you try:
>
>         domain new
>         physical grant -phdb7 -w        #swap
>         physical grant -phdb8 -w        #root
>         domain start
Doh! Thanks, Ian.  I knew about the -w.  Must've been a long day.  That allowed it to 
move into the "Init" stage of the boot process.

> All of this is rather clearer with the new tools in the unstable
> tree. Expect a 1.2 release fairly soon...
I'm not that uncomfortable with the command line tools, but, aaargh, I don't 
know python yet. :(

OK, here's the new status.  The guest no longer dies a mysterious death but 
does crash about the time it tries to set the hardware clock.  Following is a 
partial output from the guest.
...
[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] kjournald starting.  Commit interval 5 seconds
[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 unable to get I/O port access:  the iopl(3) call failed.^M
[1] Setting clock  (localtime):

And that's where it goes quiet.

Since there won't be any consoles on a guest I'm guessing that the rc.sysinit 
complaints don't matter although I don't know how to shut them up.

So it looks like setting the clock is the problem.  Any pointers or ideas, 
anyone?

Thanks,
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