after running yum upgrade, KVM vm's wont boot

Latest response

can anyone help me...

CASE 01861675
- readhat support can't help me due to self support subscription

after running yum upgrade, KVM vm's wont boot
Red Hat Enterprise Linux 7.2
Filed on Jun 02 2017 01:39:01 AM +10:00 by Rodney Sheppard

KVM vm's won't boot
after yum upgrade and reboot
machine is
Linux mon7.transmit 3.10.0-514.21.1.el7.x86_64 #1 SMP Sat Apr 22 02:41:35 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux

after restoring a snapshot of host to before the yum upgrade
the qem-kvm VM will boot again
if I then run yum update
the KVM VM stops booting

screen shot attached of where the boot gets stuck
creating a new VM has the same problem

/var/log/libvirt/qemu/rhel56t21.log...

2017-06-25 10:06:24.504+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (Red Hat, Inc. http://bugzilla.redhat.com/bugzilla, 2017-05-04-06:48:37, x86-034.build.eng.bos.redhat.com), qemu version: 1.5.3 (qemu-kvm-1.5.3-126.el7_3.9), hostname: mon7.transmit
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name rhel56t21 -S -machine pc-i440fx-rhel7.0.0,accel=tcg,usb=off -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid e1ab508b-32c0-467b-821a-b8780cb4a161 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-7-rhel56t21/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=on,strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -drive file=/u/vm/rhel56t21,format=raw,if=none,id=drive-virtio-disk0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=26,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:cc:82:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -spice port=0,disable-ticketing,image-compression=off,seamless-migration=on -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=1 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
char device redirected to /dev/pts/1 (label charserial0)
char device redirected to /dev/pts/2 (label charserial1)
((null):4795): SpiceWorker-Warning **: red_worker.c:1306:validate_surface: canvas address is 0x7f624e8ea308 for 0 (and is NULL)

((null):4795): SpiceWorker-Warning **: red_worker.c:1307:validate_surface: failed on 0
((null):4795): SpiceWorker-Warning **: red_worker.c:1308:validate_surface: condition !worker->surfaces[surface_id].context.canvas' reached
((null):4795): SpiceWorker-Warning **: red_worker.c:153:rendering_incorrect: rendering incorrect from now on: dev_destroy_primary_surface
((null):4795): SpiceWorker-Warning **: red_worker.c:9696:red_create_surface: conditionsurface->context.canvas' reached
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.157000 ms, bitrate 35310344827 bps (33674.568965 Mbps)
((null):4795): Spice-Warning **: red_channel.c:542:red_channel_client_send_ping: getsockopt failed, Operation not supported
red_dispatcher_set_cursor_peer:
inputs_connect: inputs channel client create

((null):4795): Spice-Warning **: red_channel.c:542:red_channel_client_send_ping: getsockopt failed, Operation not supported

The problem seems to be similar too.
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1492621

howvere, ifconfig has
[root@mon7 qemu]# ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
ether 02:42:b2:ee:08:4d txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.100.100.172 netmask 255.255.255.0 broadcast 192.100.100.255
inet6 fe80::a00:27ff:febd:b165 prefixlen 64 scopeid 0x20
ether 08:00:27:bd:b1:65 txqueuelen 1000 (Ethernet)
RX packets 666076 bytes 103642068 (98.8 MiB)
RX errors 0 dropped 10 overruns 0 frame 0
TX packets 823044 bytes 1923642331 (1.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 292074 bytes 988848596 (943.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 292074 bytes 988848596 (943.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:6c:fb:ad txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:6c:fb:ad txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

RS

Responses