Search results

I did an strace on /usr/bin/qemu-ga - I hope that is what you mean - and the last thing it did was go through Cpanel's /home/virtfs directory used for their jailshell implementation. clone(child_stack=NULL, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fcc9b17fa50) =...

What is the qemu agent? The qm command? Please be specific.

Sorry, maybe I'm thick, but how would I do that? Please be specific. I think you want me to run the command on the host while running an strace in the guest, is that right? Which process do I strace in the guest?

No, it was of course done on the host: # strace -o qm-fsfreeze-freeze.strace qm guest cmd 105 fsfreeze-freeze

I have a few Centos 6 VM's that need to be upgraded so I thought I'd just go straight to Centos 8 with those. Installation was a lot of headache as support for network-scripts are being removed in Centos 8, and I had to learn how to set everything up with NetworkManager specific to my...

I know it's been a while, but I'm messing with similar issues and just came across the thread. So if I understand this right, you're piping a vzdump into the script? What I don't get is why you have to lzop -d the dump - why not just not compress it in the first place if you know it's going to...

Ok, here is the strace log. First 95% seems to be a bunch of missing Perl scripts, but since it works on other VM's I suppose that's not important. Then there's a line 7791 "resource temporarily unavailable": futex(0x7f9f16ab6010, FUTEX_WAIT_BITSET|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1591953038...

I don't understand which process you want me to strace? The qm process?

What debug information? I already added the suggested "verbose = 1" to /etc/sysconfig/qemu-ga on Nov 8, and as I explained that the immediate impression was that it fixed the problem, but the week after it did the same thing again. The only "debugging" info I find is that now it shows in the...

Is there somewhere I can open a bug report on this? It is a little frustrating that after so many months of this being a confirmed bug, there still seem to be no action taken to fix it. I just tried again, same as always: # qm guest cmd 105 fsfreeze-status thawed # qm guest cmd 105...

In another problem with Proxmox I realized that it is not possible to take a snapshot of a CT with bindmounts. I'm wondering if this is the same problem causing my VM snapshots. This is in fact a VM with bindmounts. Still don't see what that has to do with freezing and thawing the container...

Yep, I do this just before snapshots: for VM in $(qm list | sed '1d' | awk '{print $1}') do /usr/sbin/qm guest exec $VM /usr/sbin/fstrim -- "-a" /usr/bin/vzdump $VM --mode snapshot --mailnotification always --mailto your@email done

After the command you need "--" to tell the qm command to ignore further options: # qm guest exec 104 /usr/sbin/fstrim -- "-av" { "exitcode" : 0, "exited" : 1, "out-data" : "/boot: 771.8 MiB (809226240 bytes) trimmed\n/: 26.4 GiB (28355977216 bytes) trimmed\n" }

Is there a way to see what has been set already? I'm thinking of something like # pct set 100 -list for example.

How about now?

Thanks, but I meant built-into Proxmox, kinda like in FreeNAS. I guess not?

How can i configure Proxmox to share an iSCSI (or other block level share) to be mounted on a PC)? I can only find descriptions for mounting iSCSI shares exported from other servers onto Proxmox.

Still no takers? I accidentally tried to make a snapshot of this vm again today and the same thing happened. Not pleased !

I mean another Proxmox node with snapshots that needs to be moved to a central storage repo. Pre-Borg I would do this by scp, but some snapshots are hundreds of gigabytes, so I was wondering if it would make sense letting Borg take care of this with it's build-in checkpointing.

This is a really cool project! Coincidentally I've been using Borg for a little while to backup my user data (NAS data) and was thinking about a way to also use it for storing snapshots, so your timing has been perfect! A quick question though - "Proxmox server must be configured to use ZFS."...