Thanks for the reports! The errors described by @zhouu, @capnspacehook and @agross should be fixed with pve-container version 6.1.1 available on the pve-test repository.
Hallo,
das geht mit qm remote-migrate, siehe https://pve.proxmox.com/pve-docs/qm.1.html
Falls die Doku nicht reicht, hier wäre noch ein Beispiel: https://www.thomas-krenn.com/en/wiki/Proxmox_Remote_Migration
If you check the bugtracker, there is a patch available as of today to be code reviewed: https://bugzilla.proxmox.com/show_bug.cgi?id=7271#c6
Once reviewed and applied, it will be part of one of the next versions of the pve-container package...
Distribution Name | Proxmox 9.1.5 Debian Trixie 13
Distribution Version | Proxmox 9.1.5 Debian Trixie 13
Kernel Version | Linux 6.17.9-1-pve
Architecture | x86_64
OpenZFS Version | zfs-2.4.0-pve1 - zfs-kmod-2.4.0-pve1
My zpool has 2 device: sdb...
Could you elaborate a bit on this? Where exactly do I find the http-proxy.conf? Will skopeo work after I apply these changes to this file? Right now the only way for me to get skopeo connecting to a registry is by setting http_proxy vars in shell...
Bitte doch nochmals lesen! Es gibt einen sekundären PBS (Version 4.x), der ganz woanders steht und hier nichts mit zu tun hat und nur angeführt wurde, weil das Argument Sicherheit angeführt wurde.
Wir reden nur vom primären PBS (Version 3.x)...
Hallo,
das geht mit qm remote-migrate, siehe https://pve.proxmox.com/pve-docs/qm.1.html
Falls die Doku nicht reicht, hier wäre noch ein Beispiel: https://www.thomas-krenn.com/en/wiki/Proxmox_Remote_Migration
This seems to be a bug with Linux kernel >=6.16 - as documented here.
As indicated above it has been patched/fixed in davfs2 1.7.2-1.
It would seem that for older versions, it can be "fixed" with:
set buf_size to 64 in
/etc/davfs2/davfs2.conf
So all of these are related to the windows versions that the backend expects:
wxp is “Microsoft Windows”, Version “XP/2003”
w2k is “Microsoft Windows”, Version “2000”
w2k8 is “Microsoft Windows”, Version “Vista/2008”
win7 is “Microsoft Windows”...
Hi @medichugh,
Best way is to examine the specified files and remove one of the duplicate references, so only single reference remains.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
I've made many modifications and improvements to zpbs-backup. If you tried it already, and were disappointed or confused, I apologize. Please give v0.5.0 or later a try. Expect most changes to be breaking, aside from the dataset properties you...
The actual task you asked for is actually rather simple, the issue is that you likely have duplicate VG names now which you need to fix first.
Use vgdisplay to get the IDs and then use something like vgrename OLDID pveold. I'm not sure how to...