From: Avi Kivity <avi@redhat.com>
To: Bernhard Held <bheld@mgpi.de>
Cc: kvm@vger.kernel.org
Subject: Re: qemu-kvm-0.12 bug?
Date: Thu, 24 Dec 2009 16:26:59 +0200 [thread overview]
Message-ID: <4B337A33.1010104@redhat.com> (raw)
In-Reply-To: <4B329EA7.6070506@mgpi.de>
On 12/24/2009 12:50 AM, Bernhard Held wrote:
>>>> I've switched from -0.11.0 to -0.12 and from 2.6.31.6 to 2.6.32.2 to try
>>>> the new virtio-memory-API introduced in latest libvirt from git. I can
>>>> start VMs f.e. by kvm -cdrom $someiso --enable-kvm but my domain configs
>>>> to not work anymore.
>>>>
>>> Just found the other bug report about this....
>>>
>> Which solves this problem, but introduces the next. My VMs are stuck at boot,
>> after "SeaBIOS...gPXE" nothing happens.
>>
> Similar problem here with 0.12.1.1.
>
> I prefer to start my linux guests with -kernel, -append and -initrd.
> With this options qemu-kvm stuck at boot.
>
> Windows 2k8 or CDROM images work flawless.
>
> 0.12.0-rc2 didn't show this bug.
>
>
I just posted a fix for this. It will be included with 0.12.1.2 or 0.12.2.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-12-24 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 12:02 qemu-kvm-0.12 bug? Thomas Treutner
2009-12-22 12:25 ` Thomas Treutner
2009-12-23 15:05 ` Thomas Treutner
2009-12-23 22:50 ` Bernhard Held
2009-12-24 14:26 ` Avi Kivity [this message]
2009-12-24 17:01 ` Thomas Treutner
2009-12-29 10:33 ` Thomas Treutner
2009-12-29 10:36 ` Avi Kivity
2009-12-29 10:54 ` Thomas Treutner
2009-12-29 11:10 ` Avi Kivity
2009-12-29 11:48 ` [Qemu-devel] " Luiz Capitulino
2009-12-29 12:08 ` Thomas Treutner
2009-12-29 12:24 ` Luiz Capitulino
2009-12-30 9:36 ` Thomas Treutner
2009-12-29 12:11 ` Avi Kivity
2009-12-25 18:28 ` Bernhard Held
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=4B337A33.1010104@redhat.com \
--to=avi@redhat.com \
--cc=bheld@mgpi.de \
--cc=kvm@vger.kernel.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