Could not start a VM with RBD at a new node

Jason2510

New Member
Sep 22, 2018
2
0
1
27
Hello guys,

Yesterday I had joned a new node into my current proxmox cluster. Everything was fined. After that, I moved a VM from an old node into this one (new node). But unfortunately, I could not start it, here is my output:

root@s34:~# qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
2510001 test-win10 stopped 8192 32.00 0
root@s34:~# qm start 2510001
kvm: -drive file=rbd:vietnixvps/vm-2510001-disk-1:mon_host=s30\:6789;storage01\:6789;storage03\:6789:id=admin:auth_supported=cephx:keyring=/etc/pve/priv/ceph/CEPH.keyring,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on: error reading header from vm-2510001-disk-1: Function not implemented
start failed: command '/usr/bin/kvm -id 2510001 -chardev 'socket,id=qmp,path=/var/run/qemu-server/2510001.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/2510001.pid -daemonize -smbios 'type=1,uuid=347e256d-d684-4495-9ba5-bbb1e8a65039' -name test-win10 -smp '8,sockets=2,cores=4,maxcpus=8' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga std -vnc unix:/var/run/qemu-server/2510001.vnc,x509,password -no-hpet -cpu 'kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,enforce' -m 8192 -object 'memory-backend-ram,id=ram-node0,size=4096M' -numa 'node,nodeid=0,cpus=0-3,memdev=ram-node0' -object 'memory-backend-ram,id=ram-node1,size=4096M' -numa 'node,nodeid=1,cpus=4-7,memdev=ram-node1' -k en-us -object 'iothread,id=iothread-virtio0' -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 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:e1318b93ea55' -drive 'file=rbd:vietnixvps/vm-2510001-disk-1:mon_host=s30\:6789;storage01\:6789;storage03\:6789:id=admin:auth_supported=cephx:keyring=/etc/pve/priv/ceph/CEPH.keyring,if=none,id=drive-virtio0,cache=writeback,format=raw,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,iothread=iothread-virtio0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap2510001i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=E6:38:58:E8:CC:C9,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1



And here is the version:

root@s34:~# pveversion
pve-manager/4.4-1/eb2d6f1e (running kernel: 4.4.35-1-pve)



Anyone ever met them? Very appreciate for any support!
 
Totally fixed it after upgrade librbd1 version, it was too old. Hope my case can help some guys later.
 

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!