Search results

That's right. Removing local backup does not affect any other VMs. So I can remove the part without any problem. How do I get the “Live VM” contained on it started on another host without a time-consuming restore?

Hi, There is an easily removable SATA SSD in the source host, which can be plugged into any target host using a USB housing. How do I get the target host to display the VMs it contains in the WebUI and thus make them startable? Please refer to...

datastore! no passthrough. mounted external per CLI/crontab.

Hi, I run a PBS VM on a removable disk. Now I would like to plug it into another PVE host and just start it there without having to go through backup/restore (4TB takes a little longer). Has anyone ever realized this?

Sag ich doch. Irgendein Rechteproblem. Darf ich fragen, warum du mit unprivileged lxc hantierst? Vielleicht lässt sich das anders lösen?

Klingt für mich doch nach Rechteproblem.

Das Problem kenne ich in der Light-version seit Jahren. Bei mir hat die Reaktivierung der Tablet-funktion aber immer Abhilfe geschaffen. Helfen kann ich Dir leider nicht. Aber du bist wenigstens nicht allein ;-)

Hi, I would like to automatically integrate external USB drives into PVE. So create a “USB disk storage” in the GUI that represents various different USB disks. Currently I do this time-controlled via commandline and crontab in the form (without appearing in the GUI): mount->script.sh->umount...

That was my wish. Almost too good to be true. Your point 5, for example GC on the pbs every Sunday, does the definitions of the pves follow? Unfortunately, I think I'll have to do the puzzle myself. I would like to thank you in advance for your exchange of ideas and I am always happy to hear...

So I define the retention on a pve host and push it including VMs to a pbs? Is this information retained there? prune&gc on the pbs are based on this? I would wish... But I'm a little confused.

Thank you for your clear statement. Without namespaces, my idea as described will not work.

Just like deleting files in every filesystem.

And how do I define on the pbs which VMs are affected in a prune&gc job?

It's clear that prune is more like marking the sets to be deleted. GC then sweeps through (and takes a long time) and frees up the corresponding storage space. If I have enough storage space, I run a GC weekly or monthly. So I miss the possibility on the pbs to define which VMs belong to a...

In the first case, I simply throw all the VMs of a PVE host onto the PBS. The PBS then takes care of storage etc. all by itself via namespaces? In the second case, I define this on the PVE hosts and don't need a prune&gc schedule on the PBS? Have I understood that correctly?

Wouldn't it be better to offer garbage collection as an option in a prune job instead of as a meager, standalone entry in the WebUI?

How do I do that? I have various VMs that are all backed up on a pbs. Now I would like to keep certain VMs for different lengths (prune&gc) of time, for example: - servers last 30 days and maximum 6 months - old, unused VMs maximum 2 versions - Workstations 5 days Where do I define these rules...

I've adapted your .service-file to my needs and will observe the systemd-solution. I will response message.

Did you compare system service vs. crontab bash?

Started as a manually executed shell script, it works wonderfully. In crontab via: @reboot /root/wol.sh > /dev/null unfortunately not.