Search results

I received help from Proxmox support and it worked. I'm posting their solution here because I've seen so many others with the same problem. One note: I don't need audio on this system. This solution worked. In my case the VM with the issue was VM 108 ***************************************...

Never mind. I did a restore of an older version onto the older Proxmox then manually did all the updates that were lost. My original problem still exist as I can't start the VM in the current version of Proxmox but at least I can open a copy of the VM in the old version now so I'll close this...

As per my other thread, which has had no replies, I have a VM that won't start due to the updated Proxmox and audio conflict. I'd like to move the VM to an older version of Proxmox so I can at least run it until someone figures out the problem on the new version. But... I can't create a...

I have been unable to find a solution. I'm assuming the VM won't start because of an audio driver issue created when I updated Proxmox but I don't know that for sure. I've tried several combinations of audio drivers which does change the error, but so far I haven't found anything that allows it...

Important update: I restored a backup file created before the power failure. It will not start either. I'm now convinced that something in Proxmox has changed that's causing the VMs not to start since both this VM and the backup VM had been running fine. It looks like some sort of audio...

Windows backups are ... lacking. I've had to do some rebuilds when hardware has failed and trying to restore from a Windows backup is pretty disappointing. You have to reinstall everything and reset everything. Many software licenses only allow for limited installations so you burn a license...

I have a friend who owns a small business. I've been telling him about Proxmox (which I love) and I think this might be the right route for him but money is tight. He really only needs one VM which would act as his Desktop machine for him. He works from home and sometimes from the road so he'd...

I hear what you're saying and I understand. I've been using Proxmox for many years now and I don't think I'm that much of a non-typical user. I'm a small business owner trying to get by in a cruel world. While I'm maybe not as much of a noob as indicated in my message, I do consider myself to...

See this is what I'm talking about. To you installing Debian is "simply" but to me it's not. I would have to figure where to get it, how to determine what version to get, and what items to select during the installation that are needed by Proxmox while also not installing things that aren't...

But if you download the ISO and are doing a clean install, you don't have Debian installed to even run scripts with. It's a blank HDD which is typically the way I install Proxmox and it's what I've always been told is the preferred way to do the install. So it seems like a clean HDD using the...

I'll throw my two cents worth in here. I LOVE Proxmox but I am not a Linux guy. I admit that I'm one of those guys who either needs an installer or I need line-by-line instructions that I would then need to manually enter onto the other computer. Same with GUI. Without it the software is much...

Perhaps. The VM has been running for months. But I don't think I've ever gone in to edit or change the hardware since the VM was created. I only have a few VMs running and it's pretty rare that I touch them.

I see now that the hardware says Display VirtIO-GPU (virtio) while all the others say Default. How would that one VM have been changed just by doing the update and restarting the VM? But yes, that was the problem. Thank you for pointing that out.

I did an update last night and as suggested I rebooted the host because of the new kernel. Almost everything works normally EXCEPT there is one VM now that won't open the console when I double click it or right click it and select Console. It just wants to save a .vv file instead of opening a...

I rebooted the version 8 server yesterday. This morning it's not showing an error on either server (never touched the version 7 machine). It looks like all backups ran successfully last night. So I don't know what caused it, or what fixed it, but it's currently working.

I have two Proxmox servers running currently. One is 8.03 and the other is 7.3-4 Eventually everything will be on the new server but I don't have all the vms moved yet. I see my backups are failing with an error trying to acquire cfs lock 'storage-NAS3' ... trying to acquire cfs lock...

Success! I I added the physical drive to the Datacenter Storage and set it as an LVM. It now shows up with the other drives. Funny.. this is about the 15th time I've set up Proxmox on a machine and I've had more trouble this time than all the other times combined. I don't recall going through...

Thanks. Working my way through that now having already done some of those steps from the earlier page reference. Question: in step 4 it has me creating a volume group. Do I still need to do that step even if I'm just adding a single drive or do I just skip this step in this case? And...

On the page you sent me to it says "We highly recommend to use a hardware RAID controller (with BBU) for such setups. This increases performance, provides redundancy, and make disk replacements easier (hot-pluggable)." so I'm not sure why you said earlier that it's discouraged. It looks like...

I use QEMU so I don't think the ZFS is an issue for me (it's never been a problem on my old server). I'm running almost all Windows VMs and I understand they work better with QEMU 2cows anyway. What I don't understand is why the 25TB drive only shows up as 264GB of space in Proxmox. The...