Ok, so this should only be relevant in combination with iothread as aderumier explained.My understanding is that it is one controller per disk.
Yes you were right. I switched back to IDE on my test system after a host reboot but couldn't get the Windows VM back up running. It kept rebooting over and over again. There was something going on with my guest system.it's 100% unrelated. Note that if you change disk from ide->scsi, scsi->ide, you need to change boot drive each in vm option.
Hi @aderumier, I just installed the .deb you provided and rebooted the host to make sure everything was started with the new version.BTW, I have build last pve-qemu-kvm with patch for@hansm bug. (which is virtio related, so maybe it could improve performance too)
http://odisoweb1.odiso.net/pve-qemu-kvm_2.9.1-1_amd64.deb
kvm: symbol lookup error: kvm: undefined symbol: rbd_aio_writev
command 'kvm -version' failed: exit code 127
TASK ERROR: detected old qemu-kvm binary (unknown)
you can download and install pve-kernel from proxmox 4 without problem.
# wget http://download.proxmox.com/debian/...d64/pve-kernel-4.4.8-1-pve_4.4.8-52_amd64.deb
# dpkg -i *.deb
uname -a
Linux pve7 4.4.8-1-pve #1 SMP Tue May 31 07:12:32 CEST 2016 x86_64 GNU/Linux
I have installed the 4.4.8-1 kernel on my test system:
Code:uname -a Linux pve7 4.4.8-1-pve #1 SMP Tue May 31 07:12:32 CEST 2016 x86_64 GNU/Linux
But still the same issue.
Hi @aderumier, I just installed the .deb you provided and rebooted the host to make sure everything was started with the new version.
But I get an error when I try to start the VM:
Code:kvm: symbol lookup error: kvm: undefined symbol: rbd_aio_writev command 'kvm -version' failed: exit code 127 TASK ERROR: detected old qemu-kvm binary (unknown)
Hi, I have rebuild my package with librbd 10.2.5, like proxmox5, so you don't need last ceph librairies to get it work and test
http://odisoweb1.odiso.net/pve-qemu-kvm_2.9.1-1_amd64.deb
# dpkg -i pve-qemu-kvm_2.9.1-1_amd64.deb
(Reading database ... 60826 files and directories currently installed.)
Preparing to unpack pve-qemu-kvm_2.9.1-1_amd64.deb ...
Unpacking pve-qemu-kvm (2.9.1-1) over (2.9.1-1) ...
Setting up pve-qemu-kvm (2.9.1-1) ...
Processing triggers for man-db (2.7.6.1-2) ...
@aderumier Thank you.
I have installed your version of qemu-kvm:
I did a reboot of my host and my KVM machine started this time without the error I got before.Code:# dpkg -i pve-qemu-kvm_2.9.1-1_amd64.deb (Reading database ... 60826 files and directories currently installed.) Preparing to unpack pve-qemu-kvm_2.9.1-1_amd64.deb ... Unpacking pve-qemu-kvm (2.9.1-1) over (2.9.1-1) ... Setting up pve-qemu-kvm (2.9.1-1) ... Processing triggers for man-db (2.7.6.1-2) ...
However the issue remains the same.
Can you post a MD5 for one of the binaries of your package so that I can compare it with my installed version just to make 100% sure the files has been correctly replaced by dpkg?
However it looks to me that this is not the solution yet.
#md5sum /usr/bin/kvm
be19f6834b8486d138f5eb9d90d2477b /usr/bin/kvm
Same result here.
I already thought about installing PVE 4.4 on my test system to check if I get the same issue there. However I would loose me 5.0 test system then and I would not be able to do tests with PVE 5.0 until I reinstall everything again. Which is quite time consuming.
No you haven't.I don't have asked to install full pve4.4, only pve-qemu-kvm package from proxmox 4 on proxmox 5.