Proxmox Serial Port Pass Through Income
Posted : admin On 24.08.2019I am using a ROM file which I dumped myself using GPU-Z, this was the only was I could get a display as well. With Q35 I do see TianoCore and then the Windows10 logo but the guest crashes straight after that.
I'm very new to Proxmox and other bare metal hypervisors.
I cannot for the life of me get a physical (local) serial port (COM1) passed through to a Windows 10 VM. The server is an R710, all up do date, and has a Cisco console cable plugged into it's serial port. I have added the serial port via the web GUI, and the Win 10 VM settings lists the correct port at the bottom of the list:
Serial Port (serial0): socket

The serial port shows up in the Windows VM in the device manager under Ports (COM & LPT) as COM1. So it appears the port is set up properly and should communicate with the switch. If I use PuTTY and open communication with COM1 @ 9600 baud, I get nothing. It's just a cursor and wont let me type or initiate the switch login by hitting 'Enter.'
I had no problem getting this set up and working properly with ESXi; I was able to access the switch from within a Windows VM using PuTTY.
Any help is appreciated.
Proxmox Web Interface Port
I have a USB ADC/DAC and a HASP protected proprietary data acquisition system for it, both of which do not work in linux. I am trying to make it work in Windows virtual machine using qemu.Here are the devices:
My user is a member of qemu group.Qemu command line:
The problem is, both devices are showing in guest, but do not work. ADC/DAC should identify as a USB block drive, and is showing as one in device list, but doesn't work. I've installed HASP drivers for my dongle on the guest system, but the DAS software doesn't recognize it. What am I doing wrong?
AxonAxon1 Answer
I finally got help on the other forum. The issue seems to be with the USB bus implementation in I440FX chipset that is emulated by qemu by default (details here). The workaround is emulating the ICH9 chipset instead. This is done by adding -M q35 parameter. I also changed the way the USB devices are specified and the final command line looks like this:
Everything works perfectly now.
Update for 2019: the usb-device option was deprecated; you can achieve the same by replacing it with -usb -device and specifying product and vendor id in hexadecimal numbers, likewise:
reference: https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/usb2.txt;hb=HEAD
Jeff Schaller♦