Very strange

[scontin]

Hi to all.
I have taken advantage of this holidays to migrate a production environment of Proxmox from proxmox-ve-2.6.18 to proxmox-ve-2.6.32

Now it's

pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-25
pve-kernel-2.6.32-4-pve: 2.6.32-25
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

No config changed at all, only acpid upgraded (with acpi-support-base) from debian backports, to permit the button shutdown.
Nothing else.

Everything it's working, except a dongle attached on parallel port (LPT1) used by a Windows XP Machine.

/dev/parport0 is seen as before, ppdev,parport_pc loaded as before.

proxmox:~# ls -hl /dev/parport0
crw-rw---- 1 root lp 99, 0 1 nov 23:45 /dev/parport0

Ideas?

 

[scontin]

Update:
I try change port settings to EPP and SPP: nothing
I checked everything (permission, ovner, symlinks) in version proxmox-ve-2.6.18: the same of proxmox-ve-2.6.32.
In the VM the LPT1 appers, but the dongle is not reached

 

[scontin]

There are differencies regard LPT in new version of qemu-server? It's compiled the support?
Thanks

 

[dietmar]

There are differencies regard LPT in new version of qemu-server?

I guess yes: see http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=summary

It's compiled the support?

yes.

Maybe you can test with qemu-server-0.13.0 from pvetest? (but please do not test on the production server).

 

[scontin]

I can only test on that production server.
No other dongles :-D

it's so unstable qemu-server-0.13.0 ?

 

[dietmar]

I can only test on that production server.
No other dongles :-D

it's so unstable qemu-server-0.13.0 ?

No, we plan to release that next week. Besides, I would never do any test on a production server.