All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15
Date: Wed, 07 Dec 2011 11:11:20 +0400	[thread overview]
Message-ID: <4EDF1198.6080704@msgid.tls.msk.ru> (raw)
In-Reply-To: <4EDE854B.6070204@web.de>

On 07.12.2011 01:12, Jan Kiszka wrote:
> On 2011-12-06 21:58, Jan Kiszka wrote:
[]
>> How embarrassing. Messed something up, maybe during rebase, and forgot
>> to retest non-irqchip mode. Will fix and repost.
> 
> Was even worse, a simple -ENOTTESTED case. Pushed an update at the same
> location.

Ok, with the updated series everything works correctly.
Guests boots, qemu does not segfault at startup anymore,
WinXP with StdPC HAL works, even coroutines on mixed
32/64 environment breaks exactly the same way as with
qemu-kvm/master ;)

Tested both -enable-kvm and -machine pc,accel=kvm,kernel_irqchip=on -
both behaves equally (I wasnt' able to spot a difference).

What is the "target" syntax -- I assume it is the more verbose
one, with -machine, so that -enable-kvm will be dropped at some
point, right?

Thanks!

/mjt

  reply	other threads:[~2011-12-07  7:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05  9:21 winXP "Standard PC" HAL and qemu-kvm >= 0.15 Michael Tokarev
2011-12-05 13:28 ` Avi Kivity
2011-12-05 20:19   ` Michael Tokarev
2011-12-06 10:32     ` Avi Kivity
2011-12-06 11:02       ` Michael Tokarev
2011-12-06 12:27         ` Michael S. Tsirkin
2011-12-06 12:27           ` [Qemu-devel] " Michael S. Tsirkin
2011-12-06 14:45           ` Michael Tokarev
2011-12-06 14:45             ` [Qemu-devel] " Michael Tokarev
2011-12-06 16:29             ` Michael Tokarev
2011-12-06 16:29               ` Michael Tokarev
2011-12-06 16:38               ` Jan Kiszka
2011-12-06 16:38                 ` [Qemu-devel] " Jan Kiszka
2011-12-06 16:57                 ` Michael Tokarev
2011-12-06 16:57                   ` [Qemu-devel] " Michael Tokarev
2011-12-06 17:45                   ` Jan Kiszka
2011-12-06 17:45                     ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:13                   ` Michael Tokarev
2011-12-06 18:13                     ` [Qemu-devel] " Michael Tokarev
2011-12-06 18:21                     ` Jan Kiszka
2011-12-06 18:21                       ` [Qemu-devel] " Jan Kiszka
2011-12-06 18:45                       ` Michael Tokarev
2011-12-06 18:45                         ` [Qemu-devel] " Michael Tokarev
2011-12-06 19:38                         ` Michael Tokarev
2011-12-06 19:38                           ` [Qemu-devel] " Michael Tokarev
2011-12-06 20:58                           ` Jan Kiszka
2011-12-06 20:58                             ` [Qemu-devel] " Jan Kiszka
2011-12-06 21:12                             ` Jan Kiszka
2011-12-06 21:12                               ` [Qemu-devel] " Jan Kiszka
2011-12-07  7:11                               ` Michael Tokarev [this message]
2011-12-07  9:02                       ` Kevin Wolf
2011-12-07  9:02                         ` [Qemu-devel] " Kevin Wolf
2011-12-07  9:31                         ` Michael Tokarev
2011-12-07  9:31                           ` Michael Tokarev

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=4EDF1198.6080704@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.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 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.