Search results

Moving the disk to another PVE storage and back to the ZFS can be done in the GUI and should be the "easiest" solution. If this takes too long, you can also set the attribute in ZFS via command-line interface.

Proxmox VE supports only raw images for VMs on ZFS storages. This is why the disk images get converted and the format is greyed out. Nonetheless, you should set the sprase flag (thin provisioning) in the configuration of your ZFS storage in Proxmox VE. See also...

Proxmox Backup Client ist für verschiedene Betriebssysteme verfügbar. Damit können Backups von physischen Rechnern, VMs und Containern erstellt werden.

What you could also try is setting the OS type to Vista or change extra CPU flag hv-tlbflush (this can be done in the GUI) There are a few similar problems in the forum https://forum.proxmox.com/threads/windows-guest-bluescreen-with-proxmox-6.56053/

Your packages look OK. Therefore, I suspect some networking problem. Can you access the Web GUI from any other browser or device? Could you please also post ip address ip route

Proxmox VE does not natively support (rootdir is missing in the content types list of the respective wiki page) LXC on GlusterFS. You can workaround by creating a directory storage on your GlusterFS storage. Nevertheless, it is still not possible to use qcow2 as LXC rootfs.

storage-id as in name/ID of the storage definition in Proxmox VE, in other words what you see when you go to Datacenter->Storage or look at the resource tree on the left or type pvesm status into the command line interface

If browser refresh doesn't work, then please post the output of apt update apt full-upgrade pveversion -v and perhaps apt install --reinstall pve-manager proxmox-widget-toolkit systemctl restart pveproxy pvestatd pvedaemon systemctl daemon-reload

In PVE 6 5.4 is default and 5.11 is opt-in In PVE 7 5.11 is default https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.4 Are your other VM settings the default settings? Because for me the installation worked both with CPU=host (Xeon(R) CPU E3-1231) and CPU=Westmere

Automatisch von DOWN auf UP setzen geht mit dem Stichwort "auto" in /etc/network/interfaces auto eno1 iface eno1 inet manual iface eno2 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.10.10/24 gateway 192.168.10.1 bridge-ports eno1 Wenn du rebootest und dann ist...

Thanks, repository and upgrades should be OK. What you can try to do about is installing a more recent kernel (5.11 is shipped with PVE) apt install pve-kernel-5.11 and reboot. The CPU type determines which CPU flags are passed to your guest. host means all flags from the host, whereas the...

Hi, I'd suggest upgrading your PVE version first! This should also fix broken packages Use apt update apt full-upgrade you can also post the output so that we can check if the PVE repositories are correctly configured

Seems like removing in the GUI has not worked. Have you tried removing it manually already?

Which certificates show up when you type pvenode cert info ?

Hi, I'd suggest upgrading to the latest version of Proxmox VE first. This might already be fixed. If not, could you please post cat /etc/pve/storage.cfg ?

Is there anything relevant in the syslog from the day when the network breaks down?

What updates do you mean exactly? Drivers, firmware, Proxmox VE?

Virtual or physical disk? How was it attached to the VM?

Hi, to avoid such problems you should use uuids instead ls -lah /dev/disk/by-uuid

Both LVM and LVM-Thin only support .raw images in Proxmox VE. qm importdisk silently ignores invalid storage-format combinations.