Recent content by aghadjip

i too have very poor perf on cpu=host. have a threadripper and need to use cpu=epyc or similar, but then i lose virtualization.

@jic5760 did you ever solve this? THreadripper with GPU passthrough experiencing terrible perf when cpu=host but blazing with cpu=epyc or emulated.

OK, reimaged and started over. Something about my setup didnt like the proxmox 8 tutorial. https://forum.proxmox.com/threads/pci-gpu-passthrough-on-proxmox-ve-8-installation-and-configuration.130218/ I dont know what yet, but here is what worked for me and the WRX80E-SAGE SE to passthrough the...

The asus PCIE storage card was causing the issue. Removed it and no more reboots, im going to wipe the server in case its the pass through edits i did is causing the issue. 2023-11-20T17:56:02.111071-05:00 compressor kernel: [ 396.945570] {7}[Hardware Error]: Hardware error from APEI...

Well, passthrough works for HBA and the Asus quad PCIE x16 card, but ive got a weird rebooting issue where the host reboots after about 20 min, Trying to dig deeper, turned off all power managemnt

Im going down this path shortly, same board and processor but with Nvidia 2 x RTX A5000 for LXC native docker GPU work (not passed through) 1x 3060ti passed through to windows gaming VM 1x 1660ti passed through to plex 1 LSI Hba passed through to trunas connected to a Jbod using the m.2 pcie...

You are correct, it was the cache, Cleared it and netdata is reporting the memory correctly. Ran a memory muncher and both the UI and netdata report the same actual memory. It is weird that netdata doesnt report this usage for the bare metal, ill open a bug with netdata to understand this more

hmm, it does look that way ~ λ free -h total used free shared buff/cache available Mem: 4.0G 534M 5.6M 95M 3.5G 3.5G Swap: 4.0G 127M 3.9G Im surprised that netdata reports this incorrectly...

Hey Folks, Trying to understand why netdata is showing differing data than the container summary page. I keep getting alerts on high cgroup mem usage, but every time i look at the summary page i see its very low. However, netdata says im using closer to 3.5 gigs and triggering alerts...

while not exactly the same, we have observium in an lxc container. No special configs. Give it a try and post up any issues!

OK finally got everything working, i think. I have no idea why, but the Aarch hates the efi disk that is created by the gui. I had to skip the GUI efi disk add, edit the config /etc/pve/nodes/<host_name>/qemu-server/<vm_id>.conf arch: aarch64 remove vmgenid: change any ide<#> to scsi<#> then...

Confirmed, removal of the EFI disk does not impact booting from local disk in the VM.

Removing the EFI disk seems to allow it to boot, Maybe the EFI disk is too small? Will continue to troubleshoot

looking through the code for QemuServer.pm sub get_ovmf_files($$$) { my ($arch, $efidisk, $smm) = @_; my $types = $OVMF->{$arch} or die "no OVMF images known for architecture '$arch'\n"; my $type = 'default'; if (defined($efidisk->{efitype}) && $efidisk->{efitype} eq...

I as well :-) will post up if a solution is found