Well, pve-zsync is supposed to ignore the the `format=` option in the config. Could you post the error messages you see along with the disks found in the VM's config at the time of a failure?
They ended up with a kernel-side fix for this. There's a kernel in the `pvetest` repository ready to be tested. Package pve-kernel-4.15.18-1-pve version 4.15.18-17.
Geht natürlich auch ohne systemd, je nachdem was drin tatsächlich passiert. Die Meldung sieht schon stark nach demselben Problem aus. Zumindest gibt's nur 1 Operation die das auslösen kann. Sollte also schon auch zusammen mit diesem bug[1] gefixt werden, hoffe ich mal.
[1]...
The corosync service uses /etc/corosync/corosync.conf, you need to make sure the same changes are applied there. This file is usually updated by the cluster service when the corosync.conf in /etc/pve gets updated by one of the nodes, but if you make manual changes, you need to make sure they're...
Looks like the pve-cluster service is not running properly. Assert this by stopping it (`systemctl stop pve-cluster.service`). Then run `pmxcfs -l` to start the cluster file system in "local mode", go to /etc/pve/nodes, there should be a folder with the old node name, and most likely one with...
See here[1] (The 'split image' section) for how lxd images work. You can use the vzdump tarball as a filesystem-only tarball and have to create a metadata file in an extra tarball. From what I can tell it should be enough to provide the architecture and creation_date entries (the creation date...
Yes, this is being worked on. There will be some quirks to deal with, however. (Particularly docker and systemd-networkd manage to have conflicting requirements for when they're running in a user namespace, for example.)
There are two steps here: The first one resizes the images, this was successful. The second one was to resize the filesystem on top of that image, this failed. You'll want to shutdown the container, run fsck, mount it and then run resize2fs manually:
# pct fsck 104
# pct mount 104
# resize2fs...
Apparmor in the ubuntu bionic kernel supports a new feature (socket mediation) which the userspace tools don't make use of because upstream it was moved to a newer ABI version. (Iow. our kernel doesn't advertise the feature to the user space tools and therefore they don't know about it and...
`them in` typo corrected...
Open eg. /etc/pve/qemu-server/100.conf, look for (or add) the line starting with `cipassword: ` and put the password there in plaintext like
cipassword: 12345678
For configuraton errors / faster restore, you should use snapshots. `data` there is a thin pool supporting snapshots after all. If you still want to allocate some space for a directory storage, you can just as well create a thin volume on that data pool with the size you would otherwise want to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.