On Mon, Jul 10, 2017 at 12:42 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:

Do you understand why my engine vm remains in "Booting from Hard Disk" screen from these logs?

Thanks,

Gianluca

One of possible causes of my engine unable to boot up could be this?

In 4.1.2 I was already in 7.3 and with the same qemu-kvm-ev and libvirt versions of 4.1.3, if I compare the command line of the VM, it was:

diff 4.1.2 4.1.3

< 2017-07-04 16:42:19.418+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem <http://bugs.centos.org>, 2017-05-25-20:52:28, c1bm.rdu2.centos.org), qemu version: 2.6.0 (qemu-kvm-ev-2.6.0-28.el7.10.1), hostname: ovirt02.localdomain.local

---

> 2017-07-09 23:09:13.894+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem <http://bugs.centos.org>, 2017-05-25-20:52:28, c1bm.rdu2.centos.org), qemu version: 2.6.0 (qemu-kvm-ev-2.6.0-28.el7.10.1), hostname: ovirt02.localdomain.local

5,6c5,6

< -machine pc-i440fx-rhel7.2.0,accel=kvm,usb=off 

< -cpu qemu64,-svm -m 6144 

---

> -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off 

> -cpu Broadwell,+rtm,+hle -m 6144 

9c9

< -smbios 'type=1,manufacturer=oVirt,product=oVirt Node,version=7-2.1511.el7.centos.2.10,serial=564D7100-F0D4-3ACC-795A-145A595604C0,uuid=87fd6bdb-535d-45b8-81d4-7e3101a6c364' 

---

> -smbios 'type=1,manufacturer=oVirt,product=oVirt Node,version=7-3.1611.el7.centos,serial=564D8F16-993A-33E1-3B2E-E1740F99C542,uuid=87fd6bdb-535d-45b8-81d4-7e3101a6c364' 

13c13

< -rtc base=2017-07-04T16:42:19,driftfix=slew 

---

> -rtc base=2017-07-09T23:09:13,driftfix=slew 

21c21

< -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=33 

---

> -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=32 

28a29,30

> -chardev pty,id=charconsole0 

> -device virtconsole,chardev=charconsole0,id=console0 

31c33,35

< -incoming defer -msg timestamp=on

---

> -object rng-random,id=objrng0,filename=/dev/urandom 

> -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 

> -msg timestamp=on

So it seems it changed both "machine" (from pc-i440fx-rhel7.2.0 to pc-i440fx-rhel7.3.0) and "cpu" (from qemu64,-svm to Broadwell,+rtm,+hle)

Can I revert so that I can check if it has any influence?

BTW: this is a nested environment, where the L0 host is ESX 6.0 U2.

Thanks for any suggestin to fix engine start

Gianluca