public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Pauline Middelink <middelink@polyware.nl>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-85 won't boot guests with virtio block device
Date: Sun, 26 Apr 2009 13:25:15 +0300	[thread overview]
Message-ID: <49F4368B.5070505@redhat.com> (raw)
In-Reply-To: <20090424171853.GA3798@polyware.nl>

Pauline Middelink wrote:
> Hi,
>
> To follow up on the issues with kvm-85 and libvirt I discovered the following
> issue: libvirt detects from the help of qemu which options it can give to
> qemu. (in this case obviously /usr/kvm/bin/qemu-system-x86_64 -help)
>
> If you look carefully to the output of the -help of qemu from kvm-84 and
> kvm-85, you will notice the boot flag to the -drive option has disappeared!
> Hence letting libvirt believe it isnt allowed to use it, hence the unable
> to boot error.
>
> A small patch which fixes the problem for me, is attached.
>
>   

It's missing the sacred signoff, can you add it please?

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2009-04-26 10:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 17:18 kvm-85 won't boot guests with virtio block device Pauline Middelink
2009-04-24 23:25 ` Marcelo Tosatti
2009-04-24 23:46   ` Anthony Liguori
2009-04-24 23:47     ` Anthony Liguori
2009-04-26 10:27     ` Avi Kivity
2009-04-25 20:13 ` Gerd v. Egidy
2009-04-26 10:25 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-27  7:57 Pauline Middelink
2009-04-27  9:00 ` Avi Kivity
2009-04-23 11:00 Darius Drozdowski
2009-04-23 12:05 ` Gerd v. Egidy
2009-04-23 12:40   ` Bernhard Held
2009-04-23 12:49     ` Alexey Eremenko
2009-04-23 13:27     ` Gerd v. Egidy
2009-04-23 13:49       ` Bernhard Held
2009-04-23 14:01         ` Gerd v. Egidy

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=49F4368B.5070505@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=middelink@polyware.nl \
    /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