I''ve been experimenting with using save/restore as a poor-mans migration on 3.0.2-2 and have experienced some real problems with the guests hanging when they are restored. In the end, I was able to repro this simply executing ''xm save'' and then ''xm restore'' on the same system -- the symptom is that the the restored guest is apparently running (for example, I can ping it) but anything that requires access to the disk hangs up. Eventually, I dumped the guest and used crash to look at what was going on and I can see that the VBD front end driver is hung waiting for disk I/O to complete -- it seems to reconnect to the backend OK and re-issues I/O that was outstanding when the guest was saved (in all cases, there seems to be a single I/O outstanding when the save is done - a syslog write) and even carries on and issues more disk I/O requests _but_ none of them complete. I should say that both Dom0 and DomU are 3.0.2-2 on top of vanilla 2.6.16kernels. Anyone know if this is a known issue with the release? Or suggest further investigation required? Simon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users