Search results

I also experienced the issue with my OPNsense VM (FreeBSD) and because of that reinstalled it in a SeaBIOS VM. The thing is that the issue doesn't appear directly after VM creation and guest OS installation. It starts after some time, which can be days, weeks or even months.

Thank you for confirming that the error is still present for Linux and BSD guests.

I already looked a few pages back in this thread but the mentioned fix included in Qemu 7.0, what is it for exactly? Does it fix the "Guest has not initialized the display (yet)" error that appears during the boot of OVMF VMs? I am asking because the error just appeared again on my Home...

Not a windows (guest) issue at all! This also happened to me on a OPNsense (BSD based) VM with OS type set to "other". Ever since I had these problems I stopped using UEFI VMs on Proxmox and now only use SeaBIOS. Never had any issues again since switching back to BIOS VMs. I am not a...

I just tried various different workarounds mentioned in this thread. - I switched machine types back and forth. (i440fx - q35) - Changed the hotplug settings. - Changed the graphics device and graphics memory. - Enabled / disabled NUMA. - Removed the EFI disk (only removed it, didn't delete it)...

Thanks for confirming. This is what I was thinking too. https://jellyfin.org/docs/general/administration/hardware-acceleration.html#lxc-container-on-proxmox They don't say to also install it on the host, but to only install them on the host. Which is also kind of wrong if using LXCs, IMO.

Just a quick question (mainly) for the PVE developers. When passing through a device to an LXC is it necessary to ALSO install the drivers for that device on the PVE host? Or is it enough to install them in the LXC? (so the PVE host OS remains untouched) I passed through the iGPU of my AMD APU...

I am still experiencing issues with "default VGA" and "OVMF". The VM is running OPNsense and refuses to reboot when the reboot is issued from within the VM, stopping the VM is still working. Rebooting using proxmox is working fine.

I created a solution. https://forum.proxmox.com/threads/tutorial-unprivileged-lxcs-mount-cifs-shares.101795/

Since unprivileged LXCs are not allowed to mount CIFS shares and priviliged LXCs are considered unsafe (for a reason) I was scraping my head around how to still have my NAS shares available in my LXCs, f.e. (Jellyfin, Plex, ...). The solution provided by the Proxmox Wiki would require many...

This is why I was refusing to use unpriv. LXCs. I even tried the bind mounts before and it worked. And since the changes are only necessary on the host and not in the LXC I think it would be nice to have this as a feature available in the web GUI. This would make it a lot easier... I will open...

Mhh I guess you are right. This exposes my server to unnecessary risk. https://pve.proxmox.com/wiki/Unprivileged_LXC_containers I guess bind mounts are the way to go then and mounting the NAS share directly on proxmox.

The LXC is configured like this: priviliged=1,nesting=1,cifs=1 The CIFS share is working great within the LXC and doesn't create any problems whatsoever, apart from the reboot/shutdown issue. Are priviliged LXCs really THAT unsafe? The reason I went with an priviliged LXC instead of an unpriv...

Nobody here with an idea?

I am facing a strange problem with my Arch Linux LXC running Jellyfin. I mounted my media shares in the LXC which is working fine. However, during every reboot, poweroff or stop of the LXC I need to kill the pve-process of the whole container because it simply won't shutdown. At first I...

interface address "10.10.31.10/24" removed from vmbr2 10.10.31.208 via 10.10.73.1 dev vmbr2.20 src 10.10.73.10 uid 0 cache interface address "10.10.31.10/24" on vmbr2 10.10.31.208 via 10.10.31.1 dev vmbr2.20 src 10.10.31.10 uid 0 cache Oh man! o_O It seems that I oversaw something when...

If I remove the interface address "10.10.31.10/24" from vmbr2 the issue is still present, even though PVE shouldn't be able anymore to directly speak to my "10.10.31.x" clients. Why is it working for all the other services that are in a different VLAN than my LAN clients? I mean my OPNsense is...

I would like to have my PVE available only via its VLAN_SRV_IP "10.10.73.10". Sadly when accessing it via SSH/SCP/HTTPS on that VLAN/IP the connection times out after about 30 seconds. When I access it on the untagged LAN IP "10.10.31.10" I don't get these timeouts. However, it can't be an issue...

SOLVED After hours of googling, reading several tutorials and endless man pages I finally found the missing piece! https://wiki.archlinux.org/title/Hardware\_video\_acceleration The solution therefore is quite simple. pacman -S libva-mesa-driver

I am currently trying to get VAAPI working for Jellyfin inside my Arch Linux LXC. Google pointed me to many different tutorials from which I think I picked the most up to date information from. My PVE version: 7.0-11 with the lastest upgrades What am I missing? Is it even necessary...