qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jason Baron <jbaron@redhat.com>
Cc: David Allan <dallan@redhat.com>, Eric Blake <eblake@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] q35 and ahci
Date: Tue, 17 Jul 2012 16:50:45 +0100	[thread overview]
Message-ID: <20120717155045.GE18843@redhat.com> (raw)
In-Reply-To: <20120717154714.GE2463@redhat.com>

On Tue, Jul 17, 2012 at 11:47:14AM -0400, Jason Baron wrote:
> On Tue, Jul 17, 2012 at 09:31:46AM -0600, Eric Blake wrote:
> > > Update on q35 testing with various os's.
> > > 
> > > Linux
> > > -----
> > > -RHEL6.3 installs + runs 
> > > -Fedora 16 install + runs
> > > -Fedora 17 - squashfs errors 
> > >    running on already installed f17 seems ok.
> > 
> > Pardon my high-level question (I haven't been following q35 threads
> > closely), but I just looked at http://wiki.qemu.org/Features/Q35 for the
> > first time.  Am I correct that all we are doing is adding a new machine
> > model, but that it will still be possible to select the older machine
> > model for migration compatibility when migrating a guest in from an
> > older qemu?  Does libvirt need to do anything special to its generated
> 
> yes, right now its specified as -M pc_q35
> 
> > command line to specify the old vs. the new machine model?
> > 
> 
> The current command line I'm using something such as:
> 
> $ /usr/local/bin/qemu-system-x86_64  -name "f16" -M pc_q35 -m 1G -smp 4
> -hda ./f16.img --enable-kvm  -bios <path>/q35-seabios/out/bios.bin
> -acpitable file=<path>/q35-seabios/out/q35-acpi-dsdt.aml  -monitor stdio
> 
> So it might be nice to avoid the '-acpitable' flag. Perhaps, we can
> teach qemu to pull in the correct acpitable depending on the -M
> specification...

Absolutely, this requirement to set magic -bios and -acpitable params
when using '-M pc_q35' is really horrible. If QEMU requires a different
BIOS setup for this machine type, then it should just do the right
thing itself, since presumably it knows what it wants better than
libvirt or any other mgmt app does.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2012-07-17 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 15:31 [Qemu-devel] q35 and ahci Eric Blake
2012-07-17 15:47 ` Jason Baron
2012-07-17 15:50   ` Daniel P. Berrange [this message]
2012-07-18 13:34   ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2012-07-03 16:16 Jason Baron
2012-07-03 18:25 ` Alexander Graf
2012-07-03 18:38   ` Jason Baron
2012-07-03 18:41     ` Alexander Graf
2012-07-03 18:46       ` Jason Baron
2012-07-03 18:52         ` Alexander Graf
2012-07-03 20:37           ` Jason Baron
2012-07-03 20:54             ` Alexander Graf
2012-07-04  1:29               ` Jason Baron
2012-07-04  8:33                 ` Alexander Graf
2012-07-05 14:06                   ` Jason Baron
2012-07-05 15:07                     ` Alexander Graf
2012-07-20 15:27                       ` Jason Baron
2012-07-22  6:48                         ` Gleb Natapov

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=20120717155045.GE18843@redhat.com \
    --to=berrange@redhat.com \
    --cc=dallan@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jbaron@redhat.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).