From: Dustin Kirkland <dustin.kirkland@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [libvirt] dynamic scsi disk attach seems to be broken in qemu(-kvm)-0.11, libvirt-0.7.1
Date: Fri, 9 Oct 2009 10:27:48 -0500 [thread overview]
Message-ID: <d9c105ea0910090827n17ae68a1oaff2b4ddb1725966@mail.gmail.com> (raw)
In-Reply-To: <4ACF4AFA.80804@codemonkey.ws>
On Fri, Oct 9, 2009 at 9:38 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>> I would like some advice on how to proceed with this bug, and where
>>> the solution lies...in qemu or in libvirt. Ultimately, I would like
>>> the behavior we had in our previous release with kvm-84 and
>>> libvirt-0.6.1, where we could dynamically add scsi devices without a
>>> problem, using:
>>> pci_add 1 storage file=/tmp/foo,if=scsi
>>>
>>> Can anyone else reproduce this? Is this considered a regression by
>>> anyone else? Where should I look to solve this, in libvirt, or in
>>> qemu?
>>>
>>
>> Independently of what I said about libvirt not implementing SCSI hotplug
>> with the right apporoach, the pci-add stuff should definitely work, so if
>> it doesn't then this is a regression that needs to be fixed
>>
>
> There's definitely a bug somewhere. When you add a second PCI controller,
> the controller shows up in the guest but the disk attached to the controller
> isn't visible. Rescanning the scsi bus does not make the disk appear
> either.
Okay, thanks for confirming this, Anthony.
I have added a task against upstream QEMU at:
* https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/432154
:-Dustin
next prev parent reply other threads:[~2009-10-09 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 3:57 [Qemu-devel] dynamic scsi disk attach seems to be broken in qemu(-kvm)-0.11, libvirt-0.7.1 Dustin Kirkland
2009-10-09 8:18 ` [Qemu-devel] Re: [libvirt] " Daniel P. Berrange
2009-10-09 14:38 ` Anthony Liguori
2009-10-09 15:27 ` Dustin Kirkland [this message]
2009-10-09 15:38 ` Dustin Kirkland
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=d9c105ea0910090827n17ae68a1oaff2b4ddb1725966@mail.gmail.com \
--to=dustin.kirkland@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@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).