Proxmox Thread - Home Lab / Virtualization

Hi, I started dabbling in Homelab a few months back. Have a tiny pc with 12th Intel as my proxmox node and just added a NAS PC running TrueNas a week back.
I need advice from you guys about a peculiar issue I am facing. My TrueNas pc shuts down after some time on its own. There are no errors when I restart it using the hardware power button.
On my proxmox, I have a VM running a mediaserver using docker along with some LXCs for adguard, NPM, etc. It runs fine as long as the mediaserver VM is not running. But when I run it, the whole machine goes in reachable, even though the tiny PC is on. I have had it do this even while watching a video from the mediaserver through Plex. It seems high read write crashes it.
Any help, especially on the NAS machine shutting down would be much appreciated.
Check for power supply and heat issues.
Tiny PC might not have enough power for processor+disks, try a bigger brick, or not enough cooling.
 
  • Like
Reactions: rahuljawale
Check for power supply and heat issues.
Tiny PC might not have enough power for processor+disks, try a bigger brick, or not enough cooling.
Yeah, power could be an issue. Heat unlikely as it has a fan, plus it doesn't feel hot or even the fan doesn't run at high speed while streaming videos. Thanks for the hint about power. Will try a bigger powerbrick.
 
  • Like
Reactions: napstersquest
web scraping and price comparisons

The most profitable time of the year (cyber monday weekend) and the electricity board is asking me to choose between 120V or 320V:

Screenshot 2024-12-01 at 11.50.07 PM.png
 
hey Proxmox experts - need ur inputs

I am currently running Proxmox on a 512gb Gen 4 nvme ssd, the usage is very less not more than 100gb overall, running few VMs and LXC containers, that's it.
I have a spare 256gb nvme which is gen 3 and 100% health

- I now want to replace the 512gb ssd with the smaller capacity 256gb.. what is the easiest process?
- will clonezilla work fine for cloning the SSDs? and I can u just swap the devices and I am good to go?
- what about the storage partition size differences?

local(pve) has 100gb partition
local-lvm(pve) has 375gb partition
 
Clonezilla used to work years ago with PVE 6, when going to a larger drive. It's never worked for downsizing or upsizing on 7 or 8 for me.

It's because the thin-pool complicates things.

The quickest way is to backup your vm's, and install proxmox on the new drive, and then restore from backup.

Everything else is just not worth the frustration, and this is from experience as I've done this almost every month the last few years.

Backup, new install, restore is also the quickest way to change ip or host name. Every other way is a time sink.

Mount a usb sata or nvme enclosure with an older ssd and use that for backup/restore.
 
  • Like
Reactions: MarioBros
I agree. Easier to backup the config, install in new drive and restore everything.
Downsizing is something I thought was easy but got complicated real fast
 
  • Like
Reactions: MarioBros
Clonezilla used to work years ago with PVE 6, when going to a larger drive. It's never worked for downsizing or upsizing on 7 or 8 for me.

It's because the thin-pool complicates things.

The quickest way is to backup your vm's, and install proxmox on the new drive, and then restore from backup.

Everything else is just not worth the frustration, and this is from experience as I've done this almost every month the last few years.

Backup, new install, restore is also the quickest way to change ip or host name. Every other way is a time sink.

Mount a usb sata or nvme enclosure with an older ssd and use that for backup/restore.
I though cloning the disk would be much easier...
the backup, install PVE on new disk & restore worked perfectly, I had followed this method a year back and it had worked

I have already set static IPs for those VMs and containers, so it was a breeze after restore..

thank for ur inputs..
 
  • Like
Reactions: rahuljawale
i am struggling with the iOMMU group id issue

1735492594250.png



initially i did setup the proxmox and put sophos firewall and passed the nic group and post reboot the iommu group iD remained constant. later on i did introduced physical hard drives and passed it to OMV post that i am facing the IOMMU id keeps on changing because the mapping breaks and my WAN remains down my managment interface is through onboard nic , isthere anyway to over come this issue ?


1735492970298.png
 
Looks like you've run into a known issue: https://www.google.com/search?q=pes12n3a+iommu

The IDT PES12N3A PCI Express Switch is a device that can cause an error when two 82576 devices are connected.

Generative AI is experimental.
[1] https://docs.redhat.com/ja/documentation/red_hat_enterprise_linux/6/html-single/6.0_technical_notes/index

But you could always go the more robust route (ha) — don't pass through network ports. Make a bridge in Proxmox and connect a virtualized port from the VM to the bridge. Use VirtIO:

Screenshot 2024-12-30 at 4.07.26 AM.png

There's barely, if any, performance hit. I run all my virtualized routers this way. I pass through only hard drives and SSDs, sometimes graphics cards and USB ports.

Screenshot 2024-12-30 at 4.03.11 AM.png
 
Looks like you've run into a known issue: https://www.google.com/search?q=pes12n3a+iommu



But you could always go the more robust route (ha) — don't pass through network ports. Make a bridge in Proxmox and connect a virtualized port from the VM to the bridge. Use VirtIO:

View attachment 218711

There's barely, if any, performance hit. I run all my virtualized routers this way. I pass through only hard drives and SSDs, sometimes graphics cards and USB ports.

View attachment 218710
so you mean to say i need to assign physical nic to a bridge ( a seprate vlan and than pass that bridge onto the Sophos FW ?
 
You got the first half right, yeah, assign a nic to a bridge vmbrX in the network settings of the proxmox node, then in the hardware page for the Sophos VM, assign as many virtual network cards as you need, with the VirtIO driver, and connect that to the bridge like so:

Screenshot 2024-12-31 at 7.40.01 AM.png

In this case, Proxmox will handle communication between the VM and the physical interface, and function as a virtual switch to everything connected to that bridge. It's pretty fantastic. You could have a bridge for the LAN side and all the VMs can communicate through that and the firewall without even needing to have a cable plugged in.

Infact, you don't even need to have a bridge connected to a physical port, if all the networking is contained within the proxmox node. It can just be left 'floating' (my terminology).
 
  • Like
Reactions: ronnie_gogs
well this has been fixed for good

Logic
i am struggling with the iOMMU group id issue

View attachment 218680


initially i did setup the proxmox and put sophos firewall and passed the nic group and post reboot the iommu group iD remained constant. later on i did introduced physical hard drives and passed it to OMV post that i am facing the IOMMU id keeps on changing because the mapping breaks and my WAN remains down my managment interface is through onboard nic , isthere anyway to over come this issue ?


View attachment 218681
this has been fixed for good .

1735655839853.png




Microsemi is PCIE switcher .Allows communition for NIC port accross the whole card



So apart from passing 0000.0a.00 one has to also pass corresponding PCIE switcher with same IOMMU group id 15. i rebooted the system multiple times and no issue observed.

1735655767052.png
 

Attachments

  • 1735655410239.png
    1735655410239.png
    29.3 KB · Views: 5
  • Like
Reactions: rsaeon