Re: qemu-kvm problem - libvirtd won't start
On Sun, Nov 16, 2014 at 05:43:07PM -0500, Gary Dale wrote:
> I've been running a couple of virtual machines on a Wheezy/AMD64 server for
> a few years now. After the last reboot, I couldn't connect to them anymore.
> I can't get libvirtd to start on the server:
> [....] Starting libvirt management daemon: libvirtd/usr/sbin/libvirtd:
> error: unable to determine if daemon is running: No such file or directory
> The message looks a bit strange with the libvirtd at the top of the path.
> Checking the libvirt/libvirtd.log I see:
> 2014-11-16 20:19:11.010+0000: 5658: error : qemuMonitorIO:660 : internal
> error: End of file from monitor
> 2014-11-16 20:19:11.014+0000: 5658: error :
> virSecurityDACRestoreSecurityFileLabel:310 : cannot resolve symlink
> /dev/bus/usb/002/002: No such file or directory
Well, that is a big hint. Some entry in the /dev
directory is not there.
For example, in my system,
$ find /dev/bus/usb/
Those are dynamically generated by a subsystem called udev.
However, sayeth the log, symlinks that point to these are dead.
Not sure where to go with that....
Did you try starting the VMs directly using the qemu command?
> 2014-11-16 20:19:14.145+0000: 5658: error : virNetSocketReadWire:1453 : End
> of file while reading data: Input/output error
> I can't see anything much in syslog - nothing about libvirt(d) and only this
> about kvm:
> Nov 16 17:07:55 TheLibrarian kernel: [ 4.077661] kvm: Nested
> Virtualization enabled
> Nov 16 17:07:55 TheLibrarian kernel: [ 4.077665] kvm: Nested Paging
> It's a fairly vanilla Wheezy server setup, running NFS and CUPS but also
> Samba4 from the backports, and of course qemu-kvm.
> Any ideas anyone?
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject
> of "unsubscribe". Trouble? Contact email@example.com
> Archive: [🔎] 5469287B.firstname.lastname@example.org">https://lists.debian.org/[🔎] 5469287B.email@example.com