| View previous topic :: View next topic |
| Author |
Message |
chrisk2305
Tux's lil' helper
Joined: 05 Sep 2007
Posts: 110
|
 Posted: Sun Jun 05, 2016 10:48 am Post subject: QEMU/KVM - VMs won't start anymore |
 |
|
Hi,
since my last world upgrade i am facing issues with my two KVM VMs. The will not start with this error message:
| Code: |
virsh
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list --all
Id Name State
----------------------------------------------------
- Windows7_BK_002 shut off
- Windows7_BK_002-clone shut off
virsh # start Windows7_BK_002
error: Failed to start domain Windows7_BK_002
error: internal error: process exited while connecting to monitor: 2016-06-05T10:47:24.058468Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
virsh #
|
And some more output from journalctl:
| Code: |
libvirtd[3082]: internal error: Failed to apply firewall rules /sbin/iptables -w --table nat --insert POSTROUTING --source 192.168.122.0/24 '!' --destination 192.168.122.0/24 --jump MASQUERADE: iptables v1.6.0: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Jun 05 12:51:06 fileserver kernel: device virbr0-nic left promiscuous mode
Jun 05 12:51:06 fileserver kernel: virbr0: port 1(virbr0-nic) entered disabled state
Jun 05 12:51:06 fileserver systemd-udevd[3258]: Process 'net.sh virbr0-nic stop' failed with exit code 1.
Jun 05 12:51:06 fileserver systemd-udevd[3261]: Process 'net.sh virbr0 stop' failed with exit code 1.
Jun 05 12:51:06 fileserver systemd[1]: Started Virtual machine log manager.
Jun 05 12:51:06 fileserver systemd-udevd[3267]: Process 'net.sh macvtap0 start' failed with exit code 1.
Jun 05 12:51:06 fileserver libvirtd[3082]: Domain id=1 name='Windows7_BK_002-clone' uuid=54aa4aad-c391-3b4e-dca7-394eb09728e1 is tainted: high-privileges
Jun 05 12:51:06 fileserver dbus[2973]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service'
Jun 05 12:51:06 fileserver systemd[1]: Created slice Virtual Machine and Container Slice.
Jun 05 12:51:06 fileserver systemd[1]: Starting Virtual Machine and Container Registration Service...
Jun 05 12:51:06 fileserver dbus[2973]: [system] Successfully activated service 'org.freedesktop.machine1'
Jun 05 12:51:06 fileserver systemd[1]: Started Virtual Machine and Container Registration Service.
Jun 05 12:51:06 fileserver systemd-machined[3277]: New machine qemu-1-Windows7BK002-clone.
Jun 05 12:51:06 fileserver systemd[1]: Started Virtual Machine qemu-1-Windows7BK002-clone.
Jun 05 12:51:06 fileserver libvirtd[3082]: Unable to read from monitor: Connection reset by peer
Jun 05 12:51:06 fileserver libvirtd[3082]: internal error: early end of file from monitor, possible problem: 2016-06-05T10:51:06.680498Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
Jun 05 12:51:06 fileserver virtlogd[3264]: libvirt version: 1.3.4
Jun 05 12:51:06 fileserver virtlogd[3264]: hostname: fileserver
Jun 05 12:51:06 fileserver virtlogd[3264]: End of file while reading data: Input/output error
Jun 05 12:51:06 fileserver virtlogd[3264]: End of file while reading data: Input/output error
Jun 05 12:51:06 fileserver systemd-machined[3277]: Machine qemu-1-Windows7BK002-clone terminated.
Jun 05 12:51:06 fileserver systemd-udevd[3288]: Process 'net.sh macvtap0 stop' failed with exit code 1.
Jun 05 12:51:06 fileserver libvirtd[3082]: Failed to autostart VM 'Windows7_BK_002-clone': internal error: early end of file from monitor, possible problem: 2016-06-05T10:51:06.680498Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
Jun 05 12:51:06 fileserver systemd-udevd[3293]: Process 'net.sh macvtap0 start' failed with exit code 1.
Jun 05 12:51:06 fileserver libvirtd[3082]: Domain id=2 name='Windows7_BK_002' uuid=bd54ef90-d454-63d8-a68d-2e882e2a40c5 is tainted: high-privileges
Jun 05 12:51:06 fileserver systemd-machined[3277]: New machine qemu-2-Windows7BK002.
Jun 05 12:51:06 fileserver systemd[1]: Started Virtual Machine qemu-2-Windows7BK002.
Jun 05 12:51:06 fileserver systemd-machined[3277]: Machine qemu-2-Windows7BK002 terminated.
Jun 05 12:51:06 fileserver libvirtd[3082]: Unable to read from monitor: Connection reset by peer
Jun 05 12:51:06 fileserver libvirtd[3082]: internal error: early end of file from monitor, possible problem: 2016-06-05T10:51:06.768353Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
Jun 05 12:51:06 fileserver libvirtd[3082]: internal error: process exited while connecting to monitor: 2016-06-05T10:51:06.768353Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
Jun 05 12:51:06 fileserver virtlogd[3264]: End of file while reading data: Input/output error
Jun 05 12:51:06 fileserver virtlogd[3264]: End of file while reading data: Input/output error
Jun 05 12:51:06 fileserver systemd-udevd[3312]: Process 'net.sh macvtap0 stop' failed with exit code 1.
Jun 05 12:51:06 fileserver libvirtd[3082]: Failed to autostart VM 'Windows7_BK_002': internal error: process exited while connecting to monitor: 2016-06-05T10:51:06.768353Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
|
The mountpoint exists of course. I don't know how to debug from here.
Any help is appreciated.
Thanks
Christian |
|
| Back to top |
|
 |
Perfect Gentleman
Veteran
Joined: 18 May 2014
Posts: 1248
|
| Posted: Sun Jun 05, 2016 1:00 pm Post subject: |
|
|
| Code: | error: internal error: process exited while connecting to monitor: 2016-06-05T10:47:24.058468Z qemu-system-x86_64: -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file
|
|
|
| Back to top |
|
|
chrisk2305
Tux's lil' helper
Joined: 05 Sep 2007
Posts: 110
|
| Posted: Sun Jun 05, 2016 1:13 pm Post subject: |
|
|
well, the files are there 
EDIT: I had indeed Problems with the Raid1 where the files are stored on. So I copied them to another disk and linked the vm files to the original folder. Same error. Please advise. |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3131
|
| Posted: Thu Jun 09, 2016 8:39 pm Post subject: |
|
|
| Quote: | | -drive if=none,id=drive-ide0-1-0,readonly=on,cache=none: Must specify either driver or file |
I don't see drive image there either.
The invocation is broken.
E.g. I call qemu with params like
| Quote: | | -drive file=./drive1.img,cache=none |
(of course it's far from the full list) |
|
| Back to top |
|
|
chrisk2305
Tux's lil' helper
Joined: 05 Sep 2007
Posts: 110
|
| Posted: Fri Jun 10, 2016 12:12 pm Post subject: |
|
|
| I could fix the issue by recreating the VMs and by adding the exisiting disks. I have no idea what the inital problem was. |
|
| Back to top |
|
|
mprivozn
n00b
Joined: 31 Jul 2016
Posts: 3
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
