qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Montes, Julio]

[-- Attachment #1: Type: text/plain, Size: 4867 bytes --]

Hi folks

I'm trying to run qemu 4.2.0 in azure VMs, unfourtunately qemu fails:

failed to launch qemu: exit status 1, error messages from qemu log: qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

I'm using the following command line:

qemu-system-x86_64 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu host,pmu=off \
-qmp unix:qmp.sock,server,nowait -m 2048M,slots=10,maxmem=8977M -device pci-bridge,bus=pci.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2,romfile= \
-device virtio-serial-pci,disable-modern=true,id=serial0,romfile= -device virtconsole,chardev=charconsole0,id=console0 \
-chardev socket,id=charconsole0,path=console.sock,server,nowait -device nvdimm,id=nv0,memdev=mem0 \
-object memory-backend-file,id=mem0,mem-path=kata-containers.img,size=134217728 -device virtio-scsi-pci,id=scsi0,disable-modern=true,romfile= \
-object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng,rng=rng0,romfile= -device virtserialport,chardev=charch0,id=channel0,name=agent.channel.0 \
-chardev socket,id=charch0,path=kata.sock,server,nowait -device virtio-9p-pci,disable-modern=true,fsdev=extra-9p-kataShared,mount_tag=kataShared,romfile= \
-fsdev local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes,security_model=none -netdev tap,id=network-0,vhost=on,vhostfds=3,fds=4 \
-device driver=virtio-net-pci,netdev=network-0,mac=ea:4a:b6:1a:92:72,disable-modern=true,mq=on,vectors=4,romfile= \
-global kvm-pit.lost_tick_policy=discard -vga none -no-user-config -nodefaults -nographic -daemonize -object memory-backend-ram,id=dimm1,size=2048M \
-numa node,memdev=dimm1 -kernel /usr/share/kata-containers/vmlinuz-4.19.86-60 \
-append "tsc=reliable no_timer_check rcupdate.rcu_expedited=1 i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp reboot=k \
console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 pci=lastbus=0 root=/dev/pmem0p1 rootflags=dax,data=ordered,errors=remount-ro \
ro rootfstype=ext4 debug systemd.show_status=true systemd.log_level=debug panic=1 nr_cpus=2 agent.use_vsock=false systemd.unit=kata-containers.target \
systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket agent.log=debug agent.log=debug" \
-pidfile pid -D qemu.log -smp 1,cores=1,threads=1,sockets=2,maxcpus=2

Qemu 4.1.0 works fine
Qemu 4.2.0 **only** fails in azure VMs, in my workstation it works fine

any thoughts?


Information about the VM:

$ cat /sys/module/kvm_intel/parameters/nested
Y

$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
stepping : 1
microcode : 0xffffffff
cpu MHz : 2294.685
cache size : 51200 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti tpr_shadow vnmi ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt md_clear
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 4589.37
clflush size : 64
cache_alignment : 64
address sizes : 44 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
stepping : 1
microcode : 0xffffffff
cpu MHz : 2294.685
cache size : 51200 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti tpr_shadow vnmi ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt md_clear
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 4589.37
clflush size : 64
cache_alignment : 64
address sizes : 44 bits physical, 48 bits virtual
power management:

$ uname -a
Linux testcrio1 5.0.0-1027-azure #29~18.04.1-Ubuntu SMP Mon Nov 25 21:18:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Thanks

-
Julio



[-- Attachment #2: Type: text/html, Size: 7359 bytes --]

Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Philippe Mathieu-Daudé]

Hi Julio,

On 12/13/19 9:53 PM, Montes, Julio wrote:
> Hi folks
> 
> I'm trying to run qemu 4.2.0 in azure VMs, unfourtunately qemu fails:
> 
> failed to launch qemu: exit status 1, error messages from qemu log: 
> qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
> qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs: 
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
> 
> I'm using the following command line:
> 
> qemu-system-x86_64 -machine pc,accel=kvm,kernel_irqchip,nvdimm -cpu 
> host,pmu=off \
> -qmp unix:qmp.sock,server,nowait -m 2048M,slots=10,maxmem=8977M -device 
> pci-bridge,bus=pci.0,id=pci-bridge-0,chassis_nr=1,shpc=on,addr=2,romfile= \
> -device virtio-serial-pci,disable-modern=true,id=serial0,romfile= 
> -device virtconsole,chardev=charconsole0,id=console0 \
> -chardev socket,id=charconsole0,path=console.sock,server,nowait -device 
> nvdimm,id=nv0,memdev=mem0 \
> -object 
> memory-backend-file,id=mem0,mem-path=kata-containers.img,size=134217728 
> -device virtio-scsi-pci,id=scsi0,disable-modern=true,romfile= \
> -object rng-random,id=rng0,filename=/dev/urandom -device 
> virtio-rng,rng=rng0,romfile= -device 
> virtserialport,chardev=charch0,id=channel0,name=agent.channel.0 \
> -chardev socket,id=charch0,path=kata.sock,server,nowait -device 
> virtio-9p-pci,disable-modern=true,fsdev=extra-9p-kataShared,mount_tag=kataShared,romfile= 
> \
> -fsdev 
> local,id=extra-9p-kataShared,path=/run/kata-containers/shared/sandboxes,security_model=none 
> -netdev tap,id=network-0,vhost=on,vhostfds=3,fds=4 \
> -device 
> driver=virtio-net-pci,netdev=network-0,mac=ea:4a:b6:1a:92:72,disable-modern=true,mq=on,vectors=4,romfile= 
> \
> -global kvm-pit.lost_tick_policy=discard -vga none -no-user-config 
> -nodefaults -nographic -daemonize -object 
> memory-backend-ram,id=dimm1,size=2048M \
> -numa node,memdev=dimm1 -kernel 
> /usr/share/kata-containers/vmlinuz-4.19.86-60 \
> -append "tsc=reliable no_timer_check rcupdate.rcu_expedited=1 
> i8042.direct=1 i8042.dumbkbd=1 i8042.nopnp=1 i8042.noaux=1 noreplace-smp 
> reboot=k \
> console=hvc0 console=hvc1 iommu=off cryptomgr.notests net.ifnames=0 
> pci=lastbus=0 root=/dev/pmem0p1 
> rootflags=dax,data=ordered,errors=remount-ro \
> ro rootfstype=ext4 debug systemd.show_status=true 
> systemd.log_level=debug panic=1 nr_cpus=2 agent.use_vsock=false 
> systemd.unit=kata-containers.target \
> systemd.mask=systemd-networkd.service 
> systemd.mask=systemd-networkd.socket agent.log=debug agent.log=debug" \
> -pidfile pid -D qemu.log -smp 1,cores=1,threads=1,sockets=2,maxcpus=2
> 
> Qemu 4.1.0 works fine
> Qemu 4.2.0 **only** fails in azure VMs, in my workstation it works fine
> 
> any thoughts?

Are you running also nested on your workstation?

> 
> 
> Information about the VM:
> 
> $ cat /sys/module/kvm_intel/parameters/nested
> Y
> 
> $ cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 79
> model name : Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
> stepping : 1
> microcode : 0xffffffff
> cpu MHz : 2294.685
> cache size : 51200 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 1
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 20
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
> constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma 
> cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand 
> hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti tpr_shadow vnmi 
> ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx 
> smap xsaveopt md_clear
> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
> swapgs taa itlb_multihit
> bogomips : 4589.37
> clflush size : 64
> cache_alignment : 64
> address sizes : 44 bits physical, 48 bits virtual
> power management:
> 
> processor : 1
> vendor_id : GenuineIntel
> cpu family : 6
> model : 79
> model name : Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
> stepping : 1
> microcode : 0xffffffff
> cpu MHz : 2294.685
> cache size : 51200 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 1
> apicid : 1
> initial apicid : 1
> fpu : yes
> fpu_exception : yes
> cpuid level : 20
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
> pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm 
> constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma 
> cx16 pcid sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand 
> hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti tpr_shadow vnmi 
> ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx 
> smap xsaveopt md_clear
> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
> swapgs taa itlb_multihit
> bogomips : 4589.37
> clflush size : 64
> cache_alignment : 64
> address sizes : 44 bits physical, 48 bits virtual
> power management:
> 
> $ uname -a
> Linux testcrio1 5.0.0-1027-azure #29~18.04.1-Ubuntu SMP Mon Nov 25 
> 21:18:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> 
> Thanks
> 
> -
> Julio
> 
> 

Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Paolo Bonzini]

