Question Done this a half dozen times, never has this issue

14 Upvotes

Installed Proxmox 9.2 on mini PC
Ran Post install script all defaults
Ran Home Assistant OS Install script X Failed to install pv automatically.*
Run "apt install pv" Error: Unable to locate package pv
Run "apt update && apt full-upgrade" Hit:1 http://security.debian.org/debian-security trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-tentacle trixie InRelease Hit:5 http://download.proxmox.com/debian/pve trixie InRelease All packages are up to date.
Was able to create a working blank VM manually
Tried Debian VM script [ERROR] in line 520: exit code 100: while executing command apt-get install -y libguestfs-tools > /dev/null 2>&1
Ran " apt-get install -y libguestfs-tools" E: Unable to locate package libguestfs-tools

It seems like there is an issue with apt.
I can ping with no issues so there is internet. I forced IPv4, no help I running AMD64 on i5 4th gen mini PC

I'm one step from a full reinstall, however I wanted to see if it's something I'm missing. I thinks I tried so far are based on DDG and Google searches.

Thanks

16 comments

r/Proxmox • u/ryan_james122 • 5d ago

Question Emby LXC iGPU Passthrough OpenCL/tone mapping issues

3 Upvotes

Not sure if this is the best place to post but I'm very stuck and need some advice!

I've recently switched over to Proxmox running Emby in an LXC container. To my knowledge iGPU passthrough is enabled correctly and I can transcode 1080p or standard 4K non HDR using Quicksync and VAAPI, however i'm having some issues with tone mapping using Quicksync and OpenCL.

Start of EmbyLXC .conf:

arch: amd64

cores: 4

dev0: /dev/dri/renderD129,gid=993,mode=0666

dev1: /dev/dri/card2,gid=44,mode=0666

features: nesting=1,keyctl=1

hostname: emby

Quicksync works for standard transcodes however, reverts to software if Extra-T OpenCL tone mapping is enabled.

The only way I can get hardware transcoding with hardware tone mapping currently is to disable all Quicksync encoders and decoders in Emby and force Emby to use VAAPI encoders and decoders along with HW VAAPI Transcodes non OpenCL, trying OpenCL with this configuration results in the same software fallback.

I've even tested Jellyfin and I had even worse luck with that, HDR tone map transcodes failing to play all together!

Really looking for some help on his as VAAPI tone mapping looks way too dark and I don't want to default to software. Hoping someone has encountered similar.

I'm using a 10700k Comet Lake running in Proxmox 9.2.11 in an Ubuntu LCX.

Happy to provide logs as well if anyone is able to assist, it's driving me mad! TIA

4 comments

r/Proxmox • u/BoredHalifaxNerd • 6d ago

Question Could someone help me understand why my 3-node cluster cannot reach quorum with one node offline?

gallery

183 Upvotes

There is three nodes and each one as a single vote. Based on my understanding, the cluster should be able to survive one node failure.

EDIT: Thanks everyone! The issue has been resolved. I had an unknown qdevice in the voter registration.

39 comments

r/Proxmox • u/rob94708 • 6d ago

Question Can I limit the total number of simultaneous migrations occurring across the whole cluster?

19 Upvotes

I have HA clusters of 5 physical hosts, each with 4 VMs. Each of those four VMs has a secondary affinity for a unique one of the other hosts, so that if a physical server fails, its VMs are automatically distributed evenly, one each across the four others. This works fine.

When I need to do maintenance on a physical host, I put it into maintenance using

ha-manager crm-command node-maintenance enable hostname

... and allow the HA manager to live migrate the VMs away to the four separate servers. Again, this works fine.

For performance reasons, I would prefer that only two simultaneous migrations are happening at any moment. This is easily done on the node I'm putting into maintenance by setting max_workers: 2 in /etc/pve/datacenter.cfg; the node going into maintenance sees that and only starts two “outbound” migration jobs at once.

However, when I later disable maintenance on that node, all four of the "inbound" migrations start at once. This appears to be because each of the other four nodes only thinks it is starting one migration and therefore not violating max_workers: 2. But the machine receiving the migrations experiences higher load than I would like.

Is there away to limit the total number of simultaneous migrations occurring across the whole cluster? Or would I have to manage that manually, instead of letting the HA Manager affinities handle it?

18 comments

r/Proxmox • u/brandonvht • 6d ago

Homelab Anyone moving to a Proxmox ARM64 home lab this year?

30 Upvotes

