Recent content by mimino

No, it's obviously not the index problem. The issue is described in the first post. Still no solution to it, even after latest upgrade with 5.3 kernel.

Gotcha, this makes sense.

I second that. New kernel doesn't solve the issue.

I don't think it's kernel specific. It's exactly this: https://forum.proxmox.com/threads/problem-of-pci-device-passthrough.60654/ This morning I updated qemu-server to version 6.0-17 and the pass through is working again. Also pfSense seems to be booting fine with the 5.3.10-1-pve kernel so I'm...

Well, my experiment with the new kernel turned out to be a complete disaster. I no longer know what's going on with proxmox, even reverting back to the old kernel doesn't work anymore. The biggest issue is that I lost the ability to pass-through my network card. With hostpci0: 01:00,pcie=1 I...

If it was only the boot "flag" then why would this disk be completely invisible in the UEFI? I've tried multiple OVMF images from different vendors with the same result, so it's not that. My guess is that it has something to do with kernel/KVM. Apparently pve-kernel-5.3 has some of the boot...

Here we go: #root@dfi: cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 48 model name : AMD RX-427BB with AMD Radeon(tm) R7 Graphics stepping : 1 microcode : 0x6003106 cpu MHz : 1972.583 cache size : 2048 KB physical id : 0...

Well, in my case no VM will boot with anything other than 'host'. kvm: warning: host doesn't support requested feature: CPUID.80000001H:EDX.nx [bit 20] kvm: Host doesn't support requested features Know any cure for that?

Thanks, might try later, but as I said the chances of booting with anything other than 'host' are close to zero. Latest kernel broke some things, we just need to get somebody knowledgeable to figure out what that is. Hoping that someone from proxmox staff might be willing to help us.

Mind sharing this reddit thread? In my case proxmox won't start any VM with CPU type set to anything other than "host", without turning off KVM hardware virtualization. So I doubt this solution would work for me :(

I've been unsuccessful in my attempts to boot HassOS VM created from the VDI image (https://github.com/home-assistant/hassos/releases/download/3.5/hassos_ova-3.5.vdi.gz). I've tried VMDK as well with the same result. Images are not corrupt, run fine on Virtual Box. Upon boot I get this error...

Have you ever figured it out? I ran into this problem with VM restored from the backup. Apparently I'm unable to boot ANY OVMF VM restored to lvm-thin. Curious how proxmox team would explain this.

I'm using UEFI. AMD RX-427BB board. Here's the full config: balloon: 0 bios: ovmf bootdisk: virtio0 cores: 2 sockets: 1 cpu: host efidisk0: local-lvm:vm-100-disk-1,size=128K hostpci0: 01:00,pcie=1 ide2: none,media=cdrom machine: pc-q35-3.1 memory: 4096 name: pfSense numa: 0 onboot: 1 ostype...

After upgrading to all latest my pfSense VM won't boot anymore. It starts loading the kernel but hangs right away. Booting 5.0.21-3-pve fixes the problem. Does anyone else have this issue?

I realize this is the old thread, but many are still facing this issue with XPenology. Adding e1000e as args option cannot work since this option has been completely removed from proxmox. Folks over at xpenology forum have come up with this ingenious solution...