Thanks for the info... I attempted a service libvirtd stop (which fails since it isn't running) a service libvirtd start says OK but the status remains the same: libvirtd dead but subsys locked so I did a service libvirtd stop and then ran it manually and got the following: 15:03:59.798: error : No vport operation path found for host1 15:03:59.801: error : No vport operation path found for host2 15:03:59.802: error : No vport operation path found for host3 15:03:59.803: error : No vport operation path found for host4 15:03:59.872: error : No vport operation path found for host6 15:03:59.880: error : No vport operation path found for host5 15:03:59.892: error : No vport operation path found for host0 I have no idea what these errors mean.... does each host entry mentioned above correspond to a xen guest? weirdness..... Thanks again Denny Snyder Systems Engineer IT@Johns Hopkins 5801 Smith Ave Suite 3110C Baltimore, MD 21209 (410) 735-7613: DESK (410) 735-4660: FAX On 10/21/2009 02:55 PM, Daniel P. Berrange wrote:
Tis means the libvirtd isn't running
'service libvirtd status' shows: libvirtd dead but subsys locked
And this obviously confirms it. Yeah its very odd that this is related.
At least if you do 'service libvirtd stop' to clear the dead PID file, and then 'service libvirtd start' it should hopefully be back to normal. If it still crashes, then best to try running /usr/sbin/libvirtd manually, or under gdb/valgrind and capture a trace
Once libvirtd is running you can disable virbr0 with
virsh net-destroy default virsh net-autostart --disable default
which will stop 'virbr0' running / being created - its only required if you want to use NAT, not for bridging
Regards, Daniel