On 14/12/19 02:31, Philippe Mathieu-Daudé wrote:
> 
> failed to launch qemu: exit status 1, error messages from qemu log:
> qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
> qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

It could be a KVM bug too.  The following features are being enabled:

#define VMX_SECONDARY_EXEC_XSAVES                   0x00100000
#define VMX_SECONDARY_EXEC_SHADOW_VMCS              0x00004000
#define VMX_SECONDARY_EXEC_ENABLE_INVPCID           0x00001000
#define VMX_SECONDARY_EXEC_RDRAND_EXITING           0x00000800
#define VMX_SECONDARY_EXEC_ENABLE_VPID              0x00000020
#define VMX_SECONDARY_EXEC_ENABLE_EPT               0x00000002
#define VMX_SECONDARY_EXEC_DESC                     0x00000004
#define VMX_SECONDARY_EXEC_RDTSCP                   0x00000008

Can you try:

1) running "vmxcap" on the Azure VM

2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
works, add only one of the two.

3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
run "x86info -a" in the resulting VM.

Thanks,

Paolo

Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Montes, Julio]

[-- Attachment #1: Type: text/plain, Size: 2467 bytes --]

Hi Paolo and Philippe

> Are you running also nested on your workstation?

yes, qemu in qemu

> 1) running "vmxcap" on the Azure VM

