qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>
Subject: [Qemu-devel] Re: start qemu failed with --enable-kvm -vga std
Date: Wed, 08 Apr 2009 18:34:26 +0200	[thread overview]
Message-ID: <49DCD212.5050200@siemens.com> (raw)
In-Reply-To: <5d6222a80904080625k4aa8186fo451772b70509f595@mail.gmail.com>

Glauber Costa wrote:
> On Wed, Apr 8, 2009 at 10:12 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> Peng Huang wrote:
>>> Hi,
>>>
>>> The HEAD version qemu can not execute a VM with --enable-kvm -vga std or
>>> -vga vmware on kernel 2.6.29.1-46.fc11.x86_64. I found it is because of qemu
>>> call cpu_register_physical_memory with a wrong size. Below patch can fix it
>>> on my box. Please test it.
>> Glauber came up with a similar patch for kvm-userspace and is currently
>> attempting to root cause the issue.
> 
> I believe this is in fact the root cause. KVM slot management code
> probably require
> memory to be page aligned. By trying to register a region that is not
> page aligned,
> the ioctl may fail. I, however, did not see this happening in qemu
> upstream (only kvm-userspace),
> and have absolutely no idea about why. But the patch makes perfect sense to me.
> 

But this really sounds like a limitation that should better be fixed in
the kvm layer, not the device/machine code.

We only map ROM regions here. So rounding them up/down and sending
properly aligned requests to the kernel should finally have the same
result for all involved pages. Only if non-compatible regions overlap
due to such roundings, we should bail out - and start to consider
changing device code.

My next free time slot is reserved now for the anyway required
enhancement of kvm's slot management in qemu. kvm-userspace could catch
up afterwards (finally fixing its broken text console after reset...).

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-04-08 16:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  3:11 [Qemu-devel] start qemu failed with --enable-kvm -vga std Peng Huang
2009-04-08 12:27 ` Paul Brook
2009-04-08 13:12 ` Anthony Liguori
2009-04-08 13:25   ` Glauber Costa
2009-04-08 16:34     ` Jan Kiszka [this message]
2009-04-08 16:41       ` [Qemu-devel] " Glauber Costa
2009-04-08 17:02         ` Jan Kiszka
2009-04-08 17:06           ` Glauber Costa
2009-04-08 17:20             ` Jan Kiszka
2009-04-08 17:23               ` Glauber Costa
2009-04-08 17:25               ` Glauber Costa
2009-04-08 17:39                 ` M. Warner Losh
2009-04-08 17:44                   ` Glauber Costa
2009-04-08 17:57                     ` M. Warner Losh
2009-04-08 17:47                   ` Paul Brook
2009-04-08 18:07                     ` Glauber Costa
2009-04-08 18:58                 ` Anthony Liguori
2009-04-08 18:57               ` Anthony Liguori
2009-04-08 19:03                 ` Glauber Costa
2009-04-08 17:31       ` Paul Brook

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=49DCD212.5050200@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=glommer@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).