This bug was fixed in the package libvirt - 0.7.0-1ubuntu13.1
---
libvirt (0.7.0-1ubuntu13.1) karmic-proposed; urgency=low
* debian/patches/9093-lp460271.patch: require absolute path for dynamic
added files (LP: #460271)
* debian/patches/9094-lp453335.patch: suppress
** Tags added: verification-done
** Tags removed: verification-needed
--
apparmor blocks migration
https://bugs.launchpad.net/bugs/461528
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing
Accepted libvirt into karmic-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
--
This now works in 0.7.0-1ubuntu13.1:
$ virsh list
Connecting to uri: qemu:///system
Id Name State
--
1 testqemu-migrate running
$ ssh 192.168.122.3 virsh list
Connecting to uri: qemu:///system
Id Name State
** Also affects: libvirt (Ubuntu Lucid)
Importance: Medium
Assignee: Jamie Strandboge (jdstrand)
Status: In Progress
--
apparmor blocks migration
https://bugs.launchpad.net/bugs/461528
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package libvirt - 0.7.0-1ubuntu14
---
libvirt (0.7.0-1ubuntu14) lucid; urgency=low
* debian/patches/9093-lp460271.patch: require absolute path for dynamic
added files (LP: #460271)
* debian/patches/9094-lp453335.patch: suppress confusing and
SRU
Impact: migratino no longer works
Bug is addressed in Lucid by adding 'inet dgram' to the
usr.sbin.libvirtd profile
See comment #2
The regression potential is considered extremely low. It only allows
additional access the the profile previously denied.
--
apparmor blocks migration
** Changed in: libvirt (Ubuntu Karmic)
Status: In Progress = Fix Committed
** Changed in: libvirt (Ubuntu Lucid)
Milestone: karmic-updates = None
--
apparmor blocks migration
https://bugs.launchpad.net/bugs/461528
You received this bug notification because you are a member of Ubuntu
Just found a Bug #448674 with my situation. Posted there how to
reproduce.
--
apparmor blocks migration
https://bugs.launchpad.net/bugs/461528
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs
As for hostnames it works perfectly for jaunty, not for karmic.
In Jaunty live migration worked with:
listen_tls = 0
listen_tcp = 1
auth_tcp = none
in /etc/libvirt/libvirtd.conf
Worked in Jaunty:
# virsh --connect=qemu+tcp://node1/system migrate --live vm1
qemu+tcp://node2/system
hostnames
This bug is for the apparmor problem. There is another bug for
qemu+tcp:// being blocked by apparmor. Please file a new bug regarding
migration issues not related to apparmor (note, you may want to look at
the aforementioned redhat bug).
--
apparmor blocks migration
** Changed in: libvirt (Ubuntu Karmic)
Status: Triaged = In Progress
--
apparmor blocks migration
https://bugs.launchpad.net/bugs/461528
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs
Note that there are other migration issues as detailed in
https://bugzilla.redhat.com/show_bug.cgi?id=499750, however, once
hostnames are setup right, then migration should hopefully work in 9.10
(after the profile is updated).
** Bug watch added: Red Hat Bugzilla #499750
13 matches
Mail list logo
