Vm not start after upgrade proxmox "bug?"

Norberto Iannicelli

Well-Known Member
May 9, 2016
54
0
46
38
package version:
proxmox-ve: 5.4-2 (running kernel: 4.15.18-12-pve) pve-manager: 5.4-8 (running version: 5.4-8/51d494ca) pve-kernel-4.15: 5.4-5 pve-kernel-4.15.18-17-pve: 4.15.18-43 pve-kernel-4.15.18-12-pve: 4.15.18-36 corosync: 2.4.4-pve1 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2 libjs-extjs: 6.0.1-2 libpve-access-control: 5.1-11 libpve-apiclient-perl: 2.0-5 libpve-common-perl: 5.0-53 libpve-guest-common-perl: 2.0-20 libpve-http-server-perl: 2.0-13 libpve-storage-perl: 5.0-44 libqb0: 1.0.3-1~bpo9 lvm2: 2.02.168-pve6 lxc-pve: 3.1.0-3 lxcfs: 3.0.3-pve1 novnc-pve: 1.0.0-3 proxmox-widget-toolkit: 1.0-28 pve-cluster: 5.0-37 pve-container: 2.0-39 pve-docs: 5.4-2 pve-edk2-firmware: 1.20190312-1 pve-firewall: 3.0-22 pve-firmware: 2.0-6 pve-ha-manager: 2.0-9 pve-i18n: 1.1-4 pve-libspice-server1: 0.14.1-2 pve-qemu-kvm: 3.0.1-4 pve-xtermjs: 3.12.0-1 qemu-server: 5.0-54 smartmontools: 6.5+svn4324-1 spiceterm: 3.0-5 vncterm: 1.5-3

After try start vm machine return this:

kvm: error: failed to set MSR 0x10a to 0x0
kvm: /home/build/pve-qemu/pve-qemu-kvm-3.0.1/target/i386/kvm.c:2145: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name vps.xxxxxx.com.br -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=60d2ea4d-fe6a-49e8-ab20-fe3a036c5ce9' -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu 'EPYC,+kvm_pv_unhalt,+kvm_pv_eoi,enforce,vendor=AuthenticAMD' -m 2048 -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/mnt/pve/stor01/images/100/vm-100-disk-0.qcow2,if=none,id=drive-scsi0,cache=writethrough,discard=on,format=qcow2,aio=threads,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=02:00:00:a3:41:29,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc'' failed: exit code 1
 
please use 'code' tags when pasting output, since the text is quite hard to read otherwise.

it seems you're running with an older kernel 4.15.18-12-pve (latest installed seems pve-kernel-4.15.18-17-pve) - please try to reproduce the issue with the latest available kernel.

if you can reproduce it - what kind of hardware do you experience the problem on?
 
Sorry for that, during the night I will restart the servers to test.
For an hour I circled the code below and resolved.
echo Y > /sys/module/kvm/parameters/ignore_msrs
 
I confirm the same problém. Version of Proxmox 5.4-7,4 , kernel 4.15.18-12-pve
I stop VM because of backup.
Code:
FO: starting kvm to execute backup task
kvm: error: failed to set MSR 0x10a to 0x0
kvm: /home/build/pve-qemu/pve-qemu-kvm-3.0.1/target/i386/kvm.c:2145: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
ERROR: Backup of VM 100 failed - start failed: command '/usr/bin/kvm -id 100 -name Tritius -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/100.pid -daemonize -smbios 'type=1,uuid=9c566026-8ba9-4524-85e0-7575ee12c8f1' -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vnc unix:/var/run/qemu-server/100.vnc,x509,password -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce -m 16000 -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'vmgenid,guid=6caad34f-56de-48ac-adad-9a084cea7d5b' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -device 'VGA,id=vga,bus=pci.0,addr=0x2' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:ea1126baf5f9' -drive 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/dev/localRAID/vm-100-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=72:6F:09:44:8C:2D,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -machine 'type=pc' -S' failed: exit code 1
INFO: Failed at 2019-06-29 22:14:20
INFO: Backup job finished with errors
TASK ERROR: job errors

Attempt to run VM ended with error
Code:
kvm: error: failed to set MSR 0x10a to 0x0
command
Code:
 echo Y > /sys/module/kvm/parameters/ignore_msrs
Solved the error and VM start, but I do not undertand wher is problém?
 
Last edited:
Solved the error and VM start, but I do not undertand wher is problém?
KVM can set MSRs with the new kernel, the old kernel doesn't have the interface yet. When you upgrade the new packages, but don't restart for the new kernel to activate, you will be left in this state.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!