[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
Sorry, we no longer have that server.. too many problems, kvm+libvirt
ended up getting replaced with ESXi...
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you
@Chris: Any news on this ?
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
The only KVM hardware I have access to at the moment is a production
server. Upgrading it to lucid - which is still in beta - is not really
feasible at the moment.
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
Chris asked:
has anyone ever actually tested a qemu:///session VM before? It seems odd
that this code could ever get released.
Actually, I'm running kvm/libvirt/virt-manager right now, with
qemu:///session and I'm running a Lucid guest just fine.
My xml is attached.
Can you reproduce this in
from strace:
futex(0x80cde0, FUTEX_WAIT_PRIVATE, 2, NULL11:38:23.962: error :
qemudInitCpus:1243 : failed to set CPU affinity: Operation not permitted
libvir: QEMU error : failed to set CPU affinity: Operation not permitted
qemudInitCpus:1243 does:
if (sched_setaffinity(vm-vcpupids[i],
That qemudInitCpus function is from src/qemu_driver.c : 1243
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Ok, I was really looking for the dmesg to make sure that AppArmor wasn't
the cause, but your analysis demonstrates it is not. Marking confirmed.
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
** Changed in: libvirt
Chris, can you run the following command:
$ apport-collect 535147
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
libvirtd can't start qemu:///session domain - failed to set CPU
** Tags added: kernel-series-unknown
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
** Tags removed: kernel-series-unknown
--
libvirtd can't start qemu:///session domain - failed to set CPU affinity:
Operation not permitted
https://bugs.launchpad.net/bugs/535147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
11 matches
Mail list logo
