Search results

The same as me, before migrating to 8.0 I was under 7.4 and Kernel 5.19. The issue is clearly how QEMU handle iov memory allocation before writing to virtual disks within the new version. https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2025591 That why in your case, try to change the...

Sorry missed the storage controller in the config file. Which shall be changed to SCSI Single. https://pve.proxmox.com/wiki/QEMU/KVM_Virtual_Machines The setup here looks similar to that old doc: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices Unfortunately, here the storage...

Also the disk setup. It should have cache=none and iothread=1

hi, have a look on SYSLOG, since I upgraded into 8.0 I had some troubles in between ZFS, QEMU and the kernel 6.2. https://github.com/openzfs/zfs/issues/15043

From my point of view LXC is not production ready as host for Kubernetes. After many years of attempts, finding real business cases then each time allot of issues shows up: - Security - Shared Kernel with the Hypervisor - Automation - Maintenance - Upgrade - Backups / Snapshots Finally...

From my experiences the major drawback using LXC containers for Kubernetes is the fact you will not be able to implement certain persistent storage provider such as : - OpenEBS - Kasten - Longhorn - Rook Mostly because it requires to access low level kernel apis and I already spent too much time...

Hi, I’m running a k3s cluster of 3 nodes and 1 master within privileged LXC containers. All of them are hosted into a Proxmox 7.1 cluster of 3 machines with a complex SDN topology. So it’s feasible, but really painful when you starts from scratch. You have allot of tips and tricks to put in...