Search results

Running and testing a new feature on non-critical services will hopefully improve it. This is a test environment to see how it works. I will lose no sleep if I abandon the attempt in 6 months.

I'm testing the new OCI feature in PVE 9.1. Overall, it is working well for my use case. How are people dealing with persistent data? For example, in Homepage, the image I've been testing with, most of the configuration is stored in /app/config, and I would like to have a way to make it persist...

I know this is a dated, but I just wanted to add that this solution worked for me on Proxmox VE 9 for passthrough of a motherboard based SATA controller to a TrueNAS VM. No drives from the controller are in use on the PVE host so it is safe to blacklist passthrough.

I finally logged into the mobile interface for VE 9. I'd like to give a massive kudos to the folks working on that. It is a really great improvement over the VE 9 mobile interface. Thanks!

I’m interested in the same thing for my Home Assistant vm that is using a coral tpu.

My issue might be that my PVE host is still on Proxmox 8. I'll investigate further.

I’m still using Proxmox 8.

For reference, I had no issue updating one of my Debian 12 LXCs to Debian 13. It's not using DHCP and isn't a fresh install, but if you have a tested backup setup for your LXCs and want to upgrade it seems to be working. I stand corrected. The Debian 13 LXC ended chewing up all the CPU...

I was having the same issue described here with two different Proxmox servers. I updated /etc/network/interfaces as below, and it solved the problem. Thanks for the guidance! iface vmbr0 inet manual bridge-ports enp4s0f0 bridge-stp off bridge-fd 0...

One additional note. I'm using hardware pass through on a number of VMs. The "Data Center" functionality for "Resource Mapping" works to deal with address differences for hardware between PVE cold backup hosts as long as you are consistent with the resource name between the PVE hosts. Of course...

@fiona and @chudak, Thanks for the feedback. I really appreciate it. The bit I was missing was restoring from the VM backup screen and selecting the Proxmox backup server as the source instead of local. Now that I do that it is working like a charm. Test your backups... Document recovery...

I have two PVE servers that are not clustered because do not want to keep both machines on 24/7 and I don't need hot fail over, particularly considering the cost of keeping both machines turned on 24/7. I run VM backups to a Proxmox backup server that is available when I run backups. I'm trying...

Thanks for the pointers. This helped me get things working!

Thanks! I had done enough poking to understand that I could treat it like a standard Debian host and do backups that way. It is good to know everything is in /etc/pve. I'll do a little poking around in there and see if a simple backup of that folder is enough for my needs. I am mainly looking...

I've looked around and have not been able to find anything regarding backup of the server configuration. Is there a recommended way to backup the VE server itself (not backups of the VMs running on the VE server)? Thanks!