Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=499698.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
This bug was fixed in the package libvirt - 0.6.1-0ubuntu5.1
---
libvirt (0.6.1-0ubuntu5.1) jaunty-proposed; urgency=low
* debian/patches/event-handling-fix-rh499698-lp362288.patch: cherry pick
from upstream; fixes critical, destructive bug whereby calling
'virsh destroy foo
Also confirming fixed with jaunty-proposed packages.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Branch linked: lp:ubuntu/jaunty-proposed/libvirt
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Confirmed fixed as well in jaunty-proposed.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Tags added: verification-done
** Tags removed: verification-needed
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
libvirt-bin=0.6.1-0ubuntu5.1 from jaunty-proposed passes the SRU test
case and acts as expected for me.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Accepted libvirt into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Okay, I've uploaded the package to jaunty-proposed.
Martin, could you take a look at that and accept it to -proposed at your
convenience?
There seems to be a lot of people experiencing this bug. Please, by all
means, help us test this package when it lands in -proposed.
:-Dustin
** Changed in:
** Changed in: libvirt (Ubuntu Jaunty)
Status: Triaged => In Progress
** Changed in: libvirt (Ubuntu Jaunty)
Milestone: None => jaunty-updates
** Changed in: libvirt (Ubuntu Jaunty)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
--
virsh destroy might also kill another run
Thanks Dustin for pushing this one.
Yes, I can confirm that Bryan's patched version fixes the issue for me. I
tested libvirt=0.6.1-0ubuntu6~btm2 from Bryan's PPA. I also confirm that the
problem is already fixed in karmic.
--
virsh destroy might also kill another running VM
https://bugs.launchp
** Also affects: libvirt (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Jaunty)
Status: New => Triaged
** Changed in: libvirt (Ubuntu Jaunty)
Importance: Undecided => Critical
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Rele
Thierry,
You originally reported this bug... Can you verify that Bryan's
proposed patch fixes the issue for you?
If so, I think we can move this SRU along.
:-Dustin
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification be
Setting importance to critical because this is such a destructive bug.
Awaiting Soren to continue the SRU process.
** Changed in: libvirt (Ubuntu)
Importance: Medium => Critical
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
--
virsh destroy might also kill another runni
Jaunty SRU Notes:
This bugs causes a second guest to be erroneously destroyed when the
user destroys a guest. Depending on the function of the second guest,
this can lead to unexpected data loss and service interruption and is
inherently very destructive.
Because this bug has been fixed upstream
Thank's Bryan! Patch is installed and works great (tested save, restore
and destroy) so far.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
There are a lot of patches in this package, so order matters a bit.
apt-get source libvirt=0.6.1-0ubuntu5
wget
http://launchpadlibrarian.net/29013416/event-handling-fix-rh499698-lp362288.patch
cd libvirt-0.6.1/
QUILT_PATCHES=debian/patches/ quilt push -a
QUILT_PATCHES=debian/patches/ quilt import
Excellent, thanks Bryan.
Ping me on IRC and I can walk you through the SRU process.
:-Dustin
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Bryan, I couldn't apply the event-handling-fix-rh499698-lp362288.patch
against libvirt_0.6.1-0ubuntu5 -
$ quilt push
Applying patch event-handling-fix-rh499698-lp362288.patch
patching file libvirt-0.6.1/qemud/event.c
Hunk #12 FAILED at 429.
Hunk #13 succeeded at 542 (offset -1 lines).
Hunk #14 suc
Upstream patch [1] was checked into source control [2] in 72dc6d +
0a31be + 37ede4, which are in libvirt v0.6.4. Current version of libvirt
in karmic is 0.6.4-1ubuntu2, so this bug should not be present in
karmic.
[1] https://bugzilla.redhat.com/attachment.cgi?id=343109
[2] git://git.et.redhat.com
Upstream patch [1] works against 0.6.1-0ubuntu5 on jaunty.
I'm attaching this patch converted to quilt sans the test code, it
applies fine as the last in the series.
Testers should grab libvirt=0.6.1-0ubuntu6~btm2 from my ppa [2].
Destroyed all guests and libvirt
Started libvirt
Started three gu
Michal Ingeli's http://launchpadlibrarian.net/27207697/lp-362288.patch";>patch
did not resolve the issue for me after converted by hand to quilt
(attached) and applied to the patch series in libvirt=0.6.1-0ubuntu5 on
jaunty.
Destroyed all guests and libvirt
Started libvirt
Started three guests
Des
Please note, that also a 'virsh save domain' destroys other domains. Any
updates here?
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
I'm trying to update the package with the patch, but debuild doesn't
work. This patch affects other.:
Patch event-loop-hang.diff does not apply
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member
Any updates ?
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
I don't see any updates to the libvirt package. Is this package updated,
or will it be soon?
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
this is not funny anymore. this issue should be fixed immediately.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
** Changed in: libvirt (Fedora)
Status: Fix Committed => Fix Released
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I can confirm, patch worked.
Attaching ported patch from fedora, if it's not already done.
** Attachment added: "patch ported from fedora"
http://launchpadlibrarian.net/27207697/lp-362288.patch
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You rec
** Changed in: libvirt (Fedora)
Status: Unknown => Fix Committed
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Also affects: libvirt (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=499698
Importance: Unknown
Status: Unknown
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubunt
has anyone confirmed if the fedora patch noted above actually works?
2009/5/22 Michal Ingeli
> Severity high, also according to upstream. This flaw makes libvirt
> practically unusable.
>
> --
> virsh destroy might also kill another running VM
> https://bugs.launchpad.net/bugs/362288
> You rece
I cannot find any feedback regarding the fedora fix noted by JH, has
been put into unstabletesting but no responders. Has anyone else tried
this? Will test tonight and feedback here and on bz
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received t
Severity high, also according to upstream. This flaw makes libvirt
practically unusable.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
You seriously mean that importance of this bug is medium?
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Upstream bug:
https://bugzilla.redhat.com/show_bug.cgi?id=499698
Looks like Fedora has a patch:
https://bugzilla.redhat.com/show_bug.cgi?id=499698#c7
** Bug watch added: Red Hat Bugzilla #499698
https://bugzilla.redhat.com/show_bug.cgi?id=499698
--
virsh destroy might also kill another runni
Interestingly, as Thierry pointed out, if I run 5 VMs
sec-(dapper|hardy|intrepid|jaunty|karmic)-i386, and start them in the
order I listed, and do 'virsh destroy sec-intrepid-i386', then only sec-
jaunty-i386 gets additionally destroyed. dapper, hardy and karmic all
stay up. I tried this several ti
** Attachment added: "jaunty.xml"
http://launchpadlibrarian.net/26681939/jaunty.xml
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
I too see this. Attached is the XML definitions for two affected
machines.
** Attachment added: "intrepid.xml"
http://launchpadlibrarian.net/26681761/intrepid.xml
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification beca
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs
I'm also experiencing this. This issue combined with a strange randomish
guest freezing problem (with a Debian Lenny guest) makes KVM unusable in
the Jaunty host for me.
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification b
Bolster: yes, I also experience that, however this is a different bug.
Could you please open a separate bug about it ? Thanks !
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Forgot to mention, same arch, same version of kvm and libvirt
0.6.1-0ubuntu4, tested scenarios listed above with and without guest
os's installed, all confirmed
--
virsh destroy might also kill another running VM
https://bugs.launchpad.net/bugs/362288
You received this bug notification because yo
Possibly related: when attempting to reboot vm's from the Virtual
Machine Manager windows causes this complaint:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 528, in
reboot_domain
vm.reboot()
File "/usr/share/virt-manager/virtManager/domain
44 matches
Mail list logo
