Search results

Thanks - but there's nothing running with more than 0 to 1% total, and I checked the details page.

Host: Proxmox 8.0.4, Ryzen 5700x, 64GB Both Guest VMs: Windows 10, all latest updates. 32 GB assigned. Both with 'host' CPU type. Both same virtual SSD settings When I run one of the VMs, and let it settle down with task manage open, I see it idling as expected. Looking at 'top' on the host I...

Came to say the same thing - it's a bit confusing when 7.x installer worked fine, and then with no hardware changed the installer appears to just hang at "loading drivers" stage.

Probably - although when on in BIOS, it enables some sub-options, including "Other PCI Device ROM Priority", which is set to UEFI only. That sounds like an attempt, at least, to ensure the UEFI firmware is still available even if in CSM mode.

Ok - I can answer my own question - somehow my BIOS flipped CSM support on (which I believe means legacy rather than UEFI boot). Now I've turned that off again, I see the Tianocore boot screen again, and the "No more image in the PCI ROM" message is gone. I don't really understand what that...

EDIT - Fixed turning of CSM support (somehow it turned on randomly in BIOS). However, still want to understand the behaviour Original Post: I've suddenly started noticing, when booting a Windows 10 VM, that I don't see the Proxmox/Tianco core boot screen. I do however still see Windows once...

podman is daemonless, and so it ought not to be a problem. In what way is this "asking for trouble"?

I usually run Ubuntu server in my LXC containers, but wanting to try Podman, which really only works well on a Redhat/Fedora base. Even though this is working, when I run podman commands in the LXC guest, I see two errors/warnings in the host logs: overlayfs: conflicting options...

@TheHellSite - just wanted to say thanks; this worked for me, with one niggle: The 'noauto' option means `mount -a` is ignored, which confused me. To get around this do `mount <mnt dir>`

I'm seeing the same "BugCheck" log upon restart, however I only noticed in passing. It doesn't actually seem to cause a problem. Did you find out what's wrong?

I found this too - and I'm really itching to understand why.

For me, UEFI/grub

Ah ok, I’m misunderstanding the commit log. However, do you know what might have fixed the issue @t.lamprecht ?

Yes I’m running a single 3080FE. I did initially have this error. But I also changed my processor from a 3900X to a 5700X - which is the only change.

Actually, I just noticed that this old ACS patch has been reintroduced. @t.lamprecht - could this have fixed the issue?

Have you tried 5.15.35-3? cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.15.35-3-pve root=/dev/mapper/pve-root ro quiet

Has something changed here? I've completely wiped my Proxmox system and started again - and amazingly it all just works. It's hard to tell what the changes are in https://git.proxmox.com/?p=pve-kernel.git;a=summary

I just upgrade my CPU from a Ryzen 5700G to a 5900X, and noticed the idle frequency rocketed from 900MHz to 2200MHz. As far as I know, on the 5700G the 900MHz was even there with default Proxmox settings, which I believe is "performance" (though I don't know where that's set). Anyway, I tried...

That's not the official code/repo - I wouldn't trust a random mirror on GitHub. Also - the 'proper' driver, as I say, has been upstreamed. Finally, I did try to build from Realtek source, and it made no difference.

Thanks for your help @LnxBil - sorry I had to focus on something else. The output of numastat: numastat node0 numa_hit 122712713 numa_miss 0 numa_foreign 0 interleave_hit 3105 local_node...