After Upgrade (RC -> final) -> PCI Passthrough Problems

T

trendco

Member
Proxmox Subscriber
Jan 9, 2012
282
2
18
Hi,

today i upgraded my Proxmox-RC1 installation to the Final Version ("aptitude update" & "aptitude full-upgrade"). But now, i have a Problem with one VM who uses PCI-Passthrough:

Failed to assign irq for "hostpci0": Input/output error
Perhaps you are assigning a device that shares an IRQ with another device?
kvm: -device pci-assign,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10: Device 'pci-assign' could not be initialized
Click to expand...

What's the Problem?


Alex
 
Hi maxprox,

after the upgrade to the final Version of Proxmox, "pve-qemu-kvm: 1.0-8" is installed an does not work. But i don't know, which was installed earlier version.


Alex
 
spirit said:
Could you try this package :
http://odisoweb1.odiso.net/qemu-server_2.0-31_amd64.deb
and put in your vm config file
hostpci0: XX:XX.XX,prefer_msi=on
?
Click to expand...

Hello Spirit,
On the one hand, I would also like to test it,
on the other side "never change a running system" ...
Code: 
drwxr-xr-x  2 root root 4,0K  2. Apr 12:02 test
root@fcprox01:/opt# pveversion -v
pve-manager: 2.0-42 (pve-manager/2.0/3d6d8258)
running kernel: 2.6.32-10-pve
proxmox-ve-2.6.32: 2.0-63
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-1
pve-cluster: 1.0-25
qemu-server: 2.0-28
pve-firmware: 1.0-15
libpve-common-perl: 1.0-21
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-14
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-3                      <==
ksm-control-daemon: 1.1-1
root@fcprox01:/opt#

This ist RC1 with pve-qemu-kvm changed to 1.0-3 and this combination works for me. Version pve-qemu-kvm 1.0-7 does not.

If I run now aptitude update; & aptitude full-upgrade I get the Version pve-qemu-kvm 1.0-8 and like Alex above I think it will not run.
When I install your version and realize that it also does not work, is it then possible to go back?
I mean, whether it is possible for the current proxmox pve version (stable) to switch pve-qemu-kvm back to 1.0-3?

regards
maxprox
 
Last edited:
maxprox said:
Hi Alex,

please can you show me your version?
The result of pveversion -v ...

maxprox
Click to expand...



pve-manager: 2.0-54 (pve-manager/2.0/4b59ea39)
running kernel: 2.6.32-10-pve
proxmox-ve-2.6.32: 2.0-63
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-31
pve-firmware: 1.0-15
libpve-common-perl: 1.0-23
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-16
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-8
ksm-control-daemon: 1.1-1
 
Hello,

For me it does not work!
Neither the current stable proxmox 2.0 version without changes nor with qemu-server_2.0-31_amd64.deb
both neither with nor without "...,prefer_msi=on"
Only after I've downgrade the pve-qemu-kvm: 1.0-8 to version 1.0-5 it works as bevore
Code: 
root@fcprox01:/opt# pveversion -v
pve-manager: 2.0-54 (pve-manager/2.0/4b59ea39)
running kernel: 2.6.32-10-pve
proxmox-ve-2.6.32: 2.0-63
pve-kernel-2.6.32-10-pve: 2.6.32-63
pve-kernel-2.6.32-6-pve: 2.6.32-55
pve-kernel-2.6.32-7-pve: 2.6.32-60
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-33
pve-firmware: 1.0-15
libpve-common-perl: 1.0-23
libpve-access-control: 1.0-17
libpve-storage-perl: 2.0-16
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-8   ==> I've replaced with version 1.0-5
ksm-control-daemon: 1.1-1
root@fcprox01:/opt#

maxprox
 
note:
my qemu-server_2.0-31_amd64.deb is not the version from proxmox (but same version number).
I have just recompiled with adding option to pass prefer_msi=on to config file.

maxprox :do you have tested it with my package ?

rollback pve-qemu-kvm is not an option for the future, as we always update to last kvm version.
Note: we use kvm git devel version, not yet stable 1.1, so maybe this is a bug not yet corrected by kvm devel.
 
You must log in or register to reply here.
Top Bottom