Search results

You might hit this Bug with OVS: https://bugzilla.proxmox.com/show_bug.cgi?id=2475 https://forum.proxmox.com/threads/proxmox-5-4-to-6-0-strange-network-issues.56086/

Warum versuchst du NodeJS auf dem Hypervisor zu installieren?

Upgrade finished - both proxmox and ceph are up to date.

That's where I stumbled upon that known issue :-) Upgrading ASAP.

The log level on that node is too low but I identified a disk that might be failing. The ceph cluster is using CentOS 7, not Proxmox and it's running the official build that lacks the patch.

The ceph cluster itself is also on 14.2.4 and it uses WAL on an NVMe.

Looks like I hit this bug: https://tracker.ceph.com/issues/42223 https://ceph.io/releases/v14-2-5-nautilus-released/

Hi! I am observing a strange issue on one installation (3 Node Proxmox Cluster + external Ceph Cluster). Ceph is working fine as well as all other VMs. One VM, a Windows 2019 server crashs every night and loops with "No bootable device". When I boot recovery tools, I can see the disk but it's...

I've opened a BT: https://bugzilla.proxmox.com/show_bug.cgi?id=2475

@oguz Could you take a look? I can reproduce my problem with latest updates applied.

I've now tested PVE v6 (original distribution) and OVS is also broken. Same problem. If I deploy and set up a VM and attach it to a bridge (even without a tag), traffic does not flow.

Ich hatte das gleiche Problem auch, bzw. auch wieder nicht, denn ich arbeite grundsätzlich mit englischen Spracheinstellungen (VMs und Proxmox). Damit es da keine merkwürdigen Probleme gibt, melde ich mich bei Proxmox auch auf englisch an - dann passt auch die Tastatur in NoVNC. Stelle ich auf...

You did it! I've implemented a fix to remove the unneeded newlines. I've also applied your chmod fix. Works so far. I just need to adjust the naming of the OVS bridges.

I've now merged all interfaces into the main file. The server boots fine, all interfaces are up. The Proxmox GUI still does not list any interface and the assistant does not show them either. My config looks like this: https://paste.fedoraproject.org/paste/m10bUuSnNb-mKpXLX~k-tg Might be an...

The whole point for me and proxmox is the GUI. If I would like to add / edit VMs the hard way, I would use virsh / libvirtd :) What I have in mind is: Why MUST proxmox configure the network itself? Why not just disable that page, if such an unsupported configuration (which works) has been...

Either I do it wrong or it does not work. I have several interfaces, some OVS some LB defined using interfaces.d files from my CMDB. They work fine. If I try to add a VM, I am unable to choose any bridge - the list is empty and has a red border.

Same here... Why not implement reading them first? As the OP stated, they deploy the network config using interfaces.d files. I do the same with other tools. I don't like the approach of removing support for an OS standard feature from the Proxmox GUI (forcefully, as VMs can't use defined...

If I downgrade to kernel 4.19.0-6-amd64, everything works. There seems to be an issue with the 5.0/5.3 PVE kernel in this scenario.

Hi! I've moved some VMs from Fedora 30 KVM hosts to one running Debian Buster (virsh dumpxml / define). I need to clarify that I am not yet using a full deployment of proxmox, it's more a hybrid system of PVE kernel and QEMU. The VMs boot fine but their network is not working correctly. I am...