Search results

Just ran into this myself. For some reason, I was getting "EFI variables cannot be set on this system" error when running through @Confined6999 instructions above. I ended up running "proxmox-boot-tool init /dev/nvme0n1p2" to fix it. Booted fine after that.

Have you tried using systemd.automount in the options?

Yes, also ran across this issue too. I did find another post about it, but looks like this one has more action. Basically same issue on Proxmox 8.1.3(on I5 12450H cluster) with a Debian guest. Variations of migrations using a virtio NIC and KVM64, Qemu64,x86-64-v2, x86-64-v2-aes, x86-64-v3 and...

@sb-jw I just did some more testing with PCID turned off. I mostly had no issues on Debian 12 using a virtio NIC. I did have 1 failed migration using x86-64-v3, but tested it again and it went fine. Forgot to mention, CPU arch is an I5-12450H.

I actually just noticed this a couple days ago. Found a reddit post where someone else had stumbled across it as well. On that post, they referenced noticing it with an Ubuntu vm after migration. I did some testing with a fresh install of Debian 12 and Windows11 using a Virtio NIC. Windows had...

My setup is pretty simple at the moment. 2 Hosts, both with 10 GB fiber. Backup is to spindle disks via a CIFS mount. VM's are on a Host with SSD's using qcow2 disk images.

I've have actually noticed the same, but in my instance, the performance dropped from a recent upgrade from v4.4 to v5.3. bwlimit was set to 524288 on v4.4. I have tried setting to 0 on v5.3 with no change. Processor sits at about 20% throughout the backup process. Network is 10G fiber backing...

What would you configure to tag the OVS bridge?

That's the example from the wiki page that allows the Proxmox host to communicate on the VLAN, not to tag the bridge. Unless I'm misunderstanding you. Here's my current /etc/network/interfaces. Basically, just Linux bridges for all vlans and a untagged vlan using OVS. auto lo iface lo inet...

Yes, I am familiar with the OVS wiki page. There is no example in there that shows how to do 1 vlan per OVS bridge that is tagging all bridge traffic, as in example 1 with Linux Bridges above.

Ok, I guess I hadn't tested the Linux Bridge without the vlan aware option. I'll test that out. And, when I try to create an OVS Bridge with port eth1.55, I get an error, unable to find port.

Ok, just a follow up. Looks like most of this was a hardware issue from my quick testing. I had plugged into, what I thought was, port eth1. Although, I had replaced the motherboard on my proxmox host a couple months back and realized in my testing that eth1 wasn't UP. I then noticed my new udev...

I'm running Proxmox 4.4 w/ OpenvSwitch installed. I recently grabbed a 10g sfp+ card for the server and have it trunked to my firewall. vlan 1 is native and untagged vlan 10 is tagged vlan 20 is tagged vlan 100 is tagged What I'm trying to do seems to be running me in circles. I've rebooted my...

I just wanted to verify that if I have a storage backend that is exporting iSCSI LUN's, that Proxmox currently doesn't have a file system like VMFS that you can put on top of the LUN which supports snapshots and live migration. I've got some test gear up, and it appears the only way to do this...

Thanks for the update!

I gave my node a restart and that seemed to clear out the /sys/fs/cgroups/systemd/lxc/121* duplicates. I'm wondering if there is something that isn't cleaning up correctly with containers?

I'm noticing a similar issue. My /var/log/lxc/121.log are full of lines like: directory lxc-start 20170306022553.225 ERROR lxc_cgfsng - cgroups/cgfsng.c:create_path_for_hierarchy:1317 - Path "/sys/fs/cgroup/systemd//lxc/121-2" already existed. lxc-start 20170306022553.225 ERROR...

@manu In my case, the OVS service was up and running, but networking was unresponsive on Host2 only. I tried restarting the OVS service without luck. This isn't the first time an OVS update has killed networking in my environment, which isn't that elaborate. Oddly enough, only Host1 upgraded...

Oh nice, didn't know there was a needrestart package. I had 1 of my 2 hosts lose network connectivity after the latest ovs update. I'll see if this needrestart package helps in the future.

Well interesting.... I was hoping more people would come across this issue, I guess we're special. :) Since losing networking to the openvswitch packge upgrades and getting the management ip restored in a hacky fashion, I figured I'd try downgrading openswitch to 2.3.2-3. This didn't appear to...