Re: differences in hvm save/restore in 3.1 vs 3.2

[Christopher Head <chead@cs.ubc.ca>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There's a bug in the serial port emulation in qemu related to saving and
restoring. There's a patch floating around somewhere which fixes it, but
depending on what source tree you're using you may not have it yet. One
of the critical registers isn't saved and also isn't regenerated at
restore time, meaning that serial port interrupts stop getting delivered
to the guest properly.

Chris

James Harper wrote:
|> It seems I can't use the windows debugger to help me, as after I
| restore
|> it will no longer reconnect, while it did when I was using Xen 3.1.
| That
|> may be unrelated to the above problem though... the debugger connects
| to
|> the serial port of the hvm domain via an 'xm console xxx' command in
|> inetd.conf... and I think that that isn't working properly after the
|> restore.
|
| Further to this, before the 'save' is issued, 'xm console' behaves how I
| would expect - nothing gets echo's to the screen and ^] closes the
| console session. After the 'restore', 'xm console' echo's everything to
| the screen, and ^] doesn't do anything useful (apart from print ^] on
| the screen), like the console session hasn't connected to the serial
| port at all.
|
| Any idea's on that?
|
| Thanks
|
| James
|
| _______________________________________________
| Xen-devel mailing list
| Xen-devel@lists.xensource.com
| http://lists.xensource.com/xen-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: GnuPT 2.7.2
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhtyYsACgkQiD2svb/jCb47kgCfS+6WHr8BKKeREuWY1hYatDDc
ooQAmwbuVQ7pGCLCc1KXgoX93ztijzfW
=Pw1D
-----END PGP SIGNATURE-----