On Tue, 22 Jan 2008 19:20:05 +0100
Manuel Bouyer <bouyer@antioche.eu.org> wrote:

> On Tue, Jan 22, 2008 at 12:44:00PM +0000, Steven M. Bellovin wrote:
> > On Tue, 22 Jan 2008 21:35:00 +0900
> > Curt Sampson <cjs@netbsd.org> wrote:
> >=20
> > > On 2008-01-22 13:32 +0100 (Tue), Christoph Egger wrote:
> > >=20
> > > > > I did try to suspend a domU under Xen 3.1.2, and noticed that
> > > > > it didn't appear to work.
> > > >=20
> > > > Of course not. This is a new feature in Xen 3.2.0.
> > >=20
> > > Suspending a domU? It was in 3.1. This isn't suspending a laptop's
> > > dom0; this is just "xm suspend <domUname> <filename>".
> > >=20
> > I meant suspending a dom0.  From
> > http://lists.xensource.com/archives/html/xen-announce/2008-01/msg00000.=
html
> >=20
> > =A0 - ACPI S3 suspend-to-RAM support for the host system
>=20
> Maybe this one will work. No Xen state should be lost on the dom0
> side as all of it is in ram.=20
>=20
The issue, I suspect, is the interaction between NetBSD's ACPI support
and the hypervisor.


		--Steve Bellovin, http://www.cs.columbia.edu/~smb