After Update to 4.2 unknown device acpi\qemu0002

[bonkersdeluxe]

Hi, after i upgraded to the latest version i have an unknown driver

My pveversion
proxmox-ve: 4.2-64 (running kernel: 4.4.16-1-pve)
pve-manager: 4.2-18 (running version: 4.2-18/158720b9)
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-4.4.16-1-pve: 4.4.16-64
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-44
qemu-server: 4.0-86
pve-firmware: 1.1-9
libpve-common-perl: 4.0-72
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-57
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-2
pve-container: 1.0-73
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80

the ID from the device is ACPI\QEMU0002

in the attachment screenshots from driver assistent.
What is it? I have downloaded the latest virtio drivers but nothing found.
I need drivers for windows 7 x64 and server 2008 vista base.

Thank you!

Sincerely Bonkersdeluxe

 

[wolfgang]

Hi,

please send the output of

qm showcmd <VMID>
qm config <VMID>

VMID is the No of this VM.

 

[bonkersdeluxe]

Hi, Thank you for reply.

qm showcmd 103
kvm: /usr/StorMan/ssl/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/x86_64-linux-gnu/libglusterfs.so.0)
kvm: /usr/StorMan/ssl/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/libspice-server.so.1)
kvm: /usr/StorMan/ssl/lib/libssl.so.1.0.0: no version information available (required by /usr/lib/libspice-server.so.1)
/usr/bin/kvm -id 103 -chardev socket,id=qmp,path=/var/run/qemu-server/103.qmp,server,nowait -mon chardev=qmp,mode=control -pidfile /var/run/qemu-server/103.pid -daemonize -name datevfileserv -smp 8,sockets=1,cores=8,maxcpus=8 -nodefaults -boot menu=on,strict=on,reboot-timeout=1000 -vga std -vnc unix:/var/run/qemu-server/103.vnc,x509,password -no-hpet -cpu host,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,+kvm_pv_unhalt,+kvm_pv_eoi -m 65536 -k de -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 virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -iscsi initiator-name=iqn.1993-08.org.debian:01:bf3123cc617a -drive file=/var/lib/vz/template/iso/virtio-win-0.1.118.iso,if=none,id=drive-ide0,media=cdrom,aio=threads -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200 -drive file=/var/lib/vz/template/iso/PRODVD_9_1DVD2.iso,if=none,id=drive-ide2,media=cdrom,aio=threads -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=201 -drive file=/dev/ssd/vm-103-disk-1,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,bootindex=100 -netdev type=tap,id=net0,ifname=tap103i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device virtio-net-pci,mac=00:50:56:86:00:01,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300 -rtc driftfix=slew,base=localtime -global kvm-pit.lost_tick_policy=discard

qm config 103

boot: cdn
bootdisk: virtio0
cores: 8
cpu: host
ide0: local:iso/virtio-win-0.1.118.iso,media=cdrom,size=55632K
ide2: local:iso/PRODVD_9_1DVD2.iso,media=cdrom,size=7408578K
memory: 65536
name: datevfileserv
net0: virtio=00:50:56:86:00:01,bridge=vmbr0
numa: 0
ostype: w2k8
sockets: 1
virtio0: ssd:vm-103-disk-1,cache=writeback,size=200G

Thank you!

Sincerely Bonkersdeluxe

 

[fabian]

Hi, Thank you for reply.

qm showcmd 103
kvm: /usr/StorMan/ssl/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/x86_64-linux-gnu/libglusterfs.so.0)
kvm: /usr/StorMan/ssl/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/libspice-server.so.1)
kvm: /usr/StorMan/ssl/lib/libssl.so.1.0.0: no version information available (required by /usr/lib/libspice-server.so.1)

really offtopic, but this does not sound good.. why do you have a copy of openssl in /usr/StorMan/ ? why is it included in ldconfig's include path and thus loaded when starting the kvm binary? this is a disaster waiting to happen..

 

[bonkersdeluxe]

Hi Fabian,
I don't know why the Adaptec StorMan installer included it. I have downloaded the last version from Storage Manager.
To acces the webgui, i must comment out the library pam_cracklib in the storman config, as workaround...

My workaround for StorMan
...
comment out
password required /lib/security/pam_cracklib.so retry=3 type=

and
change the path part of the modules from

/lib64/security/
to
/lib/x86_64-linux-gnu/security/
...
Do you have an idea?

Thank you!


Sincerely Bonkersdeluxe

 

[Kaya]

Hi, after i upgraded to the latest version i have an unknown driver

the ID from the device is ACPI\QEMU0002

Same unknown device here after upgrading to latest proxmox.
Reading here https://fossies.org/linux/qemu/docs/specs/fw_cfg.txt seems:

   87 == ACPI Interface ==
   88
   89 The fw_cfg device is defined with ACPI ID "QEMU0002". Since we expect
   90 ACPI tables to be passed into the guest through the fw_cfg device itself,
   91 the guest-side firmware can not use ACPI to find fw_cfg. However, once the
   92 firmware is finished setting up ACPI tables and hands control over to the
   93 guest kernel, the latter can use the fw_cfg ACPI node for a more accurate
   94 inventory of in-use IOport or MMIO regions.
   95

So: it's a windows 2k3 related problem that doesn't know how to handle this ACPI information?