Hi, I`m new member on the forum, but I`m working with Proxmox for a while. I run into quite confusing problem and need advice. Below I will describe my problem and hardware on which I am working.
Host is a Supermicro AS 4124GO-NART with NVIDIA DGX A100 8-GPU 40GB working on my University...
Originally, I was getting a "detected old qemu binary (at least 3.0 is required)" error when I tried to boot up a VM. Since it's only a newly created VM, I decided to just delete and recreate it. Now every time I try to create any VM, I'm getting this error
I was trying to update my proxmox server and it has been removed from cluster after installing update,
When I have restarted the system I'm unable to access GUI and server accessible from ssh
But I need to take vm backup and my pve configuration file has been deleted
I have prepared...
hi, I'm attempting to setup a windows 10 vm with a Radeon pro wx 5100 passed through as the gpu. After following all the steps given in the guide for pci passthrough, I cannot boot the vm after repeatedly getting the error:
Today i'm co-fronting a issue, i have followed the tutorial like step by step but i can use my Nvidia Geforce on the VM with x-vga i don't know why
dmesg | grep ecap to be sure than remaping is supported/or not supported
Planning to migrate from Unraid's KVM over to Proxmox (plus MergerFS & SnapRAID and Docker, etc). During VM testing, I've found that I cannot boot a VM that I migrated over. I've searched the forum and all I've found is one thread that said this should just work, but I can't for the...
yesterday, I wanted to try out the latest Ubuntu LTS version 18.04.2 and installed it as a normal VM on my PVE-Server (v.5.3.9). Unfortunately, it wount start after installation has completed. After removing the ISO from the drive the startup is stuck in the fsch dialog as displayed in the...
I had my pve host shutdown for a few weeks while I was on vacation.
After starting it again I am unable to start any of my VMs.
This is the error message I get:
Could not open '/dev/pve/vm-101-disk-1': No such file or directory
The odd thing is when I click on "local-lvm" on the summary...
I recently had a problem starting up a VM on an updated cluster (4.4 to 5.1). I did everything according to the guides, first updating and rebalancing the ceph pool and then doing a dist-upgrade one node at a time. Everything is documented very well and the process is straightforward...
vllt. könnt ihr mir helfen. Meine VM startet nicht. Es ist Ubuntu Server 16.04. KVM Virtualisierung wurde bereits auf "no" gestellt. Cache ist auf Write tough.
Hier ist der Log vom Start:
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -chardev...