On Thursday, 03 December 2009 at 17:10, Jeremy Fitzhardinge wrote:
> On 12/03/09 16:24, Brendan Cully wrote:
> >On Thursday, 03 December 2009 at 15:22, Jeremy Fitzhardinge wrote:
> >>On 12/03/09 11:35, Brendan Cully wrote:
> >>>Not a patch, but I've just tried out xm save -c again with the latest
> >>>xen changes, and while I no longer see the grant table version panic,
> >>>the guest's devices (aside from the console) appear to be wedged on
> >>>resume. Is anyone else seeing this?
> >>>
> >>>After a while on the console I see messages like this:
> >>>
> >>>INFO: task syslogd:2219 blocked for more than 120 seconds.
> >>>
> >>>which I assume is trouble with the block device.
> >>Is there any backtrace or other info associated with this?
> >I take it you couldn't reproduce? Let me know what you want
> >captured. In the meantime, here's the kernel log:
>
> Nope, works for me :) Ian has been doing testing with hundreds or
> thousands of suspend/resumes, so it *can* be reliable.
>
> That said, I am seeing some odd hangs after suspend/resume with the
> bugfix branch merged into Linux mainline...
>
> Can you ping the domain when its in that state?
Nope. If it matters, my environment is 64-bit xen, 32-bit 2.6.18 dom0,
both the latest HG.
Here's a diff of xenstore-ls before and after xm save -c, which
doesn't say much. I don't know why that VBD ring-ref is changing
though.
--- xs-presuspend.txt 2009-12-03 20:25:51.419603196 -0800
+++ xs-postsuspend.txt 2009-12-03 20:26:20.604309769 -0800
@@ -96,7 +96,7 @@
backend-id = "0"
state = "4"
backend = "/local/domain/0/backend/vbd/18/51713"
- ring-ref = "8"
+ ring-ref = "101"
event-channel = "9"
vif = ""
0 = ""
@@ -121,6 +121,7 @@
backend = "/local/domain/0/backend/console/18/0"
control = ""
platform-feature-multiprocessor-suspend = "1"
+ shutdown = ""
error = ""
memory = ""
target = "262144"
@@ -223,7 +224,8 @@
on_crash = "restart"
xend = ""
restart_count = "0"
+ last_shutdown_reason = "suspend"
vcpus = "1"
vcpu_avail = "1"
bootloader = ""
- name = "p32"
+ name = "migrating-p32"
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|