On 04/26/10 08:42 PM, Jorgen Lundman wrote:
If you want to test it yourself, I run the following command on domU 'ssh00'
This is fixed in b137 by
6931744 DomU occasionally stops responding after reboot
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6931744
MRJ
# while [ 1 ]; do logger -p kern.alert `date`; date; sleep 1; done
Which shows output on domU 'ssh' login as well as on dom0's 'virsh console'
dom0:
Apr 27 09:36:02 ssh00.unix lundman: Tue Apr 27 09:36:02 JST 2010
Apr 27 09:36:03 ssh00.unix lundman: Tue Apr 27 09:36:03 JST 2010
domU:
Tue Apr 27 09:36:02 JST 2010
Tue Apr 27 09:36:03 JST 2010
I disconnect "virsh console":
Apr 27 09:36:04 ssh00.unix lundman: Tue Apr 27 09:36:04 JST 2010
xen01:~#
and domU keeps running:
Tue Apr 27 09:36:05 JST 2010
Tue Apr 27 09:36:06 JST 2010
Tue Apr 27 09:36:07 JST 2010
[...]
until:
Tue Apr 27 09:36:58 JST 2010
Tue Apr 27 09:36:59 JST 2010
Tue Apr 27 09:37:00 JST 2010
and it is dead. You can not even ping the server.
We connect back on "virsh console":
xen01:~# virsh console ssh00.unix
Apr 27 09:36:05 ssh00.unix lundman: Tue Apr 27 09:36:05 JST 2010
Apr 27 09:36:06 ssh00.unix lundman: Tue Apr 27 09:36:06 JST 2010
[...]
Apr 27 09:37:00 ssh00.unix lundman: Tue Apr 27 09:37:00 JST 2010
Apr 27 09:37:27 ssh00.unix lundman: Tue Apr 27 09:37:27 JST 2010
(Bit of a pause there, 27 seconds gone?)
and domU also resumes:
Tue Apr 27 09:37:27 JST 2010
^C
_______________________________________________
xen-discuss mailing list
[email protected]
