libvirtd crashes when adjusting cpu's for guest in virt-manager.

Bug #379176 reported by Robstarusa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virt-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hello,

I am running the latest libvirtd + virt-manager available in Jaunty. If I try to adjust # of cpu's down while the guest is off & click apply, this apparently crashes libvirtd.

If I xkill virt-manager, and restart it, it can't connect to libvirtd. if I run /etc/init.d/libvirt-bin stop, it doesn't kill libvirtd either. If I kill -9 the PID of libvirtd, and run /etc/init.d/libvirt-bin start, libvirtd comes back alive.

My workaround is to close virt-manager, adjust the # of cpus in /etc/libvirt/qemu/hostname.xml and then start virt-manager.

Now the correct desired # of cpu's appears.

My machine is running 64-bit jaunty with 4G ram and 2 * xeon 5520's in a dell T7500.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for reporting this issue.

This issue has been fixed in the more recent version of libvirt in Karmic and Lucid.

Changed in virt-manager (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.