Thanks. Reading the defect and the associated thread in
https://bugs.launchpad.net/qemu/+bug/1661386, I enabled performance
counters in VMWare guest settings. Now the kvm assertion `ret ==
cpu->kvm_msr_buf->nmsrs' is gone. But the qemu/kvm hangs after printing
"SeaBIOS (version 1.10.2-1)"
I presume this too is a qemu/kvm issue for vmware platforms. Is there any
existing issue reported?
Regards,
Tanmoy Sinha
=============================================
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-0/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu x86_64
libguestfs: command: run: \ /usr/lib/x86_64-linux-gnu/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-0/appliance.d
supermin: version: 5.1.17
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-0/lock
supermin: if-newer: output does not need rebuilding
libguestfs: finished building supermin appliance
libguestfs: begin testing qemu features
libguestfs: checking for previously cached test results of
/usr/bin/qemu-system-x86_64, in /var/tmp/.guestfs-0
libguestfs: loading previously cached test results
libguestfs: qemu version 2.8
libguestfs: finished testing qemu features
[00012ms] /usr/bin/qemu-system-x86_64 \
-global virtio-blk-pci.scsi=off \
-nodefconfig \
-enable-fips \
-nodefaults \
-display none \
-machine accel=kvm:tcg \
-cpu host \
-m 500 \
-no-reboot \
-rtc driftfix=slew \
-no-hpet \
-global kvm-pit.lost_tick_policy=discard \
-kernel /var/tmp/.guestfs-0/appliance.d/kernel \
-initrd /var/tmp/.guestfs-0/appliance.d/initrd \
-object rng-random,filename=/dev/urandom,id=rng0 \
-device virtio-rng-pci,rng=rng0 \
-device virtio-scsi-pci,id=scsi \
-drive
file=/tmp/libguestfswJEdlG/scratch.1,cache=unsafe,format=raw,id=hd0,if=none
\
-device scsi-hd,drive=hd0 \
-drive
file=/var/tmp/.guestfs-0/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw
\
-device scsi-hd,drive=appliance \
-device virtio-serial-pci \
-serial stdio \
-device sga \
-chardev socket,path=/tmp/libguestfsj95RNX/guestfsd.sock,id=channel0 \
-device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
-append 'panic=1 console=ttyS0 edd=off udevtimeout=6000
udev.event-timeout=6000 no_timer_check printk.time=1 cgroup_disable=memory
usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=/dev/sdb
selinux=0 guestfs_verbose=1 TERM=screen'
libguestfs: responding to serial console Device Status Report
\x1b[1;256r\x1b[256;256H\x1b[6n
Google, Inc.
Serial Graphics Adapter 12/07/13
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (mjt@gandalf) Sat
Dec 7 15:39:53 UTC 2013
Term: 80x24
4 0
SeaBIOS (version 1.10.2-1)
On Fri, 23 Mar 2018 at 14:37 Pino Toscano <ptoscano(a)redhat.com> wrote:
On Friday, 23 March 2018 07:10:00 CET Tanmoy Sinha wrote:
> I am using a debian 9 guest, hosted on a ESXi platform with nested
> virtualisation enabled.
>
> On this debian 9 guest when I run libguesfs-test-tool, it fails with an
> error:
>
> "qemu-system-x86_64:
> /build/qemu-DqynNa/qemu-2.8+dfsg/target-i386/kvm.c:1805: kvm_put_msrs:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed."
See also
https://bugzilla.redhat.com/show_bug.cgi?id=1456407
This is basically a bug in VMware and the qemu bug
https://bugs.launchpad.net/qemu/+bug/1661386
has a couple of hints about what it can be changed in VMware to avoid
this situation.
--
Pino Toscano