I confirm that fix (libvirt 1.2.2-0ubuntu13.1.10) works. The bug is
fixed in libvirt from trusty-proposed. Thank you!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.10
---
libvirt (1.2.2-0ubuntu13.1.10) trusty-proposed; urgency=medium
* 9035-qemu-snapshot-save-persistent-domain-config: upstream fix for a
regression where persistent domain config was not saved after an external
This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.10
---
libvirt (1.2.2-0ubuntu13.1.10) trusty-proposed; urgency=medium
* 9035-qemu-snapshot-save-persistent-domain-config: upstream fix for a
regression where persistent domain config was not saved after an external
Can someone please verify this fix soon? Otherwise we will abort this
so we can proceed with other SRUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh
@sirswa,
could you please verify this fix works for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
passthrough
HI Serge
I will test it out at one of the spare node.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
passthrough
To
Hello sirswa, or anyone else affected,
Accepted libvirt into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@serge,
Yes, I am on Trusty and the Cloud Archive version (openstack juno for us).
I'll deploy it to one server and see how it looks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
** Description changed:
+
+ SRU Justification:
+ 1. Impact: virsh save fails when cpu mode is passthrough
+ 2. Test case: create a VM with cpu mode='host-passthrough' (see below for
an example). Run
+ virsh managed save
I was able to take the PPA libvirt (1.2.2-0ubuntu13.1.10~ppa1) package
for Trusty and upgrade libvirt (and associated packages). I restarted
nova-compute (since I'm on Openstack).
After checking both apparmor_status before and after (ensuring it was
enforcing and loaded), it appears it was
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
@tlink,
Would you mind opening a new high priority bug for your issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
@serge,
I after some review, I don't think it may be the same bug . I saw the
failure for 'virsh managedsave' and presumed it was for the same.
Apologies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@tlink,
that patch looks nothing like the one posted in comment #4. That one is
rather a subset of commit adff345e1ec9a6f528731ae40168a76b8e7620e0.
Could you please verify that you're talking about the same bug?
Could you check whether the package built for trusty in ppa:serge-
hallyn-virt
Were you able to SRU it? We are in desperate need here
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
passthrough
To
I'm not sure what comment #20 was about - the fix analogous to the
attached patch is adff345e1ec9a6f528731ae40168a76b8e7620e0 (which is
upstream).
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance:
I've uploaded a test package to ppa:serge-hallyn/virt. Could you please
test whether that fixes the issue for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh
I'm not sure what comment #20 was about - the fix analogous to the
attached patch is adff345e1ec9a6f528731ae40168a76b8e7620e0 (which is
upstream).
** Also affects: libvirt (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance:
@vachon,
the original bug report was about cloud archive versions. Which version
are you looking for the fix to be in? I will push a test package for
trusty so you can verify that the fix actually suffices, but I can't yet
do the SRU as we're waiting for anohter version to clear from trusty-
This bug is a show stopper for us as well. Juno/Utopic and we can't take
snapshots.
Appears there's a fix here:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=de0aeafe9ce3eb414c8b5d3aa8995d776a2952de
root@s# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
This is fixed upstream by commit dd69a14f. It will be included in the
next merge into vivid, and I'll SRU it into Trusty hopefully next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Any update here? This is a massive blocker to nova-compute for us, it
breaks all glance snapshots and even some reboots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and
May I know if the patched has been discussed upstream and which version
will include the patch?
for a workaround(from our colleague), we have included cpu model name in
/usr/share/libvirt/cpu_map.xml base on the information we got from
/proc/cpuinfo and virsh capabilities
regards,
--
You
This bug still present in libvirt 1.2.2. And patch has not been
discussed upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu
Quoting s10 (1262...@bugs.launchpad.net):
This bug still present in libvirt 1.2.2. And patch has not been
discussed upstream.
Why has the patch not been discussed upstream? In general while we are
happy to take important patches which are not yet in a release, we
want them to be at least
Serge's package does not include Vlad's patch.
We need a package with Vlad's patch in it so it can be tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh
Has this patch been discussed upstream? I'm surprised it is not in
1.2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
If I understand correctly, the new libvirt version I just pushed should
fix this bug. Please re-mark Confirmed if I am wrong and more patches
are needed.
status: fixreleased
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because
I'm sorry, this was the wrong bug!
status: triaged
** Changed in: libvirt (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1262641
If I understand correctly, the new libvirt version I just pushed should
fix this bug. Please re-mark Confirmed if I am wrong and more patches
are needed.
status: fixreleased
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because
Serge, sorry if I've missed an obvious answer to this... but, where did
you push the updated libvirt?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave
libvirt | 1.2.1-0ubuntu4 | trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave failed with cpu mode = host-
passthrough
To manage
Oh I see: https://launchpad.net/ubuntu/+source/libvirt/1.2.1-0ubuntu4
We really need a package compatible with Precise to fix this. We may be
able to test the fix if we can cherry-pick the trusty version of libvirt
without conflict, however we'll still require a backport to fix this in
I'm sorry, this was the wrong bug!
status: triaged
** Changed in: libvirt (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save
Unfortunately, in libvirt 1.2.1-0ubuntu4 this bug still exists. And I
don't realize how the patch that enables host-passthrough for
ARM/AArch64 (not amd64) can fix this bug for other architectures (i386,
amd64, powerpc etc).
--
You received this bug notification because you are a member of
Quoting s10 (1262...@bugs.launchpad.net):
Unfortunately, in libvirt 1.2.1-0ubuntu4 this bug still exists. And I
don't realize how the patch that enables host-passthrough for
ARM/AArch64 (not amd64) can fix this bug for other architectures (i386,
amd64, powerpc etc).
Yes, I commented that in
I am now thoroughly confused... so, we should try Vlad's patch and
ignore Serge's updated package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh managedsave
There is patch to workaround for this bug, that also fixes similar error
after live migration of vm with cpu mode host-passthrough.
** Patch added: dont-fail-without-cpu-model.patch
The attachment dont-fail-without-cpu-model.patch seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
In the libvirtd.log, all I see is
2013-12-24 17:05:23.406+: 1286: error :
virSecurityDACRestoreSecurityFileLabel:307 : cannot resolve symlink
/tmp/tmp1LJkjq/device_disk.img: No such file or directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, I attached that comment to the wrong bug.
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
virsh save and virsh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262641
Title:
44 matches
Mail list logo