$ sudo ./vmxcap
Basic VMX Information
Traceback (most recent call last):
  File "./vmxcap", line 280, in <module>
    c.show()
  File "./vmxcap", line 82, in show
    value = msr().read(self.msr, 0)
  File "./vmxcap", line 33, in __init__
    self.f = open('/dev/msr0', 'rb', 0)
IOError: [Errno 2] No such file or directory: '/dev/msr0'

> 2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
> works, add only one of the two.

nop, this didn't work


> 3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
> run "x86info -a" in the resulting VM.

yes, -vmx works

x86info -a  ->  https://paste.centos.org/view/f88f02f4


thanks

-
Julio

________________________________
From: Paolo Bonzini <pbonzini@redhat.com>
Sent: Saturday, December 14, 2019 1:30 AM
To: Philippe Mathieu-Daudé <philmd@redhat.com>; Montes, Julio <julio.montes@intel.com>; qemu-devel <qemu-devel@nongnu.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

On 14/12/19 02:31, Philippe Mathieu-Daudé wrote:
>
> failed to launch qemu: exit status 1, error messages from qemu log:
> qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
> qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

It could be a KVM bug too.  The following features are being enabled:

#define VMX_SECONDARY_EXEC_XSAVES                   0x00100000
#define VMX_SECONDARY_EXEC_SHADOW_VMCS              0x00004000
#define VMX_SECONDARY_EXEC_ENABLE_INVPCID           0x00001000
#define VMX_SECONDARY_EXEC_RDRAND_EXITING           0x00000800
#define VMX_SECONDARY_EXEC_ENABLE_VPID              0x00000020
#define VMX_SECONDARY_EXEC_ENABLE_EPT               0x00000002
#define VMX_SECONDARY_EXEC_DESC                     0x00000004
#define VMX_SECONDARY_EXEC_RDTSCP                   0x00000008

Can you try:

1) running "vmxcap" on the Azure VM

2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
works, add only one of the two.

3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
run "x86info -a" in the resulting VM.

Thanks,

Paolo


[-- Attachment #2: Type: text/html, Size: 7687 bytes --]

Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Paolo Bonzini]

[-- Attachment #1: Type: text/plain, Size: 2572 bytes --]

>
>
> > 1) running "vmxcap" on the Azure VM
>

You need to run "modprobe msr" before.

Paolo


>
> $ sudo ./vmxcap
> Basic VMX Information
> Traceback (most recent call last):
>   File "./vmxcap", line 280, in <module>
>     c.show()
>   File "./vmxcap", line 82, in show
>     value = msr().read(self.msr, 0)
>   File "./vmxcap", line 33, in __init__
>     self.f = open('/dev/msr0', 'rb', 0)
> IOError: [Errno 2] No such file or directory: '/dev/msr0'
>
> > 2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
> > works, add only one of the two.
>
> nop, this didn't work
>
>
> > 3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
> > run "x86info -a" in the resulting VM.
>
> yes, -vmx works
>
> x86info -a  ->  https://paste.centos.org/view/f88f02f4
>
>
> thanks
>
> -
> Julio
>
> ------------------------------
> *From:* Paolo Bonzini <pbonzini@redhat.com>
> *Sent:* Saturday, December 14, 2019 1:30 AM
> *To:* Philippe Mathieu-Daudé <philmd@redhat.com>; Montes, Julio <
> julio.montes@intel.com>; qemu-devel <qemu-devel@nongnu.org>
> *Cc:* Eduardo Habkost <ehabkost@redhat.com>
> *Subject:* Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
>
> On 14/12/19 02:31, Philippe Mathieu-Daudé wrote:
> >
> > failed to launch qemu: exit status 1, error messages from qemu log:
> > qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
> > qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs:
> > Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
>
> It could be a KVM bug too.  The following features are being enabled:
>
> #define VMX_SECONDARY_EXEC_XSAVES                   0x00100000
> #define VMX_SECONDARY_EXEC_SHADOW_VMCS              0x00004000
> #define VMX_SECONDARY_EXEC_ENABLE_INVPCID           0x00001000
> #define VMX_SECONDARY_EXEC_RDRAND_EXITING           0x00000800
> #define VMX_SECONDARY_EXEC_ENABLE_VPID              0x00000020
> #define VMX_SECONDARY_EXEC_ENABLE_EPT               0x00000002
> #define VMX_SECONDARY_EXEC_DESC                     0x00000004
> #define VMX_SECONDARY_EXEC_RDTSCP                   0x00000008
>
> Can you try:
>
> 1) running "vmxcap" on the Azure VM
>
> 2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
> works, add only one of the two.
>
> 3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
> run "x86info -a" in the resulting VM.
>
> Thanks,
>
> Paolo
>
>

