Bug ID 998343
Summary libvirt fails to boot a KVM virtual machine, after having installed its OS
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.2
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Virtualization:Tools
Assignee virt-bugs@suse.de
Reporter hguo@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 691805 [details]
kvm host system journal

The host system is 42.2 beta running on bare metal.

I connect to its libvirtd via SSH from a 42.1 system, to install a 42.2 beta
guest virtual machine on KVM.

The installation process goes uneventfully, however when it is time to reboot
after installation, this libvirt "internal error" error shows up:

Sep 12 10:56:04 linux libvirtd[10836]: Unable to read from monitor: Connection
reset by peer
Sep 12 10:56:04 linux libvirtd[10836]: internal error: qemu unexpectedly closed
the monitor: 2016-09-12T08:56:04.217039Z qemu-system-x86_64: -drive
if=none,media=cdrom,id=drive-sata0-0-0,readonly=on,cache=unsafe: Must specify
either driver or file
Sep 12 10:56:04 linux virtlogd[11386]: End of file while reading data:
Input/output error
Sep 12 10:56:04 linux virtlogd[11386]: End of file while reading data:
Input/output error

The 42.1 virt-manager receives displays identical internal error message.

Further attempts to boot the guest VM occasionally results in a slightly
different, internal error message:
Sep 12 10:56:57 linux libvirtd[10836]: internal error: qemu unexpectedly closed
the monitor: nnel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice
port=5901,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,ma
                                       2016-09-12T08:56:56.947793Z
qemu-system-x86_64: -drive
if=none,media=cdrom,id=drive-sata0-0-0,readonly=on,cache=unsafe: Must specify
either driver or file

A workaround is to delete the guest VM and create a new guest VM using existing
disk image.

The complete system journal from host system is attached.


You are receiving this mail because: