Search results

I made some quick tests. VM image is a 8GB RAW on raid5, compressing to tmpfs (edit: I was wrong, my /tmp isn't tmpfs): edit: machine is a 2*quad xeon E5620 / 32GB RAM with hyperthreading enabled time lzop vm-911-disk-1.raw -o /tmp/lzo-default.lzo real 0m20.990s user 0m11.284s sys 0m5.452s...

Moin, guck mal hier (https://forum.proxmox.com/threads/update-wake-and-other-on-lan-for-vms-v0-3.26381) - ich hatte da neulich etwas ganz ähnliches im Sinn. Ohne GUI und sonstigem Schnickschnack, aber für mich hat meine Idee gereicht und bin glücklich damit. Vielleicht gibt es Dir aber ein paar...

You haven't to get curious. Just use the search function and read the docs more attentive ;) As usual somebody had the same question or idea before you: https://forum.proxmox.com/threads/put-vm-name-into-backup-name.27495

I did my last test with gentoo as a lxc container around 2015-12 which failed with the entitled message. Today I did a new test - and HOORAY it worked (nearly) out of the box! I built the template on a physical arch-Linux as described in https://github.com/globalcitizen/lxc-gentoo which took...

You can set a script in /etc/vzdump.conf for this, ie script: /usr/local/bin/vzdump-rename Have a look to https://pve.proxmox.com/pve-docs/vzdump.1.html which describes everything you'll need. edit: There's an example script at /usr/share/doc/pve-manager/examples/vzdump-hook-script.pl also.

Ah, I see. Great! It is working now. Thank you very much! Is it correct that the parameter stdexcludes is missing in the default vzdump.conf ? My setup is based on the 4.0 ISO and I haven't this parameter... BTW: Got'nt a notification about your answer yesterday. No entry in mail logs. Haven't...

It seems to me that backing up a lxc excludes some paths per default as mentioned, but not explicit called, in [1]. But in my opinion excluding /var/log/* MAY be a bad idea as this excludes everything - although some programs are expecting existing log paths after restoring, apache2 for example...

I've no tip for you. But having a similiar setup on two Hetzner EX-Servers it looks like a misconfiguration at your setup, as both of my systems are'nt having any issues. Both had a setup with Hetzners debian default system and even the first one survived the upgrade from pve 3.x to 4.x flawlessy.

I did the following on my providers root server and got a wonderful setup with one external and one internal IP/subnet (edit: server has a singleport NIC): auto lo iface lo inet loopback auto eth0 iface eth0 inet static address a.b.c.d netmask 255.255.255.255...

Update time! - dosthol.service: Fixed a typo which led service to fail (call of dosthol.sh instead of dosthold.sh, leftover from v0.1) - Client: Parameter parsing, help extended, some beautifyings and option to send MagicPacket to a specific IP or subnet

Project finished. Enclosed daemon, client and systemd service file. dosthol ist now able to wakeup, shutdown, poweroff (stop), suspend, resume and reset qemu and lxc VMs (reset n/a with lxc). Was a funny project :cool: Have fun!

(EDITED) I ever wondered why there's no solution to startup VMs by WOL 'til now, so I helped myself and wrote a bash script that I want to share. I called this baby dosthol (Do something on LAN) which will do other tasks some day, i.E. remote shutdown and others. Maybe someone will find this...

In pve 3.x I used to have pxe-* roms in /usr/share/kvm that I had created on my own including script, comboot and some other functions. That worked great until pve 4 - no matter what I do, the vm seems to use the original rom from the qemu package. Are they fixed/hardcoded now or something linke...