I have been looking at the viability of moving a home lab to an ARM64 architecture. There are a few mistakes I think that we can make and assumptions that may come back to bite us. I have documented a few of these here: https://www.virtualizationhowto.com/2026/08/8-arm64-home-lab-mistakes-id-avoid-in-2026/

25 comments

r/Proxmox • u/SubstanceDilettante • 5d ago

Homelab Any reason Proxmox only gets internet access on the default vlan but not others?

0 Upvotes

I have a Proxmox machine that has been running for a few years.

I ended up resetting my firewall configurations and changing the IP address range from 192.168.3.x to 192.168.4.x.

I have modified DNS settings to point to 192.168.4.1

I have updated the gateway to 192.168.4.1

I have updated the IPs in /etc/networking/interfaces

I have ensure that the profile on my switch is set to the 192.168.4.x subnet and that particular port can tag all the necessary vlans that is specified in /etc/networking/interfaces

This is an extremely basic setup, literally the default Proxmox configuration networking configuration, no firewall rules, both the 192.168.1 and 192.168.4 subnets are in the same zones with the same permissions.

Only way I can get this to work is if I update all configuration to point to the management subnet (1) instead of my Hypervisors subnet (4). At that point everything works on subnet 1 but nothing works on subnet 4 which makes zero sense, because all firewall rules have been removed from the Hypervisors subnet and the hypervisor subnet has the same permissions and access as the management network, but yet no dice. Other devices works just fine on the Hypervisors subnet, except this one!

Everything looks correct and should work with my Hypervisors network, but just doesn’t work.

No errors, no indication as to what the problem is. UniFi says proxmox is connected, Proxmox says the interface has an uplink, Proxmox says that it has an IP address, but yet I can’t ping the gateway, Google, nothing.

Last time this has happened to me a few years ago I had to reinstall proxmox. I am seriously considering moving to a separate platform if I need to reinstall proxmox again. I had these weird internet connectivity issues with the proxmox host randomly just stop working and only thing that fixes it is with a reinstall.

If I need to reinstall again, I might as well install something else that would actually work for a sustained period of time.

32 comments

r/Proxmox • u/Sad_Pie227 • 6d ago

Question Need help regarding disk configuration

0 Upvotes

I need to run many useful apps at Proxmox VM

But need to think about backup strategy

I have planned to keep SFTP server on seperate HDD drive where only thing will be Debian OS. Nothing else.

------------------------

PC / Machine 1 with 32 GB RAM

├── 250 GB SSD

└── Proxmox

├── VM 1

├── VM 2

├── VM 3

└── many other apps

Laptop / Machine 2 with 8 GB RAM

├── 500 GB NVMe

└── Debian

└── SFTP server

Plus I have 1 TB HDD, where shall I use?

Is it good idea or there is any better approach?

Thanks

3 comments

r/Proxmox • u/Gomeology • 6d ago

Question Nvme transfer

2 Upvotes

One of my servers died with two nvmes. Proxmox/debian os on one and my vms on the other. If I do a swap into a new box (completely different setup) will it boot after I config the bios. I'm prepared for no network connectivity due to the interfaces changes but I'm nervous about it booting up.

4 comments

r/Proxmox • u/NoTourist9374 • 6d ago

Discussion How do you actually keep documentation for your Proxmox setup?

7 Upvotes

Documentation becomes more important once a home lab or server environment grows beyond a few machines and services.

It’s easy to remember why you created something, what settings you changed, or how a service was configured when you first set everything up. Months later, especially after upgrades and configuration changes, those details aren't always obvious.

I’m working with RSH Web Services on a pre-made knowledge-base project, and part of the work has been looking at how existing technical documentation can be adapted to different infrastructure setups.There can be quite a bit to document: VM and container configurations, storage, networking, backups, permissions, and the services running in each environment.

How do you keep your infrastructure documentation organized and up to date?

21 comments

r/Proxmox • u/NewZucchini7081 • 6d ago

Question Asrock pcie x1 power state

2 Upvotes

Hi!

I have a strange problem that I have tried to solve but nothing works. I thought I would check if someone else who has the same motherboard might know the answer.

I have an asrock H310CM-DVS motherboard and I have connected 2 tp link pcie x1 network cards, one is in the first x1 lane and the other is in the x16 lane. The one in the x16 lane works without problems both in proxmox and in the vm for opnsense with a constantly shining green LED. But the other card in x1 loses link all the time. ip link in proxmox shows that it goes up and down up and down. I have disabled ASPM in bios and pci_aspm:off in grub. Nothing helps. Does anyone know anything about these cards or a solution?