[-- Attachment #2: Type: text/html, Size: 7094 bytes --]

Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

[Montes, Julio]

[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]

here the log https://paste.centos.org/view/cbaae252

Thanks

-
Julio
________________________________
From: Paolo Bonzini <pbonzini@redhat.com>
Sent: Monday, December 16, 2019 1:23 PM
To: Montes, Julio <julio.montes@intel.com>
Cc: Philippe Mathieu-Daudé <philmd@redhat.com>; qemu-devel <qemu-devel@nongnu.org>; Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.


> 1) running "vmxcap" on the Azure VM

You need to run "modprobe msr" before.

Paolo



$ sudo ./vmxcap
Basic VMX Information
Traceback (most recent call last):
  File "./vmxcap", line 280, in <module>
    c.show()
  File "./vmxcap", line 82, in show
    value = msr().read(self.msr, 0)
  File "./vmxcap", line 33, in __init__
    self.f = open('/dev/msr0', 'rb', 0)
IOError: [Errno 2] No such file or directory: '/dev/msr0'

> 2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
> works, add only one of the two.

nop, this didn't work


> 3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
> run "x86info -a" in the resulting VM.

yes, -vmx works

x86info -a  ->  https://paste.centos.org/view/f88f02f4


thanks

-
Julio

________________________________
From: Paolo Bonzini <pbonzini@redhat.com<mailto:pbonzini@redhat.com>>
Sent: Saturday, December 14, 2019 1:30 AM
To: Philippe Mathieu-Daudé <philmd@redhat.com<mailto:philmd@redhat.com>>; Montes, Julio <julio.montes@intel.com<mailto:julio.montes@intel.com>>; qemu-devel <qemu-devel@nongnu.org<mailto:qemu-devel@nongnu.org>>
Cc: Eduardo Habkost <ehabkost@redhat.com<mailto:ehabkost@redhat.com>>
Subject: Re: qemu-4.2: failed to set MSR 0x48b to 0x1582e00000000: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

On 14/12/19 02:31, Philippe Mathieu-Daudé wrote:
>
> failed to launch qemu: exit status 1, error messages from qemu log:
> qemu-system-x86_64: error: failed to set MSR 0x48b to 0x1582e00000000
> qemu-system-x86_64: /root/qemu/target/i386/kvm.c:2947: kvm_put_msrs:
> Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.

It could be a KVM bug too.  The following features are being enabled:

#define VMX_SECONDARY_EXEC_XSAVES                   0x00100000
#define VMX_SECONDARY_EXEC_SHADOW_VMCS              0x00004000
#define VMX_SECONDARY_EXEC_ENABLE_INVPCID           0x00001000
#define VMX_SECONDARY_EXEC_RDRAND_EXITING           0x00000800
#define VMX_SECONDARY_EXEC_ENABLE_VPID              0x00000020
#define VMX_SECONDARY_EXEC_ENABLE_EPT               0x00000002
#define VMX_SECONDARY_EXEC_DESC                     0x00000004
#define VMX_SECONDARY_EXEC_RDTSCP                   0x00000008

Can you try:

1) running "vmxcap" on the Azure VM

2) adding "-vmx-xsaves,-vmx-shadow-vmcs" to the "-cpu" option and, if it
works, add only one of the two.

3) if it doesn't work, adding "-vmx" to the "-cpu" option.  Either way,
run "x86info -a" in the resulting VM.

Thanks,

Paolo


[-- Attachment #2: Type: text/html, Size: 9359 bytes --]