search for: kvm_msr_buf

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:...

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." Instead when I use a wrapper script and hook it with the env variable LIBGUESTFS_HV=/tmp/qemu.wrapper, things work fine, as in the script I just spawn the guest with the specific machine type pc-i440fx-2.1 over KVM. exec qemu-system-x86_64 -enable-kvm -machine *pc-i44...

...On Fri, Mar 23, 2018 at 05:35:38PM +0000, Tanmoy Sinha wrote: > > 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? > > Does it work if you set: > > export LIBG...

Hi, I am having issues with libguestfs; I am unable to mount a disk either from cli or via python bindings. This was working previously, but in order to have access to python3.5 I am trying to upgrade from Debian 8/Jessie to Debian 9/Stretch. Unfortunately the libguestfs error is getting in the way. Output of libguestfs-test-tool is attached as per libguestfs.org help. My current environment:

...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

On Fri, Mar 23, 2018 at 05:35:38PM +0000, Tanmoy Sinha wrote: > 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? Does it work if you set: export LIBGUESTFS_BACKEND_SETTINGS=force_tcg ?...

...2018 at 05:35:38PM +0000, Tanmoy Sinha wrote: >> > 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? >> >> Does it work if...

...a - BR/Sao Paulo)> Original error from libvirt: internal error: process exited while connecting to monitor: 2018-11-21T08:15:39.670714Z qemu-kvm: error: failed to set MSR 0x38d to 0x0 > qemu-kvm: /builddir/build/BUILD/qemu-2.10.0/target/i386/kvm.c:1809: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. [code=1 int1=-1] Yes this is unfortunately a recent bug in qemu which has come up several times. I don't believe there is a resolution yet, but please see: https://bugzilla.redhat.com/show_bug.cgi?id=1651021 https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg0350...