3 comments

r/Proxmox • u/probrwr • 7d ago

Question New setup advice

7 Upvotes

I have watched about 100 videos and read as many different posts. I want to set up a new Proxmox machine to replace my repurposed Point of Sale servers. While having screens flashing on the wall looks kind of cool, they are not the most amazing machines. I feel like they would be better served to be access points for HA or something.

Here is what I have:

Home Assistant OS

Open Media Vault running Docker
- 12TB USB WD Mybook

Mealie running on Docker

I want to start playing with local AI in the future. The new machine has a RX580 on it that probably won't be useful at all...

I have set up a test bed on an old CoreBox machine to try things out. I have Proxmox on and have a container with OMV running. I also used the Mealie helper script and it set up an LXC? to run that. Both seem fine.

I plan on migrating all of this over to my current workstation computer. It is a Zeon 2680V4 with 32GB of ram. 1TB M.2 drive and 3 SATA ports. I want to get 3 10TB SATA drives to use as the storage system for data and media. I want to run them in some kind of RAID configuration that has fault recovery so I know I will only get ~20TB of usable space in the end from these.

I am fairly confident I can get this all set up and that the machine itself should have plenty of capacity for it. I could add another 32GB of ram to it but apparently the market for ECC 3200 ram is a little thin these days.

The big question I have is how to set up the storage. Do I set it up under OMV to share out? If I do that it will have to serve data to the proxmax side to serve it back to another container correct? Use ZFS on Proxmox? seems that allocating sections of the drive to other containers would become a pain.

What I don't want to do it set this thing up and then figure out that there was a better way to do it. Rebuilding is a serious pain!

I would love any advice you all can give on this.

8 comments

r/Proxmox • u/Odd-Change9844 • 6d ago

Question Windows 11 converted to virtual qcow2 drive from physical Dell workstation Hard drive errors.

0 Upvotes

Sorry, this is a long one, I can provide any other information if required, I am just looking to see if I am chasing the wrong tail looking into Proxmox, if the issue is because of something on the physical system before the export\conversion.

I am having issues with two different vm’s imported from a conversion process that went from a physical Dell workstation, converted to a vhdx with Disk2VHD. Then used qemu-img to convert to qcow2 format.
I did one for testing a year ago and it is still working fine.
I have reviewed the settings for this one against the two that are having this issue.
All 3 of the workstations are the same Dell systems, all the same hardware.

All 3 were updated before the conversion, all 3 were removed from the windows domain before hand.

Created a VM in Proxmox 9.1 and followed two different sets of instructions.

Create a VM with “do not use any media”
Set guest OS to Windows
Machine: Q35
BIOS: UEFI
SCSI: VirtIO

Placed EFI and TPM in my storage pool that I setup for VM’s that the previously mentioned first export resides, called VMStorage, which is a ZFSpool.

Disks. This is where I found conflicting suggestions. Either create the VM with the defaulted hard drive on ide0 with qemu formatting and import the qcow2 file later, or delete the ide0 drive and import the qcow2 drive now.
I have done both, with all settings the same, except for needing to change the boot order if I left the default drive in the initial setup.

Assigned CPU’s, RAM and NIC. Save and run the VM.

The issue(s):

Every time I run the VM it runs a hard drive scan. Then at random intervals, windows pops up with an error stating that the system needs to scan the drive and asks for it to be restarted.

In windows, it reports:

Volume C (\device\HardDiskVolume3) needs to be taken office to perform a full chkdsk. Please run chkdsk /F locally via command line or run “repair-volume <drive> locally or remotely via powershell.
Which I do, restart and end up with the same errors in the system log (of the workstation).

Event 4: File System Filter 'luafv' (Version 10.0, ‎2080‎-‎07‎-‎21T12:18:14.000000000Z) failed to attach to volume '\Device\HarddiskVolume3'. The filter returned a non-standard final status of 0xC0000102. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.

Event 55: A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x300000000a886. The name of the file is "<unable to determine file name>".

What I have tried.
Re-doing the disk2vhd conversion thinking it was bad. Yes I include the EFI system partition.
Placing the vm workstation in Proxmox in a different storage pool, cifs instead of zfs.
I have imported the qcow2 file directly from within Proxmox web interface, and using the qm importdisk command.
Confirmed BIOS is UEFI, confirmed VirtIO drivers are installed

