I have retested this problem.
I find if only xenU memory config is 256, the problem is coming.
But if xenU memory config is only 128, there isn''t this problem.
Could anybody reproduce this problem?
Here is my problem xenU conf:>cat xenu.conf
kernel = "/boot/vmlinuz-2.6.11-xenU"
memory = 256
name = "problem_xenU"
disk = [ ''file:/data/rhel3-domU.2g.img,sda1,w'' ]
root = "/dev/sda1 ro"
If memory = 128, won''t happen this bug.
Thanks,
Yongkang You(Kangkang)
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>bounces@lists.xensource.com] On Behalf Of You, Yongkang
>Sent: Thursday, June 30, 2005 1:36 PM
>To: xen-devel@lists.xensource.com
>Subject: [Xen-devel] ia32 xenU crashed
>
>Hi all,
>
>Did anyone try xenU in latest bk?
>
>My xenU crashed with following flushed screen: :-(
>...
>XENBUS xs_read_watch: -5
>XENBUS xXENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_wX_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_wXENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xXENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>XENBUS xs_read_wXENBUS xs_read_watch: -5
>XENBUS xs_read_watch: -5
>...
>
>Nothing output to "xm dmesg" and serial port.
>
>Thanks,
>Yongkang You(Kangkang)
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel