All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	agraf@suse.de, afaerber@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 0/2] apic: bump emulated lapic version to 0x14
Date: Wed, 7 May 2014 17:02:42 +0300	[thread overview]
Message-ID: <20140507140242.GB14558@redhat.com> (raw)
In-Reply-To: <20140507134505.GB1655@ERROL.INI.CMU.EDU>

On Wed, May 07, 2014 at 09:45:06AM -0400, Gabriel L. Somlo wrote:
> On Wed, May 07, 2014 at 12:37:43PM +0200, Paolo Bonzini wrote:
> > So Gabriel what's left for OS X guests to run out of the box (with
> > the right key for -device applesmc of course)?
> 
> Once Gerd imports a new SeaBIOS blob, QEMU should be able to boot
> OS X "out of the box". Of course, there are stil some caveats:
> 
> 1. We still need the Chameleon bootloader (to work around EFI):
> 
> 	- by loading only its stage-2 component (named "boot")
> 	  via the "-kernel boot" command line option to QEMU
> 	  (this is how I'm starting it right now)
> 
> 	- by installing all of Chameleon to the guest disk image,
> 	  the way hackintoshes do (I haven't tried this, but thought
> 	  it's worth mentioning).
> 
> 2. e1000 flakiness:
> 
> 	- link negotiation is flaky (I have a patch, but was told
> 	  and agree that it morally belongs in the BIOS layer)

Could you remind me what the issue and the patch are?

> 	- Mavericks doesn't like the current e1000 model
> 	  (E1000_DEV_ID_82540EM); there was a patch sent to the list
> 	  to allow selecting among different e1000 models, I think
> 	  it was:
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2014-02/msg04411.html
> 
> 	  Mavericks likes E1000_DEV_ID_82545EM_COPPER, but Windows
> 	  won't work with that, so picking which model to use from
> 	  the command line would be nice. The patch seems abandoned
> 	  at this point, so I might contact the author and ask if
> 	  he minds me picking it up and continuing to polish it until
> 	  it's acceptable :)

Yay, please do that!

> 	- virtio-net works with an "aftermarket" driver, verified to
> 	  work both in MountainLion and Mavericks. It's what I'm using
> 	  right now.
> 
> AFAIK, that's everything :)

For older OSX we need the mwait nop hack right?
http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/kvm-mwait-nop-20140205.patch


> There's a GSoC student (Reza Jelveh) who will be working on trying
> booting OS X with OVMF (piix only for now).
> 
> I'm toying with the idea of maybe getting OVMF to work with Q35,
> but I have absolutely no idea yet how big of a job that might be,
> and whether I'm mentally equipped to tackle it myself, in my "spare time" :)
> 
> Last but not least, I keep a "current state of OS X on QEMU/KVM"
> writeup online at
> 
> http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/
> 
> so any new and interesting developments should show up there in a
> reasonably timely way...
> 
> Cheers,
> --Gabriel

  parent reply	other threads:[~2014-05-07 14:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 15:17 [Qemu-devel] [PATCH v6 0/2] apic: bump emulated lapic version to 0x14 Gabriel L. Somlo
2014-05-06 15:17 ` [Qemu-devel] [PATCH v6 1/2] pc: add compat_props placeholder for 2.0 machine type Gabriel L. Somlo
2014-05-06 15:17 ` [Qemu-devel] [PATCH v6 2/2] pic: use emulated lapic version 0x14 on pc machines >= 2.1 Gabriel L. Somlo
2014-05-06 17:54   ` Gabriel L. Somlo
2014-05-07  9:03 ` [Qemu-devel] [PATCH v6 0/2] apic: bump emulated lapic version to 0x14 Michael S. Tsirkin
2014-05-07 10:37   ` Paolo Bonzini
2014-05-07 13:45     ` Gabriel L. Somlo
2014-05-07 13:49       ` Paolo Bonzini
2014-05-07 14:02       ` Michael S. Tsirkin [this message]
2014-05-07 14:39         ` Gabriel L. Somlo
2014-05-07 15:05           ` Michael S. Tsirkin
2014-05-07 15:30             ` Paolo Bonzini

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=20140507140242.GB14558@redhat.com \
    --to=mst@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=gsomlo@gmail.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.