From: "Daniel P. Berrange" <berrange@redhat.com>
To: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [libvirt] Bugs filed in the week for Upstream Qemu and Libvirt
Date: Wed, 10 Jul 2013 14:20:58 +0100 [thread overview]
Message-ID: <20130710132058.GO15655@redhat.com> (raw)
In-Reply-To: <51DD5E5C.8090505@linux.vnet.ibm.com>
On Wed, Jul 10, 2013 at 06:45:08PM +0530, chandrashekar shastri wrote:
> Hi,
>
> Below are bugs filed in this week for Upstream qemu and libvirt:
>
> Qemu in Launchpad:
>
> https://bugs.launchpad.net/opensuse/+bug/1199416
> Hot-add qcow2 [virtio-scsi] devices doesn't work in SlLES-11-SP2guest
>
> Libvirt Bugs:
>
> Bug 982224 - Attaching of the Virtio-scsi [qcow2] drives fails with
> "error: internal error No more available PCI addresses"
> Bug 982455 - RHEL Guest fails to boot after attaching 200+ scsi
> devices [virtio-scsi qcow2]
> Bug 980954 - Virtio-scsi drives in Windows7 shows yellow bang in
> device manager though virtio scsi pass through driver is installed
> Bug 982630 - Documentation : virsh attach-disk --help shouldbe
> updated with proper examples for --type and --driver
We really don't need lists of bugs emailed to the libvirt-list mailing
list. People already monitor bugzilla & have email alerts from bugzilla
as they desire.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2013-07-10 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 13:15 [Qemu-devel] Bugs filed in the week for Upstream Qemu and Libvirt chandrashekar shastri
2013-07-10 13:20 ` Daniel P. Berrange [this message]
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=20130710132058.GO15655@redhat.com \
--to=berrange@redhat.com \
--cc=cshastri@linux.vnet.ibm.com \
--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).