Search results

Oh: https://forum.proxmox.com/threads/proxmox-8-1-upgrade-and-secure-boot.136973/

Does this mean that the process to enable SB is undocumented/unsupported despite upgrading to 8.2?

A clone from a linked clone will inherit the base drive?

Same question here. Also, what permission is associated with rollback operations?

This should be a sticky. Dunuin's solution is what I came up with on my own ages ago, you would have saved me some time!

UPDATE: 722 based, not 710.

This is actually keeping us from configuring a new PVE host successfully. The M/B is a Supermicro one with a Xeon Silver gen2, and two 10G SFP+ NICs, 710 based. It fails with VLANs configured.

Hi edo, I must check in with some news: my problems seem to have been compounded by two things, one is OVS, the other is PHY-related with a Mikrotik L2 switch: The ethboot port (PoE input) is 1g and connected to its own PHY, which is "bridged" to the 10G PHY. I used it untagged in an isolated...

I'm observing packet loss on vmbr1 and ruled out the firewall and switches involved (tested and verified with iperf3 in UDP mode and manually checking with snmp). I'm using OVS... my only gripe at moment is that I initially moved to OVS so I could configure spans/mirror ports for some VM guest...

Experiencing this kind of packet loss myself for one container and there is no duplication of MACs.

Some tests, running nc -l 4545 inside the guest (-k as option): client date | nc -N guest 4545 inside a loop: Thu Oct 14 15:38:44 CEST 2021 Thu Oct 14 15:38:44 CEST 2021 Thu Oct 14 15:38:44 CEST 2021 Thu Oct 14 15:38:44 CEST 2021 Thu Oct 14 15:38:44 CEST 2021 Thu Oct 14 15:38:44 CEST 2021 Thu...

Hi, The host has a trunk connected to a secondary 10G switch that uplinks to a main switch aggregating multiplke 10G links via fiber. All VLANs are tagged. The secondary switch uses a 1g link for the VLAN that is tagged for the guest NIC, and this is shared to the trunk port used by the VM...

It was caused by an iODD external drive used to install the initial system and run some updates to the BIOS. 100% unrelated to Proxmox and Debian but at the same time, udevadm settle should time out gracefully. It's too obscure right now to figure out unless you trace the systemd process.

Hello, I'm trying to configure a new system with the following properties: One NIC exclusively for management, only gets untagged traffic (not used by VMs) One 10G NIC used as a trunk for the VMs (no need to have an IP associated with it for the host) One 10G NIC used as a storage/clustering...

Hi! I'm on it, already reviewing the 'blame' output. I can confirm udevadm settle is the real culprit, and it is mostly occurring when someone leaves an iODD "multi image" USB3 disk plugged. I think any drive that is dying/faulty will also cause this issue, or any controller that responds in...

How can we diagnose what is causing the udevadm settle to fail? I'm on this boat too now, unfortunately.

How did you identify the disk and why was it hanging boot??

Quick update: It might not be the culprit. The symptoms are: all requests time out for the Storage tabs (cannot access anything at all), or reports 'communication failure'. No NFS in use either.

Just narrowed down my search for the culprit of my boot issues to this: ░░ Subject: A start job for unit systemd-rfkill.socket has finished successfully ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ A start job for unit systemd-rfkill.socket has finished successfully...

I just found this thread after posting this: https://forum.proxmox.com/threads/vlan-aware-network-configuration-not-working.46930/ Also having similar issues.