This bug was fixed in the package libvirt - 0.8.3-1ubuntu1
---
libvirt (0.8.3-1ubuntu1) maverick; urgency=low
* Merge from debian unstable with security fixes
* Fixes:
- LP: #588369
- LP: #585964
* Remaining changes:
- debian/control:
+ Build-Depends on qemu-kv
** Changed in: libvirt (Ubuntu)
Status: Triaged => In Progress
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubun
** Changed in: virt-manager (Ubuntu)
Status: New => Invalid
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Triaged
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubun
Restarting the libvirt daemon in addition to the above seems to have
cleared things up. I can now clone LVM backed VMs.
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team,
No, nothing.
Here is the full kern.log since the reload:
Aug 5 12:39:21 kvm-host kernel: [90351.748748] type=1505
audit(1281033561.731:23): operation="profile_replace" pid=7783
name="/usr/sbin/libvirtd"
Aug 5 12:46:07 kvm-host kernel: [90757.988390] lo: Disabled Privacy Extensions
Aug 5 13
Jamin, were there any other apparmor denied messages in kern.log after
you made the profile changes and tried again?
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team, whic
Made the requested apparmor change, checked the dmesg output before
attempting to clone the VM, found the following new entry:
[90351.748748] type=1505 audit(1281033561.731:23):
operation="profile_replace" pid=7783 name="/usr/sbin/libvirtd"
Looks good so far.
First attempt to clone the VM and se
Jamin, can you add the following to /etc/apparmor.d/usr.sbin.libvirtd:
capability fsetid,
Then do:
$ sudo apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.libvirtd
and report back if it resolves the issue for you.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Incomplete
--
does
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because
Rebooted the server and now I'm no longer getting the "Could not
determine original disk information: Disk '/dev/group/volume' does not
exist." error. However it fails to actually perform the cloning with the
following:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager
Jamin,
I suspect this is related to apparmour profile for libvirt. Do you see
messages in dmesg after attempting this ?
** Also affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
** Changed in: libvirt (U
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/53054416/Dependencies.txt
--
does not support cloning vm storage on lvm backend
https://bugs.launchpad.net/bugs/613549
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
12 matches
Mail list logo
