Recent content by SirMaster

Not really. What I did for now was to create a script inside the VM that runs when the VM starts up and that connects to Proxmox via SSH and runs my command.

I am looking for a way to run a custom shell command as root automatically sometime after a VM is started. I need the command to be run at least after the main KVM process and all it's threads have been created. The command I want to run is this: ls /proc/$(pgrep -f nick-htpc)/task | xargs -n...

I updated my post with a slightly different request.

I'm looking for a way to set the Linux scheduling priority of my VM on Proxmox to SCHED_FIFO automatically when it's started. Currently I have to start my VM, then look up the PID of the process and all it's threads and run the command "chrt -f -p 1 PID" to set the scheduler to SCHED_FIFO. I...

FWIW, mine is working correctly. HOST: 5.0-23/af4267bf grep -c processor /proc/cpuinfo 8 CONTAINER: arch: amd64 cores: 4 hostname: nick-gdrive memory: 2048 mp0: /nickarray,mp=/nickarray net0: name=eth0,bridge=vmbr0,gw=10.0.0.254,hwaddr=7A:40:78:24:92:09,ip=10.0.0.12/24,type=veth onboot: 1...

So I see the update for this was released a few days ago and it seems to work. However maybe I am misunderstanding how the numa configuration works, but my goal was assign cores 0,2,4,6 (the 4 real non-hyperthreaded cores) from my 0-7 cores to my VM which I wanted to assign 4 internal cores to...

Good idea, thanks!

The question would be why do we still need it on PVE though cause it was only added to Debian repos in May 2016. That's why it's in PVE in the first place because it didn't used to be in Debian. Also maybe they don't want to add jessie-backports as a required source? Another difference is...

Yeah even jessie-backports got 0.6.5.8 already heh. https://packages.debian.org/jessie-backports/zfs-dkms Unfortunately we can't use the debian packages as they will conflict with the proxmox repo.

I added this line to my directory storage where the directory is on zfs: is_mountpoint 1 But whenever I edit any storage entry from the GUI, the 1 (that follows is_mountpoint) is removed from every storage entry when I click save.

FWIW I fixed this to make zfs mount on non-empty directories by modifying the file: /lib/systemd/system/zfs-mount.service I found: ExecStart=/sbin/zfs mount -a And I changed it to: ExecStart=/sbin/zfs mount -O -a I had to do this because I wanted to use a zfs dataset as a directory storage in...

Awesome. Good job spirit, thanks for finding and fixing the issue :)

Yeah, parsing the semi colons wrong seems like a real possibility. Thanks and there is not necessarily a great rush on this.