libvirtd becomes unresponsive on setvcpus
Bug #379415 reported by
jetole
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Ubuntu 9.04 AMD64 Server edition
0.6.1-0ubuntu5
When running windows xp pro as a VM on qemu/kvm via dual cpu intel E5540 and issuing a command the command `virsh setvcpus winxp1 1` on a dual vcpu vm, I get the response "Connecting to uri: qemu:///system" which seems to last indefinitely. My VM becomes unresponsive and and that same message appears on all following virsh commands. Restarting /etc/init.
Changed in libvirt (Ubuntu): | |
importance: | Undecided → Medium |
To post a comment you must log in.
Confirmed on two Jaunty servers. (Guest is also Jaunty here)
There are two methods to recreate this:
- virsh setvcpus
- change vcpus with virt-manager (after pressing 'apply', virt-manager will become unresponsive too.)