Kleiner Typo: du hast ethtool enp0s31f5 getippt, die NIC heißt aber enp0s31f6. Darum kommt nur "No such device". Der erste Screenshot ist aber interessanter. Nach dem Boot gibt es vmbr0 gar nicht und die NIC ist ohne Carrier DOWN. Das hat nichts...
Same exact issue here under Windows 2025 Hyper-V Server attempting to install as a version 2 Hyper-V VM with BOTH the new proxmox-ve_9.2-1.iso or proxmox-backup-server_4.2-1.iso. Something has broken.
Proxmox Development: Please fix this. Be...
Linux and Windows guests get handled differently. Windows will claim and zero all RAM at the VM start - which causes the VM to use your entire allocation just seconds after boot.
Ballooning and KSM will kick in at about 80% of your host systems...
You seem to be fairly alone in that desire.
ETA: Holy crap, that script is UGLY. Completely unreadable 4000-character lines with DOS line terminators. You have got to be kidding with that.
It sounds like we may have different views on the intended use of the forum. In my view, forum posts are not the ideal place for large code dumps, particularly ones approaching 16 KB, let alone 128 KB.
For larger code samples, a repository or...
Hi @shodan ,why not post this script on github and provide a link?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I wouldn't have suggested that path if it was going to be a major problem. But plenty of people have had issues with adding/removing hosts and as stated in the documentation, there are specific requirements and limitations as well that can catch...
I think enough tokens were spent on this banter. Best of luck!
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I think enough tokens were spent on this banter. Best of luck!
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
yeah I dont see anything in those links to suggest difficulty.
and the only thing that changes for local vm migration is that the target will have to be on a clustered storage- which is still easiest handled via storage migration in cluster.
I mean, any way you slice it, it's a 45 page explanation
even if I gave all the extra manipulation to publish four service unit files and copying them in the right place and doing all the stuff by hand.
This
Is still what you end up with
And I...
Security trade-off -> yes that is precisely the difference between setting it to lazy strict and passthrough, #notabugwontfix
Overengineered or "needs rollback and extra validation ?" Well, which is it ?
Code duplication
Hmm, ok, this...
Here are links covering some of the various restrictions and items to be aware of:
https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_join_node_to_cluster
https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_remove_node
Side note: the poster...
Some of us like to know what it is we're running as root.
So you're going to put it on the eventual users to each individually reformat your thing to make sure it is reasonable and that your account hasn't been hacked by someone who is...
Some of us like to know what it is we're running as root.
So you're going to put it on the eventual users to each individually reformat your thing to make sure it is reasonable and that your account hasn't been hacked by someone who is...
All the LLMs have the very useful "sceptic" mode. I find it invaluable. In fact pitting one against the other often gives you a more refined result.
Overengineered: Excessive code for a simple task, including custom TTY detection and ANSI color...