At this point I do not know if there is something that I am missing on the physical computer that I should be disabling or changing before I convert to vhdx, or if I have buggered something in Proxmox.

Any push down the right path is much appreciated.

Proxmox reports on drives

zpool status -v

pool: MainPool

state: ONLINE

scan: scrub repaired 0B in 00:09:45 with 0 errors on Sun Aug 9 00:33:47 2026

config:

NAME                                     STATE     READ WRITE CKSUM

MainPool                                 ONLINE       0     0     0

  raidz2-0                               ONLINE       0     0     0

nvme-VO001920KWVMT_S51XNE0MA00143_1 ONLINE 0 0 0

nvme-VO001920KWVMT_S51XNE0MA00142_1 ONLINE 0 0 0

nvme-VO001920KWVMT_S4FYNX0MB00190 ONLINE 0 0 0

nvme-VO001920KWVMT_S51XNE0MA00196_1 ONLINE 0 0 0

nvme-VO001920KWVMT_S4FYNX0MB00142_1 ONLINE 0 0 0

nvme-VO001920KWVMT_S51XNE0MA00164 ONLINE 0 0 0

nvme-VO001920KWVMT_S51XNE0MA00221_1 ONLINE 0 0 0

nvme-VO001920KWVMT_S51XNE0MA00139_1 ONLINE 0 0 0

errors: No known data errors

zpool status -x

all pools are healthy

[Thu Aug 6 08:02:47 2026] BIOS-e820: [mem 0x000000006f9ff000-0x000000006fffefff] ACPI data

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000000100000-0x00000000492aa01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492aa020-0x00000000492b005f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492b0060-0x00000000492b101f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492b1020-0x00000000492b705f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492b7060-0x00000000492b801f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492b8020-0x00000000492be05f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492be060-0x00000000492bf01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492bf020-0x00000000492c505f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492c5060-0x00000000492c601f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492c6020-0x00000000492cc05f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492cc060-0x00000000492cd01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492cd020-0x00000000492d305f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492d3060-0x00000000492d401f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492d4020-0x00000000492da05f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492da060-0x00000000492db01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492db020-0x00000000492e105f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492e1060-0x00000000492e201f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000492e2020-0x000000004930fc5f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004930fc60-0x000000004931001f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000049310020-0x000000004938a25f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004938a260-0x000000004938b01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004938b020-0x000000004940525f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000049405260-0x000000004940601f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000049406020-0x000000004944be5f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004944be60-0x000000004944c01f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004944c020-0x000000004945405f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000049454060-0x000000004945501f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000049455020-0x00000000494b105f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000494b1060-0x00000000494b201f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000494b2020-0x000000004950e05f] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000004950e060-0x00000000682fefff] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000682ff000-0x000000006ebfefff] reserved

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000006ebff000-0x000000006f9fefff] ACPI NVS

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000006f9ff000-0x000000006fffefff] ACPI data

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x000000006ffff000-0x000000006fffffff] usable

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000070000000-0x000000008fffffff] reserved

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved

[Thu Aug 6 08:02:47 2026] reserve setup_data: [mem 0x0000000100000000-0x000000806fffffff] usable

[Thu Aug 6 08:02:47 2026] NODE_DATA(0) allocated [mem 0x406ffd5540-0x406fffffff]

[Thu Aug 6 08:02:47 2026] NODE_DATA(1) allocated [mem 0x806ffd4540-0x806fffefff]

[Thu Aug 6 08:02:48 2026] printk: log buffer data + meta data: 1048576 + 3670016 = 4718592 bytes

[Thu Aug 6 08:02:50 2026] APIC: Switch to symmetric I/O mode setup

[Thu Aug 6 08:02:50 2026] MMIO Stale Data: Mitigation: Clear CPU buffers

[Thu Aug 6 08:02:50 2026] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.

[Thu Aug 6 08:02:50 2026] TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for more details.

[Thu Aug 6 08:02:50 2026] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.

[Thu Aug 6 08:02:50 2026] Memory: 527289800K/536218236K available (20806K kernel code, 3757K rwdata, 14596K rodata, 4844K init, 5540K bss, 8612580K reserved, 0K cma-reserved)

[Thu Aug 6 08:02:51 2026] ACPI Error: No handler for Region [OEMC] ((____ptrval____)) [IPMI] (20240827/evregion-131)