From: Loiseleur Michel <mloiseleur@linagora.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU on x86_64: some feedback and questions
Date: Mon, 04 Jun 2007 11:39:07 +0200 [thread overview]
Message-ID: <f40mjr$v14$1@sea.gmane.org> (raw)
In-Reply-To: <20070603210301.GD10057@victoria2.home.musique-ancienne.org>
Bruno Cornec a écrit :
> Hello,
>
> I hope this kind of message is acceptable for this list.
> [I'm not a subscriber yet, please keep my address in cc:]
>
> I'm the developper of a project (http://www.mondorescue.org) where I
> extensively use QEMU for generating all the packages I want to produce
> for my application.
>
> Up to now my home system was an i686 machine and I had 26 different VMs
> to generate my sw for 26 different distros. All was fine, and kudos to
> the dev team for that.
>
> I recently changed for a Core2 Duo machine, and began to add 64 bits
> virutal machines to the play.
>
> First point, all my 26 i386 VMs seem to still work fine.
> For x86_64 VMs, the results are mixed:
>
> Fully operational for fedora 6, mandriva 2007.0, 2007.1, rhel 4 and 5.
>
> My rhel 3 x86_64 VM is unable to reboot correctly. When no special
> parameter given to the kernel, it does 'Lost interrupts' after detecting
> my hda IDE drive, and finishes by a kernel panic. If I add noapic
> nolapic to the boot line, it goes further (without 'Lost interrupts'
> mesages) but panics during ethernet card setup (acpi irq messages).
>
You can try also with -kernel-kqemu or with -no-kqemu. Sometimes, it's
more reliable.
Regards,
Michel
prev parent reply other threads:[~2007-06-04 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 21:03 [Qemu-devel] QEMU on x86_64: some feedback and questions Bruno Cornec
2007-06-04 8:24 ` Natalia Portillo
2007-06-04 9:39 ` Loiseleur Michel [this message]
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='f40mjr$v14$1@sea.gmane.org' \
--to=mloiseleur@linagora.com \
--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).