Then I don't get, why this issue shows " that such things will really keep proxmox far from "production ready" ( from this thread) unless it is stated somewhere". It's clearly stated at each login that one shouldn't use no-sub in production. So...
This was exactly my point I wanted to make since somebody in this thread argued that things like the current isse might led to companies considering PVE not "production-ready" for enterprise environments. And this is nonsense: In an enterprise...
It is a bug and has since been fixed (fix waiting approval). Non volume mountpoints (e.g. externally mounted) are excluded in the future from changing file-permissions when bound. Means attribute-preservation will get removed for these kind of...
I hope I'm mistaken, but it seems like the content describes a single VM mirroring virtual disks located on two NAS devices.
If I'm mistaken, I apologize.
If the understanding is correct, this configuration should not be used because delays...
This was exactly my point I wanted to make since somebody in this thread argued that things like the current isse might led to companies considering PVE not "production-ready" for enterprise environments. And this is nonsense: In an enterprise...
Isn't the point of the test & non-subscription repos that bugs can happen and thus us reporting them and it getting fixed is part of the process? I would go to enterprise branch but for my homelab purposes I'm not sure if even the community...
I am also having this issue, fresh install of 9.1 today even after upgrading via apt to 9.1.5, any of my Tagged vms dont work. im coming off a hardware failure and 3 installs so im hoping to find a fix that doesn't include a 4th install of 9.0...
Isn't the point of the test & non-subscription repos that bugs can happen and thus us reporting them and it getting fixed is part of the process? I would go to enterprise branch but for my homelab purposes I'm not sure if even the community...
Ich weiß ja nicht, mit welchem Dateisystem du Proxmox jetzt installiert hast :-) Entweder Du hast "local-lvm", oder "local-zfs" bei Dir, da werden die VMs dann mittels Blockstorage angelegt.
I added this line and it wiped it except for UUID, so I grabbed my actual UUID with `dmidecode -s system-uuid` ... (Edit: did it through GUI it stayed)
I added a randomized Intel MAC address ...
I added `args: -cpu host,-hypervisor,kvm=off` ...
ok, ich habe es versucht. Ich habe Proxmox auf einer Partion von 50Gb (von 900GB) installiert. Aber wie komme ich dann an den Rest unter Proxmox dran? In der Weboberfläche sehe ich nichts, was auf den Rest von den 900GB hinweisen könnte. Die...
Is this just wishful thinking? Or is it a procedure you've verified, backed by evidence and proven results, that anyone would find convincing?
I, for one, would not entrust my systems to the company that proposed this.
Ok, aber für solche Dateien hat man doch in der Regel ein NAS. Ich habe selbst noch nie eine Nextcloud „gebraucht“, weil ich meine Daten bequem auf dem NAS ablegen kann. Ich persönlich würde meine Daten nicht direkt auf Proxmox speichern, sondern...
Is this just wishful thinking? Or is it a procedure you've verified, backed by evidence and proven results, that anyone would find convincing?
I, for one, would not entrust my systems to the company that proposed this.
Forget btrfs and go with zfs mirror, it's supported in the installer and there is actual official doc on it. Tested and works.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_change_failed_dev...
WOW, three lines of code, and the job is done:
lvremove /dev/pve/data
lvresize -l +100%FREE /dev/pve/root
resize2fs /dev/mapper/pve-root
Massive THANK YOU :)
For others coming here for the same question:
local-lvm
- Remove local-lvm from the storage configuration of the Datacenter
- Execute the following commands on the node's console:
lvremove /dev/pve/data
lvresize -l +100%FREE /dev/pve/root...
You confuse lxcs ( Linux containers) with lxd ( Software for managing vms and lxcs) Both lxd ( and it's fork incus) and ProxmoxVE manage vms and lxcs. Lxcs are more lightweight than vms but only work for Linux applications since they run directly...
Was? Das prunen geht eigentlich recht schnell. Die garbage-collection oder verify-Job werden bei hdds aber immer lange dauern, weil beim PBS der Datenbestand in zig kleine Dateien ( Chunks ) aufgeteilt wird und jeder (!) chunk dafür eingelesen...