Search results

Just as a side note: Proxmox will store all relevat VM information including config on the main OS disk. Keep that in mind. You won't loose any data from the VM itself if it sits on healthy drive but you would need to rebuild the VM by hand

Mehr Speicherplatz schaffen - um es kurzzufassen.

Can you boot into Proxmox installer?

Yeah I know and as mentioned earlier you can ignore this during your installation.

No, you need to add this after you have installed PVE on your hardware.

I also enabled this feature - didn't harm any of my servers. The command should be added to either grub or systemd bootloader - depending on what you are using --> https://pve.proxmox.com/wiki/Host_Bootloader Simply add it there and rerun the config command to enable it. After that you should...

A quick search on the internet may indicate that your GPU is causing those error messages. You can try to install Proxmox anyway and see if it runs. Adding pci=noaer to your bootloader should solve the problem afterwards

(Fingers crossed that you have a backup.) You may try do the repair way: Create a new VM with the same vmid of your old Windows VM. Mount the existing disk to it and start the VM via a Windows ISO matching the version you had running. Maybe if you are lucky there are some things like "repair...

Nothing much to add here as my @Tmanok already did an outstanding overview what is possible and which paths you may select. The only thing which I would like to highlight is ZFS filessystem which can be installed on Proxmox itself, mostly any Linux Enterprise OS (if you want to go the DIY route)...

No as long as you did not do something totally weird with BIOS/UEFI Proxmox is not really bothering about it. What I do see and what might causes the problems is the line with "no device with valid ISO found..." - have you double checked that?

Currently you can only download the master branch, compile it and install it locally. But please note: If you enable any features from a future version there is no possiblitiy to go back to a current stable version.

Can you please send the output of pvecm status

Okay seems it was an invalid corosync configuration

I have reinstalled one of my Proxmox PVEs and wanted to join the cluster again. Unfortunately I am not able to as the GUI and the CLI wants to have two links? ! node 'proxmox1' is missing address forinterface number 1 Can someone please tell me what I am doing wrong?

I logged a bug report at Bugzilla for the Proxmox team to investigate: https://bugzilla.proxmox.com/show_bug.cgi?id=5306

I experienced the same issue and also added the kernel parameter now. Not sure if this is relevant or somehow related to but I am using four NVMe drives at a PCIe extension card with PCIe bifuraction enabled (x4x4x4x4) and one "disappeared"

Don't forget to mark this thread as "solved"

You can either create the VLAN tag on the VMs NIC interface or you create a VLAN at the network setup and use the VLAN NIC (e.g. vmbr0.100) at your VM

And can you also share which HDDs/SSDs you are using for this pool?

Ideally you would use a dedicated network just for storage = SAN, so would use the a dedicated network interface only for for Ceph. In general higher bandwith is a requirement for Ceph - I do not think that 1 Gbit is enought.