Search results

Thanks @fabian! As others have pointed out in many other threads with the same issue, this is not preferable as Proxmox handly takes care of a few things during install that Debian does not. This is also a less clean method. This issue seems to be quite prevelant - could we not have non x...

I just tried an install of this on an Intel NUC 11 Pro (NUC11TNKi3). It gets stuck at starting a root shell on TTY3. If I switch to TTY3 there is an xorg error about cannot run in framebuffer mode. All the troubleshooting I can find about this mentions AMD Ryzen and AMD gfx cards :/ Edit: no...

Congrats! I moan a lot here (especially around documentation!) but the reality is you are doing amazing work and I've learnt so much playing around in a homelab. Thank you!

If VM ballooning allocation only kicks in if RAM usage on the host is below 80%, then I don't think a Proxmox host using ZFS and ballooning are compatible. ZFS gobbles up RAM - sure it will release it quickly enough if the host OS needs it, but from the above it sounds like Proxmox will never...

Thanks - this is still an issue I've just come across again, running the latest version of Proxmox. And I'm not the only one https://forum.proxmox.com/threads/vm-efi-boot-corrupt.82922/

Same problem here. FFS :/

I have a similar issue. I have a dead node, it shows in the GUI, but I cannot delete it because pvecm nodes doesn't even list it, and pvecm delnode proxmox1 throws: Killing node 1 Could not kill node (error = CS_ERR_NOT_EXIST) error during cfs-locked 'file-corosync_conf' operation: command...

OMG. I was trying to run some tensorflow code in docker on a VM this morning. Was getting Illegal instruction (core dumped). Lots of googling, came to the avx instruction set missing conclusion. Didn't think it would be possible, but changing the processor type to host worked. Thank you...

Lol this is still a problem. I removed a gluster storage config. Tried to readd it: create storage failed: error during cfs-locked 'file-storage_cfg' operation: mkdir /mnt/pve/glusterfs: File exists at /usr/share/perl5/PVE/Storage/GlusterfsPlugin.pm line 303. (500) Then noticed on the pm nodes...

Hi, Last night one of my VM's failed to backup, and worse, Proxmox left it in a powered off state. There is not much to go on from the logs, is there anywhere else to see what caused this? Task viewer: Backup Job INFO: starting new backup job: vzdump 100 101 103 104 --mode stop...

That is fair enough I suppose! Thanks.

I'm groaning about the fact that "Cloning the disk over the network is currently not implemented". Instead I just tried to migrate a server, but it seems like Proxmox migrate totally ignores thin volumes, and doesn't use compression. So the migrate feature is currently shifting 28GB worth of...

"For a linked clone to work across nodes, the template's disks have to be stored on a shared storage " No worries, I'll do a full clone! "Oh that won't work either" Why is everything simple so painful in Proxmox? Cloning is effectively the same as migrating except you don't delete the running...

Thank you @rioga!

Of couuuurse it's not. :rolleyes:

Running a single node Proxmox 6.1-8 environment Running a VM that is the HomeassistantIOS image Doing a backup in 'stop' mode to an NFS share Once the VM boots back up, I get BdsDxe: failed to load Boot0001 "UEFI QEMU HARDDISK QM00005 " from PciRoot (0x)/Pci....<some stuff>: Not Found I then...

The documentation on adding USB 3 devices to a running VM leaves a hell of a lot to be desired. Reminds me of the "draw the rest of the owl" meme. "USB3.0 qm monitor 804 device_add nec-usb-xhci,id=xhci,addr=0x1B,bus=pci.1 device_add...

The current instructions are: Incongrent with the default disk settings of Proxmox (VirtIO SCSI is the disk default in proxmox but instructions show vda/VirtIO) Don't acknowledge that the web UI can be used Show command syntax that doesn't actually work on recent linux distributions...

Just ran into the same problem also with Ubuntu desktop 18.04.3. Pretty unbelievable that proxmox doesn't smoothly work via the defaults with one of the most popular distros out there. FWIW I found VMware compatible display was very laggy, the VirtIO-GPU one seems smooth even at high resolutions.

The web UI doesn't allow upload of anything thats doesn't end in .img/.iso though :(