[ovirt-devel] VM won't start because of -incoming flag after upgrading to alpha-2

[Francesco Romani]

----- Original Message -----
> From: "Christopher Pereira" <kripper at imatronix.cl>
> To: "Doron Fediuck" <dfediuck at redhat.com>, "Francesco Romani" <fromani at redhat.com>
> Cc: devel at ovirt.org, "Roy Golan" <rgolan at redhat.com>
> Sent: Tuesday, July 7, 2015 12:07:20 PM
> Subject: Re: [ovirt-devel] VM won't start because of -incoming flag after upgrading to alpha-2
> 
> 
> On 07-07-2015 6:59, Doron Fediuck wrote:
> > On 07/07/15 12:50, Christopher Pereira wrote:
> >>
> >> Well, something is triggered it.
> >> I will send you the logs right now.
> >>
> >
> > According to libvirt docs, this is an internal flag, which is not
> > exposed to the user-
> > http://wiki.libvirt.org/page/QEMUSwitchToLibvirt#-incoming
> >
> > Can you please provide the libvirt log?
> >

> 2015-07-07 05:31:32.792+0000: starting up
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name test-vm -S -machine
> rhel6.5.0,accel=kvm,usb=off -cpu Nehalem -m 4096 -realtime mlock=off
> -smp 1,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
> 8c9437e4-5514-4c85-a52b-da33d9ab6061 -smbios
> type=1,manufacturer=oVirt,product=oVirt
> Node,version=7-1.1503.el7.centos.2.8,serial=32393735-3733-5355-4532-303957525946,uuid=8c9437e4-5514-4c85-a52b-da33d9ab6061
> -no-user-config -nodefaults -chardev
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/test-vm.monitor,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc
> base=2015-07-07T02:31:32,driftfix=slew -global
> kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on
> -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
> virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device
> virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5
> -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device
> ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive
> file=/rhev/data-center/1963d7ab-a65b-4a70-8749-f45aceba2393/ebd94ac1-84df-47da-be87-ca49f7bffdcf/images/7fba2829-772b-43e0-9d47-0b164b2ac975/7b2102e5-5f97-4185-9c71-618187c6dee9,if=none,id=drive-virtio-disk0,format=qcow2,serial=7fba2829-772b-43e0-9d47-0b164b2ac975,cache=none,werror=stop,rerror=stop,aio=threads
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
> -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=30 -device
> virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:16:01:54,bus=pci.0,addr=0x3
> -chardev
> socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/8c9437e4-5514-4c85-a52b-da33d9ab6061.com.redhat.rhevm.vdsm,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm
> -chardev
> socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/8c9437e4-5514-4c85-a52b-da33d9ab6061.org.qemu.guest_agent.0,server,nowait
> -device
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0
> -chardev spicevmc,id=charchannel2,name=vdagent -device
> virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0
> -spice
> port=5900,tls-port=5901,addr=0,disable-ticketing,x509-dir=/etc/pki/vdsm/libvirt-spice,seamless-migration=on
> -vnc 0:2 -device
> qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,vgamem_mb=16,bus=pci.0,addr=0x2
> -incoming fd:26

This means the VM is "migrating from file", aka resuming after a suspension.
Any chance the VM was suspended while running some QEMU version and resumed using a different QEMU version?

> --- Starting via virsh define + start (from a dump) ---
[snip]

OK, so new boot and no resume, this explains why it starts OK.

Bests,

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani