Search results

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...

I thought that should only affect the performance on the virtual drive though, not the passed-though drive?

qm config 104 balloon: 0 bios: ovmf boot: order=scsi0;net0 cores: 12 cpu: host efidisk0: local:104/vm-104-disk-1.raw,efitype=4m,pre-enrolled-keys=1,size=528K hostpci0: 0000:0b:00,pcie=1,x-vga=1 hostpci1: 0000:0d:00.3,rombar=0 hostpci2: 0000:01:00.0,rombar=0 machine: pc-q35-6.2 memory: 16000...

Ah, sorry, I'm confusing things - actually I tried three ways: 1) Windows host 2) Proxmox host, with tested drive a vfio scsi drive on the nvme I'm interested in (no caching) 3) Proxmox host, with nvme drive passed through. In case 1 and 2, 4k random writes with 32 queue depth are good. In the...

Yes, identical VM - the OS itself is running off a virtual disk.