Can you try and specify the bridge-vids 100-120 to start at 101 in the second example? Because the dedicated interface wants to assing itself a VLAN that the bridge already has.
By the way, you could also add it as it would look when you use the...
Same here with similar hardware :
MSI Z97M-DS3H with i7-4790k
my cmdline that workaround this problem :
BOOT_IMAGE=/boot/vmlinuz-7.0.2-5-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt libdata.force=noncq pci=nomsi
using older...
Hello,
I spoke to @PVasileff , he tested older kernel versions. That doesn't help. As far as I can tell it's related to disk creation and management.
On minihv (Qoton Q20332G9 S20) today we created 2 VMs:
- Alma 9.7, then updated - after the...
The deprecation itself was not strongly influenced by that, but the decision to communicate it more actively was in fact primarily driven by it. Normally, we only mentioned it on the side once a new kernel became the default. In the past, we...
@Upstairs_Cycle384 Not sure why Windows still detects it, maybe querying the CPUID leaf directly still works or something. Regarding the other question, there is a custom CPU model editor coming with the next Proxmox VE 9.2 point release. There...
something is a bit off kilter with one of our pve hosts, where snapshots and outbound migrations are slow, but inbound migrations are normal. to elaborate, inbound migrations traverse the network at ~5.5 gbps; which is about the normal rate those...
this is a vanilla install, when I try to force the if up , I get this output ..
root@proxmox1:~# ifup vmbr0.100 --force -v
info: requesting link dump
info: requesting address dump
info: requesting netconf dump
info: loading builtin modules from...
Hi Dominik,
Thanks for your reply!
Sure - happy to supply as much information as I can. So this has only begun since the latest update and reboot and can be replicated across nodes.
This cluster has gone all the way from PVE 6 with Ceph 16...
Hi Aaron,
If could either be like this
auto lo
iface lo inet loopback
iface nic7 inet manual
iface nic0 inet manual
iface nic1 inet manual
iface nic2 inet manual
iface nic3 inet manual
iface nic4 inet manual
iface nic5 inet manual
iface...
This indicates you added/mounted that disk using a systemd mount file. Hence it does not show up in fstab.
Probably check with:
ls /etc/systemd/system/mnt-pve-nvme2tb.mount -lh
# It maybe in another dir, so you'll have to check
I've never done...
Hi @fever_wits,
on the third server, could you first test the older kernel builds with ZFS support:
proxmox-kernel-7.0.0-3-pve
proxmox-kernel-7.0.2-1-pve
proxmox-kernel-7.0.2-2-pve
proxmox-kernel-7.0.2-3-pve
For each kernel, you can run...