From: Pavel Machek <pavel@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Antonio Vargas <wind@cocodriloo.com>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
root@mauve.demon.co.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspend on one machine, resume elsewhere [was Re: [Swsusp-devel] RE:Re: Thoughts wanted on merging Softwa]
Date: Thu, 17 Jul 2003 18:29:06 +0200 [thread overview]
Message-ID: <20030717162906.GB446@elf.ucw.cz> (raw)
In-Reply-To: <1058442562.8620.24.camel@dhcp22.swansea.linux.org.uk>
Hi!
> > > Would it not be a lot easier to tackle that with qemu, and teach qemu to
> > > freeze/restore virtual machines ?
> >
> > AFAIK, qemu does virtual processes, but not virtual machines. Running init(1)
> > from qemu could be fun, anyways ;)
>
> qemu moves on release by release. It can run an entire virtualised linux kernel
> nowdays, although its performance still needs some work.
I guess qemu is way too slow for this.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-07-17 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 20:20 RE:Re: Thoughts wanted on merging Softwa pavel
2003-07-15 21:22 ` [Swsusp-devel] " Karol Kozimor
2003-07-16 8:37 ` Pavel Machek
2003-07-16 10:37 ` root
2003-07-16 10:40 ` Suspend on one machine, resume elsewhere [was Re: [Swsusp-devel] RE:Re: Thoughts wanted on merging Softwa] Pavel Machek
2003-07-16 17:51 ` Ingo Oeser
2003-07-16 18:15 ` Pavel Machek
2003-07-16 19:17 ` Alan Cox
2003-07-16 22:39 ` Antonio Vargas
2003-07-17 11:49 ` Alan Cox
2003-07-17 16:29 ` Pavel Machek [this message]
2003-07-17 16:45 ` Alan Cox
2003-07-19 18:22 ` Suspend on one machine, resume elsewhere Jan Rychter
2003-07-20 22:53 ` Pavel Machek
2003-07-21 20:41 ` Jan Rychter
2003-07-23 5:13 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030717162906.GB446@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mauve.demon.co.uk \
--cc=wind@cocodriloo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).