From: Gerd Hoffmann <kraxel@redhat.com>
To: Jason Baron <jbaron@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
somlo@cmu.edu, qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update
Date: Tue, 04 Dec 2012 16:37:51 +0100 [thread overview]
Message-ID: <50BE18CF.7070704@redhat.com> (raw)
In-Reply-To: <20121204143725.GA11368@redhat.com>
Hi,
>>> '-machine q35,diskmode=ahci,ide,raid'?
>>
>> I'm wondering whenever we want to deal with that at all?
>>
>> "If your guest is too old to handle ahci natively, just stick to piix."
>> is a sensible policy IMHO.
>>
>
> There was some discussion of trying to make q35 the default for 1.4, in
> which case it may be important to support older OS's such as WinXP.
>
> Anthony, do you have any opinion on this?
The fundamental issue is that you have either good compatibility (makes
old guests happy) or good performance (makes modern guests happy) by
default. Picking a default which makes everybody happy is impossible.
That problem doesn't change no matter whenever the choice is piix vs.
q35 or q35+ide vs. q35+ahci.
management apps (using libosinfo) can tackle this in a sensible manner
by picking virtual hardware depending on the guest capabilities. So I
wouldn't worry too much on qemu level.
>>> 2) HPET ACPI error
>>>
>>> This line: 'IRQNoFlags () {2, 8}' in the HPET acpi table is causing the
>>> folloing ACPI message (removing it makes it go away):
>>
>> Hmm. That was added to make macos x happy and is also present on real
>> hardware, so I'm wondering what is going on here.
>>
>
> I also noticed that on Windows 7, the 'IRQNoFlags' line above makes the RTC
> clock complain that it does not have resources available. While removing the
> above line, removes that error.
Hmm. The IRQNoFlags for the RTC isn't new though, but I can see that
with win7 on piix too.
cheers,
Gerd
next prev parent reply other threads:[~2012-12-04 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 10:11 [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 1/3] seabios: update to 3d11108f45818d75140530a184c05680f1be51ad Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 2/3] configure: also symlink *.aml files Gerd Hoffmann
2012-12-03 10:11 ` [Qemu-devel] [PATCH 3/3] acpi: autoload dsdt Gerd Hoffmann
2012-12-03 18:47 ` [Qemu-devel] [PULL for-1.3 0/3] seabios: q35 update Jason Baron
2012-12-04 7:40 ` Gerd Hoffmann
2012-12-04 7:46 ` Jan Kiszka
2012-12-04 14:37 ` Jason Baron
2012-12-04 15:37 ` Gerd Hoffmann [this message]
2012-12-04 15:57 ` Gerd Hoffmann
2012-12-04 14:42 ` Gabriel L. Somlo
2012-12-04 15:11 ` jbaron
2012-12-04 15:39 ` Gabriel L. Somlo
2012-12-04 16:56 ` Gerd Hoffmann
2012-12-04 17:14 ` Gabriel L. Somlo
2012-12-05 6:50 ` Gerd Hoffmann
2012-12-05 14:49 ` Gabriel L. Somlo
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=50BE18CF.7070704@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=jbaron@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
/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).