Search results

Wow look at the TAP interface go ! Is that disk ZFS by any chance ? If so, are you able to test without compression, and also triple checking ur ashift=12 setting m

Sorry reread the part where you mount the VM volume and it "inconsistent" Have you looked at htop, atop, iowait or iostat while doing the transfer ? Is it pinning the CPU core (htop) or waiting for disk (atop)

Are you running LUKs on the machine with the J1900 CPU ? As i'm not sure that CPU has the AES-NI that speeds up encryption and decryption LUKS can use.....

I just had this ! Have a node with a subscription, but two others with non, and the packages were all marked as unstable. Many thanks for this info.

This will be the death of you. I for a very short time hosted backups for my mum, from her laptop, but quickly found another solution as i was beng hammered for support.

So with the new option to Hibernate from the shutdown options with virtauls, i can't see any option to use it rather than a full shutdown when the proxmox node is rebooted/shutdown. Is this a planned feature that will be added from the Options/Start/Shutdown order menu ?

U need to make sure the drivers for it are installed on the guest. Before you switch over to a spice display. I think once U've installed the OS, u change to the spice display boot into safe mode and install the driver. There should be a guide on the wiki

I would try using spice, which even has usbpass though for a few device (I'm pretty sure)

What are you using for controlling the console ? I've found spice was very quick, which is one of the options in proxmox

A) what did you change, so others can get help from your issue. B) the console as in through proxmox ? That's expected as the video card is the primary video output, u have to either plug a monitor into he card, or RDP to it. I used to also pass thought a normal video feed and set it all up...

You need to pass through everything on the GPU, i.e. the audio part as well. so f1:00.0 and f1:00.1 as they are on the same pci group. Make sure u've read a few guides on how to do it under normal linux (Ubuntu or Debian) and make sure they are from this side of 2018/19 as some of the guides...

Sorry one last question, could i not mount the read only snapshot created by zfs snapshot and either point borg at that or pipe it in to borg ?

Sorry misunderstood. Hmmmm Going to have to think of another plan for fat virtuals then....

Already trying that.... zfs send $zfsvmdisk@borg | borg create -v --stats \ $borg_repository::$vm-'{now:%d-%m-%Y-%H:%M}' \ -

Any pointers on how to do this with Virtual Machines ? Every time i do a backup from a ZFS snapshot (i just called) of the machines the repository grows by the size of disk. i.e. 20 GB drive, first backup takes 20GB, then the second backup (called minutes after the first one completes) takes...

So i'm using Borg to create a backup, but i might be going about it the wrong way by calling zfs snapshot in my script, and then using that to create the Borg backup. I've just noticed that call virtual machine hard drives start with VM-, so i'll filter out the drives like that i think, as for...

Yea, so that's what I'm doing, but wasn't sure if there a filter/option to only show disks, as I have to know how the disk is attached, i.e. SCSI sata (tho I'm sure I could change what my grep filter is.... Hmmmm) With regards to the inbuilt backup, it does fulls each time and has no...

So just trying to get a list of attached disks on a virtual machine. So for containers i used a basic grep the container for the item "rootfs:" then used that with pvesm path (now thinking about it containers can have more than one attached storage) But for qemu virtuals, they could have IDE...

That's what I thought, If you get a chance can you let me know the file that I would need to change/patch.

I'm having disk issues where the backup hangs due to other issues, that are in the a queue my end to be solved. Is it possible to add 'timeout 240' to the backup commnd, so that no backup takes longer than 240 minutes, and if it does kill it (sig term seems to get the next one to run) but I...