Search results

Sorry to dig up an old thread, but what is the status of this in Proxmox 7? I have a couple of virtual disks mounted over CIFS at the moment and I'm not too impressed with the performance, wondering if this is the way to go.

I know this is a slightly old thread now, but it is one of the top results on Google at the moment - did you ever find a solution for this problem?

Howdy folks, This is less of a support request, and more of a heads-up that this can happen. I've accepted my data is gone and I am now restoring a backup. I had a basic test VM based on Win11 (Legacy BIOS boot) that I was working on. Single VirtIO SCSI boot disk. I made some changes and then...

Yup, it links here so I figured an update can't hurt.

Came across this today - ugh. I would be understanding if perhaps it would check for VMID conflicts prior to joining the cluster (and throw an error if there was a conflict), but flat out refusing to join a cluster if I have a VM is rather annoying. That said I can see there are workarounds so I...

Right now I'm using CIFS. It's okay, but I feel that Proxmox struggles with this sometimes. For example, I tried creating a virtual disk for my Proxmox Backup Server - unfortunately this lead to backups that failed to verify. That said I have other virtual disks mounting over CIFS that works...

I can concur that it is still necessary to manually remove the config files after removing the node, even in Proxmox 7. Is there a reason this isn't in the wiki?

Thanks for the link - I will definitely check it out.

Unfortunately it is necessary if you want to avoid conflicts, especially with things such as backups. I have three Proxmox hosts that have been converged into a cluster - and some of the VMs use the same ID. Therefore I must change the ID to avoid issues. Otherwise I wouldn't bother. Personally...

The inability the rename the VMID has to be one of my top pet peeves with Proxmox. It's an ID that should be unique, yet it cannot be changed? I'll try this script, but still a bit frustrating that we have to jump through hoops to do some basic tasks. Backing up and restore isn't an option...

Just wanted to chime in to say that backup options of the Proxmox host configs are still severely lacking. Even something within the GUI that would spit out all the configs to a text file (like what you see in a router) would be better than nothing. I had a host SSD fail and it has been hell...

This Wiki Article suggests that the Ballooning driver is a source of performance problems. https://pve.proxmox.com/wiki/Performance_Tweaks Is this still the case on Proxmox 7?

I am experiencing the same checksum error. My underlying storage is fine, no errors. Quite concerning that my backups don't actually work, good thing I am just trying to move my VM between hosts.

Hey guys, just wondering if there was any plans or ways to rename Proxmox 7 hosts? It has been out for a little while now.

Yep this is one of the things that I was hoping Proxmox 7 would resolve. Alas, it appears to be an ongoing issue :( The only way that I've had success is to backup all my VMs, reinstall Proxmox, and restore all my VMs again. It's kind of a pain to do though.

I can concur that the wiki post is hot garbage and you will ruin your Proxmox host if you try this. Good thing I tried this in a lab first. Encountering the same issue where the nodes folder contents refused to copy. Gave it another reboot, and not sure what has happened, but now the entire...

I've performed this on a handful of systems, and so far I have mixed results: 1. On both AMD systems that I tried this on ( AMD Turion X2 TL-50 and AMD Turion II N54L) CPU frequencies were stuck at 800Mhz and performance was pretty bad. I've only tried this on Intel systems that are running...

Thanks. I double checked my repositories and I believe I messed up sources.list for non-subscription. Updated it with the correct lists and it all appears to be working now.

Yes, I pressed CTRL + F5. Here's a screenshot: https://i.imgur.com/iddFBzA.png Here's a paste of the output: root@pve01:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve) pve-manager: 5.4-11 (running version: 5.4-11/6df3d8d0) pve-kernel-5.0: 6.0-5 pve-kernel-helper: 6.0-5...

I followed the steps here and whilst the pve5to6 checklist says that I am on Proxmox 6, it still shows 5.4.11 in the WebUI. Is this a bug? https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 Am I missing something? It is also showing 41 packages that can be upgraded under "origin: Proxmox"...