Recent content by nz_monkey

Is there any way to run Ubuntu 24.04 via LXC with working networking and without the "nested" option on Proxmox ?

Glad my mailing list post helped you. Andrew.

Container config is as follows: arch: amd64 cores: 4 hostname: emby1 memory: 4096 mp0: /store0/Media,mp=/media/store0/Media net0: name=eth0,bridge=vmbr0,gw=10.69.1.254,hwaddr=A6:3D:6B:A5:7C:54,ip=10.69.1.24/24,type=veth onboot: 1 ostype: ubuntu rootfs: lvm-nvme0:vm-125-disk-0,size=32G swap: 512...

This problem looks to be related to: LXC no permission to use VAAPI

I am having this exact problem after upgrading the host to Proxmox VE 7. My LXC is running Ubuntu 20.04 with Emby. The container has the following devices: crwxrwxrwx 1 root video 226, 0 Jul 13 21:35 card0 crwxrwxrwx 1 root render 226, 128 Jul 13 21:35 renderD128 but Emby is unable to...

Hello, I have a zpool called "store0" that is mounted to /media/store0 due to consistency reasons. When I create a "mountpoint" for a container on this zpool, the container will not start and gives the error: lxc-start 125 20200107015607.240 DEBUG conf - conf.c:run_buffer:340 - Script...

I would just like to +1 this feature request. We are using the workaround to pass a SR-IOV VF to a LXC container so we can run Suricata at wirespeed. For the most part it works, but if you change the "lxc.network.name" in the vmid.conf it will not be picked up until the host is rebooted. It...

Hi There, I have noticed that whether a VM is started with fixed memory, or dynamic memory it starts with the same CLI string. e.g. VM with 16GB fixed memory: root 6237 1 4 14:21 ? 00:20:26 /usr/bin/kvm -id 247 -chardev...

Hi Guys, We have a number of virtual appliances that need a serial port to boot, to get around this we have been using "serial0: socket" in the vm_id.conf which works well. However, when we try to do a migration on one of these VM's we get the error "can't migrate VM which uses local...

Some additional information. This problem only occurs on the 3.10-5 and 3.10-7 PVE kernel images. We compiled our own 3.10-5 image, installed it and rebooted and we no longer get swap_dup errors.

Hello, We have a cluster running PVE3.3 with kernel 3.10.0-7-pve on Intel Xeon E5v2 processors. Each host has between 256GB and 512GB of ECC RAM. We have been seeing a large number of "swap_dup: Bad swap file entry" errors in the syslog of our Proxmox hosts, and occasional complete lock up...

We have a PVE3.3 cluster that has ben running well. Recently we added a second PVE3.0 cluster to run some VM's that will not run on newer KVM. Both clusters share the same management network, but have different IP addresses. Ever since adding the second cluster we have experienced pveproxy...