Hi all!
We're one MS Windows 11 Professional Guest running in Proxmox VE 8.03 with virtio-Drivers and guest-agent installed.
Guest runs fine so far.
But now we want to do backups from guest-system to different USB-HDDs. So we configured USB-device mapping to a specified USB-port (for example one of the both front-USB-ports: 2-6). After plug-in the HDD, it's recognized in Windows without any error, performance is fine. Now, after backup is done, we just plug-off the HDD.
This works fine most of the time.
But sometimes, after plug-in, the guest system (Win 11) stops working, so I have to boot it again. In Windows event manager there's only one entry sounding like "System has been switched off without clean shutdown".
Please find the output of the PVE-log below...
The issue sounds like that one from user FaySmash: https://forum.proxmox.com/threads/vm-crashes-on-usb-to-sata-adapter-removal.129087/
Type of Mainboard: Supermicro X12STL-IF
External HDDs use USB 3.0
Could you please help me?
Seems like an qemu issue, or I'm wrong?
Could an upgrade to PVE 8.1 resolve my issue? I looked at the release notes but I'm not sure...
Best regards
mica85
QM-Config:
Here's the log from pve (Host):
We're one MS Windows 11 Professional Guest running in Proxmox VE 8.03 with virtio-Drivers and guest-agent installed.
Guest runs fine so far.
But now we want to do backups from guest-system to different USB-HDDs. So we configured USB-device mapping to a specified USB-port (for example one of the both front-USB-ports: 2-6). After plug-in the HDD, it's recognized in Windows without any error, performance is fine. Now, after backup is done, we just plug-off the HDD.
This works fine most of the time.
But sometimes, after plug-in, the guest system (Win 11) stops working, so I have to boot it again. In Windows event manager there's only one entry sounding like "System has been switched off without clean shutdown".
Please find the output of the PVE-log below...
The issue sounds like that one from user FaySmash: https://forum.proxmox.com/threads/vm-crashes-on-usb-to-sata-adapter-removal.129087/
Type of Mainboard: Supermicro X12STL-IF
External HDDs use USB 3.0
Could you please help me?
Seems like an qemu issue, or I'm wrong?
Could an upgrade to PVE 8.1 resolve my issue? I looked at the release notes but I'm not sure...
Best regards
mica85
QM-Config:
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0;ide0
cores: 4
cpu: host
efidisk0: storage:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-q35-8.0
memory: 8128
meta: creation-qemu=8.0.2,ctime=1698750141
name: Win11srv2
net0: virtio=DE:22:88:60:77:F3,bridge=vmbr0,firewall=1
net1: virtio=32:24:B4:B6:15:0E,bridge=vmbr1,firewall=1
numa: 0
onboot: 1
ostype: win11
parent: db_bereinigt
scsi0: storage:vm-100-disk-1,iothread=1,size=1000G
scsihw: virtio-scsi-single
smbios1: uuid=7adb8a0e-7193-4d21-a1ef-f19c692ebc2f
sockets: 1
tpmstate0: storage:vm-100-disk-2,size=4M,version=v2.0
usb0: host=2-6,usb3=1
vga: qxl
Here's the log from pve (Host):
Nov 27 15:36:24 pvesrv kernel: usb 2-6: USB disconnect, device number 6
Nov 27 15:36:25 pvesrv QEMU[3139271]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Nov 27 15:36:26 pvesrv kernel: usb 2-6: new SuperSpeed USB device number 7 using xhci_hcd
Nov 27 15:36:26 pvesrv kernel: usb 2-6: New USB device found, idVendor=1058, idProduct=2626, bcdDevice=10.34
Nov 27 15:36:26 pvesrv kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 27 15:36:26 pvesrv kernel: usb 2-6: Product: My Passport 2626
Nov 27 15:36:26 pvesrv kernel: usb 2-6: Manufacturer: Western Digital
Nov 27 15:36:26 pvesrv kernel: usb 2-6: SerialNumber: xxxxxxxxx (edit: S/N removed from mica85)
Nov 27 15:36:26 pvesrv kernel: usb-storage 2-6:1.0: USB Mass Storage device detected
Nov 27 15:36:26 pvesrv kernel: scsi host6: usb-storage 2-6:1.0
Nov 27 15:36:27 pvesrv QEMU[3139271]: kvm: ../hw/usb/host-libusb.c:899: usb_host_ep_update: Assertion `alt < conf->interface.num_altsetting' failed.
Nov 27 15:36:28 pvesrv kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Nov 27 15:36:28 pvesrv kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Nov 27 15:36:28 pvesrv kernel: fwbr100i1: port 2(tap100i1) entered disabled state
Nov 27 15:36:28 pvesrv kernel: fwbr100i1: port 2(tap100i1) entered disabled state
Nov 27 15:36:28 pvesrv systemd[1]: 100.scope: Deactivated successfully.
Nov 27 15:36:28 pvesrv systemd[1]: 100.scope: Consumed 16h 31min 32.116s CPU time.
Nov 27 15:36:28 pvesrv kernel: zd32: p1 p2 p3 p4
Nov 27 15:36:28 pvesrv qmeventd[3023256]: Starting cleanup for 100
Nov 27 15:36:28 pvesrv kernel: fwbr100i1: port 1(fwln100i1) entered disabled state
Nov 27 15:36:28 pvesrv kernel: vmbr1: port 2(fwpr100p1) entered disabled state
Nov 27 15:36:28 pvesrv kernel: device fwln100i1 left promiscuous mode
Nov 27 15:36:28 pvesrv kernel: fwbr100i1: port 1(fwln100i1) entered disabled state
Nov 27 15:36:28 pvesrv kernel: device fwpr100p1 left promiscuous mode
Nov 27 15:36:28 pvesrv kernel: vmbr1: port 2(fwpr100p1) entered disabled state
Nov 27 15:36:29 pvesrv kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 27 15:36:29 pvesrv kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Nov 27 15:36:29 pvesrv kernel: device fwln100i0 left promiscuous mode
Nov 27 15:36:29 pvesrv kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Nov 27 15:36:29 pvesrv kernel: device fwpr100p0 left promiscuous mode
Nov 27 15:36:29 pvesrv kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Nov 27 15:36:29 pvesrv qmeventd[3023256]: Finished cleanup for 100