Recent content by andreas70

Hello, we use a SafeNet Sentinel HASP Key, connected to a Win2k8R2 vm with Anywhere USB. SafeNet Driver version 6.22.0.0. Everything works fine.

Hallo Peter, thank you for this tip! I will try this. At the moment my server is in produktiv use and the dongle is connected to a hardware usb server. But i would be glad to get rid off this extra box. Andreas

I use use VIRTIO for all Disks + Network with Win2k8R2, fast and stable!

Hallo! Is the "backup=no" option now (i'm using pve 1.9) valid in a [vmid].conf? I want to use this feature (excluding a disk from backup) but i can't find any info exept this thread.

Hallo Jannis! It's the ID of the usb device you want to connect. You can lookup the devices avilable on your host with info hostusb. Please read the QEMU documentation for more infos: http://wiki.qemu.org/download/qemu-doc.html#pcsys_005fmonitor

Hallo Valle, i use a hardware usb-server (http://www.digi.com/products/usb/anywhereusb#overview), not a software on the host!

Hallo Jannis, you can connect an usb device to a vm with the usb_add command in QM Monitor, as i wrote in my post. I got no Solution for my problem (usb dongle not connected at boot), so i now use an usb-server(hardware) for my dongle.

Hallo! On one off my W2K8 VMs i need a usb hardlock dongle. When i conntect the dongle with usb_add host:0529:0001 (in QM Monitor), it works fine. But i don´t get it working automatically after rebooting the VM. I added hostusb: 0529:0001 to my .conf. After rebooting, the app does not see...

I also have a problem with usb. On one off my W2K8 VMs i need a hardlock dongle. When i conntect the dongle with usb_add host:0529:0001 (in QM Monitor), it works fine. But i don´t get it working automatically after rebooting the VM. I added hostusb: 0529:0001 to my .conf. After rebooting...

Hallo, i get a bluescreen on a KVM VM with Windows 2008 64bit OS (SBS) about once a day. It says: "A clock interrupt was not received on a secondary processor within the allocated time interval". Is there any known issue? For me it looks like this error comes from the virtual cpu the OS sees...