Search results

I suspect you won't need the modifications you made with that enabled. I run a few fuse mounts in my containers, enabling that was all I needed to do.

Have you enabled fuse in the Container Proxmox options (under Features).

Ah, I see thanks. I misidentified my CPU, actual 6 Core with SMP in a 2x3 config. Lots of fun tweaking time ahead :)

Thanks Stefan, that is good to know, and a cleaner looking interface. Would the following be appropriate? (12 Core Ryzen) systemctl set-property --runtime -- user.slice AllowedCPUs=4-11 systemctl set-property --runtime -- machine.slice AllowedCPUs=0-3 systemctl set-property --runtime --...

Have you stopped/started the vm after adding the USB entry?

IDE/SATA will give terrible performance. Qemu Agent has nothing to do with the disk, you need the vertio drivers installed. The root of the stable virtio ISO has an installer that installs everything - "virt-win-guest-tools.exe" However, if you installed Windows on the VM ide/SATA to start...

Sounds like older kernel versions, which is pretty normal for a Linux system that has been updated with a new kernal via updates. Could you post a picture of the screen?

What version of windows? I have successful passthrough with my W10 VM, but I got a code 43 with W11 We are using the exact same driver version, though my card is a GTX 1070. Have you disabled the Windows Basic Adapter?

Thanks, but my German is non-existent :(

Trying to shield my pinned cpus (0-7) with the following command: cset shield --cpu=0-7 But I just get this error: mount: /cpusets: none already mounted on /sys/fs/bpf. cset: **> mount of cpuset filesystem failed, do you have permission? The CPU pinning cmd does work fine (taskset --cpu-list...

Same here, container on ZFS, PVE 7.0-11, can see the IO on the host.

Still happening on PVE 7.0-11

Interesting and way beyond my pay grade :) Thanks, I'll keep an eye on my test server. For now, we have ballooning disabled on production.

Thanks - do you know whether its fully fixed in the latest? (5.11.22-7)

How does that work for restoring? can it restore the whole boot image? I have a PVE host with the usual boot/kernal customisations for GUI passthrough, it was a PITA to setup and it would be great if I could just restore it to the bare metal machine.

Thanks, good to know. Was just looking at moving my home Windows 10 Dev PC to ProxMox Host with Win10 as a VM, and it would be easier to run the gui access from the host. Alternatively, I could just run a cheap nuc as a client.

Can confirm, reporting correct values now on my homeserver containers.

The way we have been doing it is to run the PBS server as a container with sufficient root storage to store the backups. Then vzdump the entire PBS container to an external usb drive.

Exccelent, thats perfect. Thanks.

Noticed that boot SSD on one of the older nodes in the cluster is at 60% wear! Decided to do some proactive maintenance, replace it with a pair of SSD's and reinstall with mirrored boot zfs. Can I safely reuse the node name and IP? (vnb/192.168.5.240). From memory that used to be an issue with...