From: Fabrice Bellard <fabrice@bellard.org>
To: a_mulyadi@softhome.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ask about simulating cluster using Qemu
Date: Wed, 12 May 2004 20:54:11 +0200 [thread overview]
Message-ID: <40A272D3.8010309@bellard.org> (raw)
In-Reply-To: <200405071025.10908.a_mulyadi@telkom.net>
Mulyadi Santosa wrote:
> Hello all
>
> I have been following Qemu's development for about 3-4 months and I must say :
> TOTALLY AWESOME !!
>
> OK, to the point, i want to ask several things:
> 1. I have plan to simulate openMosix cluster....just 2 node for start. 1 node
> is my real PC, and the other is Qemu emulated host. AFAIK, when I try to load
> openMosix patched kernel (using 0.5.2), it got some errors on initial kernel
> loading......sorry I lost the exact message
>
> What should I do to solve it, at least clues to debug it....?
>
> 2. should I use tmpfs mounted on /tmp to accelerate Qemu? User Mode Linux
> suggest to use tmpfs....does Qemu use same method?
Yes, but it matters only for qemu-fast.
> 3. Is there any automation tools for generating disk image, more or less
> similar with UMLBuilder for UML? So far, for creating one, I put Debian Woody
> CDROM, boot it inside Qemu and install it into pre-made empty file.....
No. But you can use tools from other projects.
> 4. at certain interval, i got this message when running Debian:
> "probable hardware bug: restoring chip configuration
> probable hardware bug: clock timer configuration lost - probably a VIA686a
> probable hardware bug: restoring chip configuration"
It is a QEMU bug :-)
Fabrice.
next prev parent reply other threads:[~2004-05-12 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 12:57 [Qemu-devel] ask about simulating cluster using Qemu Mulyadi Santosa
2004-05-12 18:54 ` Fabrice Bellard [this message]
2004-05-13 4:14 ` Mulyadi Santosa
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=40A272D3.8010309@bellard.org \
--to=fabrice@bellard.org \
--cc=a_mulyadi@softhome.net \
--cc=qemu-devel@nongnu.org \
/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).