qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Cornec <bruno@mondorescue.org>
To: qemu-devel@nongnu.org
Cc: bruno@mondorescue.org
Subject: [Qemu-devel] QEMU on x86_64: some feedback and questions
Date: Sun, 3 Jun 2007 23:03:01 +0200	[thread overview]
Message-ID: <20070603210301.GD10057@victoria2.home.musique-ancienne.org> (raw)

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).

My debian 4.0 and suse 10.2 x86_64 VMs exhibit another issue. During
installation they block at grub-install and never go out - I left them
for hours with out sign of change. I tried to install grub manually
without more luck. And thus can't really finish the installation.

Let me know if I can provide you more precise details (or screenshots)
that could help you solve those issues, or if you have tests that you
want me to perform in order to diagnose the problem.

I already saw some similar reports (Cf:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425648) but not any
track to solve them.

At least I hope the report is useful.
Thanks for a great tool and best regards,
Bruno.
-- 
Des infos sur la musique ancienne  -- http://www.musique-ancienne.org
Des infos sur les logiciels libres -- http://www.HyPer-Linux.org
Home, sweet musical Home -- Lover of Andromède, Béatrice, Early Music, 
Josquin, Linux, Mélisande, Recorder, and Ségolène (not in that order)

             reply	other threads:[~2007-06-03 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 21:03 Bruno Cornec [this message]
2007-06-04  8:24 ` [Qemu-devel] QEMU on x86_64: some feedback and questions Natalia Portillo
2007-06-04  9:39 ` [Qemu-devel] " Loiseleur Michel

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=20070603210301.GD10057@victoria2.home.musique-ancienne.org \
    --to=bruno@mondorescue.org \
    --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).