I updated to pve-kernel-5.4 (6.2-4). Ran my first test this morning by restarting my server with the USB flash drive plugged in. My VM recognized the flash drive. I unplugged it, the VM didn't freeze/crash, and I could see in the CentOS VM that it had been disconnected. I then plugged my next...
I updated to pve-kernel-5.4 (6.2-4). Ran my first test this morning by restarting my server with the USB flash drive plugged in. My VM recognized the flash drive. I unplugged it, the VM didn't freeze/crash, and I could see in the CentOS VM that it had been disconnected. I then plugged my next...
Dang. I just installed the following, rebooted PVE, and then tested this... and pulling the USB drive out of the server still locked up / froze / crashed the Linux VM that has the USB drive passed to it. Do you know why you also got pve-kernel-5.4.44-1-pve: 5.4.44-1? Edit: Looks like I just...
I'm not entirely sure anyone has acknowledged this as an issue to be fixed yet.
I think you would downgrade using something like apt-get install proxmox-ve-6.1-2, but you'd want to do a little more investigating before taking my quick comment. I have no clue what concerns there might be about...
I'm going to reply, but for some reason I'm no longer getting spammed with the idle time message even though I didn't add the -l flag.
Here's the pveversion -v output:
I'm running two containers and one VM.
All the containers are on local-lvm.
The log spam was always related to one...
Do you mind if I ask a side question here? Is there documentation on the difference between selection Skylake-Client or Skylake-Server? When I built my VM back in 2017, I think there was only an option for Skylake-Client. And when I attempt to switch it to Skylake-Server, the VM won't start and...
And here is the rest of the Messages logging:
May 25 13:42:04 pve kernel: [310966.170156] fwbr900i0: port 2(tap900i0) entered blocking state
May 25 13:42:04 pve kernel: [310966.170156] fwbr900i0: port 2(tap900i0) entered disabled state
May 25 13:42:04 pve kernel: [310966.170200] fwbr900i0: port...
Here is the Messages logging at the point that I disconnected the USB flash drive and the CentOS VM froze/crashed:
May 25 13:33:21 pve kernel: [310443.308499] usb 2-3: USB disconnect, device number 4
May 25 13:41:37 pve kernel: [310939.009120] fwbr900i0: port 2(tap900i0) entered disabled state...
Not much, but maybe I'm not looking in the right places? Here is what I have. With the Cent OS VM was running perfectly fine after booting it with the USB flash drive already inserted, I unplugged the USB flash drive and got the following log.
May 25 13:33:21 pve kernel: [310443.098278] usb 2-3...
I have Proxmox running a CentOS VM and two Linux Containers for a UniFi Controller and UniFi Video. I've included my VM configuration below. The system that runs on this VM has a nightly backup process that saves to a USB flash drive. As you can see in the config, I pass a USB port through to...
Yes, I had restarted the service and the server. I am running lxcfs.service without the -l flag. If I should have it, I can follow these instructions after hours later today.
[Unit]
Description=FUSE filesystem for LXC
ConditionVirtualization=!container
Before=lxc.service...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.