Created a Fedora 38 LXC container on Proxmox. After first boot found network not working. Search found a bug report stating systemd-networkd service not enabled. Did a systemctl start systemd-networkd.service and then a systemctl enable systemd-networkd.service.#

Alas, Fedora just locked up on me while I was using it. It's looking like I can't run a VM on this host. #

I now have Fedora 38 running in a VM that I can access via RDP. This time I am using KDE. Fedora workstation uses Gnome which is too graphically intense for remote desktop use. I am not sure whether Fedora is going to be any better at not locking up than Ubuntu, only time will tell. I did select a number of different options for the VM: 6 GB of RAM with no ballooning; OVMF (UEFI) Bios; q35 machine but kept the default display, which I am connecting to at 2560x1600. Performance is decent for running Firefox.#

Creating a Fedora 38 workstation VM, curious to see whether that distro has any problems. I've run Red Hat on this Beelink U59 Pro with no noticable problems, so I am wondering whether Fedora will be as reliable. #

Might be an issue with the CPU used by the Beelink U59 Pro. Reading a thread about this on the Proxmox forums. Might need to determine how to get Onedrive working in an LXC container. Going to turn off memory ballooning to see what that does.#

I could not connect to my remote desktop VM this morning and found that it locked up just like I had experienced earlier. When I look at the VM in Proxmox I see the CPU pegged at 25% and the memory pegged at 50% (4 GB) and the console is not responsive. Not sure here whether the problem is with Proxmox or Ubuntu or both. It would be good to know why this is happening. In the mean time, I changed the VCPU to 2 from 4. #