Xin Chen wrote:
Thanks for quick response, Richard. Yes, it is similar but two differences: 1, instead of cpu lock, my domain 0 simply just reboot itself~~
The default configuration of Xen is that it will reboot if it detects that dom0 has crashed. To stop it doing this (so you can see any console messages), add noreboot to the Xen hypervisor command line. ie. in /boot/grub/menu.lst, locate the line which says:
kernel /xen.gz-XXX.fc6 and add: kernel /xen.gz-XXX.fc6 noreboot
2, I can't find any error message in the log, it is like a power off the machine.I thought it might be network I/O, but if using ftp, then there is no errors~, maybe a disk I/O, then I try cp a 10gb file to local drive on domain 0, it works as well.
From the other reports, it does look like it has something to do with network I/O.
Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
