Search results

I realise this is an older post by now, but still one of the top results on Google. Is this still an issue on Proxmox 8.x? I have a couple of hosts that I'd like to add swap to, and a zpool for swap would be the most convenient way to achieve this. That said, I wouldn't want to do it if it is...

When a patch arrives, probably in the next 2 months

I'm glad people still use this. I do wish that the Proxmox team would introduce something like OMV-Firstaid (for OpenMediaVault) - makes this sort of thing so much easier to deal with.

I don't think asking for an ISO that boots is unreasonable. This is software that businesses run on, after all.

I think some people mentioned even this did not work for them. Realistically, we need an updated ISO that doesn't break with common hardware. Any idea when a patched 8.0.3 ISO will be available?

I performed a UEFI installation. After Proxmox was installed, I was able to re-install my Nvidia GT 710, and it seems to be working fine. Definitely seems like a bug with the installer, I'd expect a patched ISO to be posted pretty soon.

I am also having the same issue. HP Z640 with Xeon E5 v3, 32GB RAM, and a standard Nvidia GT710. EDIT: The problem is Nvidia GPUs. I swapped my Nvidia GT710 for an AMD Radeon RX 580, and it progressed no issues.

Proxmox 8 is out now, is there a way to painlessly change the hostname yet? I ran into this issue again on Proxmox 7.4 and it is still highly frustrating that hostnames cannot be easily changed.

Ah, good to know, wasn't aware that this was a universal variable. Very cool. Thank you.

Not quire sure what you're asking for here - I just replaced $IFACE with my interface ID, in my case, eno1. Screenshot that might help: https://i.imgur.com/7POUGnu.jpeg

Howdy folks. I was recently given a Microsoft Surface Pro 4 with a swelling battery. I managed to remove the battery without too much trouble, and decided to use it for Proxmox as I figured it would be a pretty low power option as power prices are getting a bit crazy. Unfortunately, I seem to...

On my Surface Pro 4, this makes my display blank, but it's still on. Am I missing something? Edit: It may have been due to having nomodeset enabled in grub. I performed the following steps and it now turns my displays off correctly: Edit the grub bootloader nano /etc/default/grub Replace the...

Quite frustrating that this problem is still ongoing today... I had this issue around a year or two back, and put together a new Proxmox system (well, it's refurbished) and forgot about this bug. Workarounds did the trick thankfully.

Came across this today, was rather baffled by this as I had used LVM in the past. I guess the "workaround" would be to restore the snapshot first and clone as current. A little messy, but it does work in a pinch.

Just wanted to quickly chime in to say that I was in a similar situation and this guide worked perfectly for me. My situation was I was moving my PBS server to another Proxmox host, which was stored on a USB external hard drive. These are my notes: Discover the list of ZFS pools zfs list...

Okay, so this post may have just made me realise that I may have a bug in my Proxmox instance. This doesn't line up with what I'm seeing on my hosts. I think my host is applying Linux default settings to Windows based systems? This is really strange. Sorry for coming across as a bit annoyed...

Hey guys. So this is definitely a pet peeve more than anything, but I don't understand why Proxmox has chosen deliberately bad default settings for VMs. Here's my pet peeves after creating about 100 VMs: For starters, on the "OS Selection", choosing Windows / Linux / etc should ideally be...

Thanks for the info. If I ever get some time I might do some testing myself, so far I haven't really seen a difference.

Whilst this is an older thread now, I just wanted to chime in that I have experienced this issue as well. My example is a bit more realistic - I have a cloud hosted Promox host with 4GB RAM that was running some basic VPN services. Normally only 60% of the memory is utilised, and the largest VM...

Interesting findings. Do you have more information on how the performance was improved? What % difference are we talking?