Search results

Hi guys, thanks for replys and suggestions. Later I noticed, that dirty blocks are also on disk, not just in RAM and gave up, as the 1Gbps link would always be to slow. FYI some of the VMs actually migrated after a day or two of migrating. :-) But I was notified that live / online migration...

Hi guys, recently I upgraded two node cluster to four nodes from 6.0 to 6.3. I migrated VMs (some online, som offline) to the new nodes. On the new nodes we have the same series (E5 v2) CPUs, just around 1/5 faster per core and more cores. The thing I notice is, that CPU usage (with the same...

I use NVMe as any other SAS or SATA drives in my ZFS pools.

Hi guys, i have a situation where migration link is slower than VMs RAM, which is constantly being changed. So when doing an online migration from 6.0 to 6.2, it never completes, just synces RAM forever and ever. Does anyone have any ideas for online migration in this case? VM disk in on a ZVOL.

Well, i have had created a replication job, which i wanted to stop and it would take forever if I did not kill it manually. It would be nice to have a GUI option to kill a running replication process. Pve-zsync does not have GUI, so there is no need to implement GUI option to stop it. Whould you...

Oh, you are correct. I missed that. There are no missing links then. Tnx for the point out. :-)

There are many, from the simplest of just buying a power switch which you can get from your local hardware store and then using cronjob to shut down cleanly or you could use wake on lan and dronjob to shutdown,... etc

As title states, how to regenerate /dev/zvol ZFS missing links (without reboot)? Back story: I added two new nodes (6.2-15/48bd51b6) to 6.0-7/28984024 cluster. I wanted to live migrate VMs to them and then upgrade old nodes. There were quite a few issues which I worked around to make live...

Well, can't you test by failing over a test NFS share? Or use a test device? Upgrading HA storage controllers should not present a downtime to clients. Unless it is not HA. NFS states and everything should be failed over.

There might be multiple version of conifg files on the destination, one for each snapshot. You probably used the wrong one. pve-zsync work perfect every time. You should do nothing special. Just read the instructions and use it accordingly. If you have problems, come and ask. Also you can run...

I guess this was never realized? Should I open a feature request?

What you describe is a pve-zsync command line utility which I use often to move VMs across clusters. https://pve.proxmox.com/wiki/PVE-zsync

OK, let just cover the basics first. What is the Realm selected?

Hi, if you do not touch the RAID array or the LVM data that resides on it, you will be able to access it with new install. Might even work, if you just bring over storage.cfg or whichever file has storages defined. In any case you can activate (vgchange -a y) and ad it manually. I never used...

I think you should have a GUI option if you right click a LXC and there is also a command line one: root@leona:~# pct migrate 400 not enough arguments pct migrate <vmid> <target> [OPTIONS]

Didn't read your whole post, but I felt sorry, 'cause i do not think people will want to do your work for you (employed to know this things :-), so here are my quick answers. I would always set up cluster with ZFS and replication on Enterprise SSD drives with NVMe as log and / or special...

LXC does not support live migration, so PM does not either. (CRIU does not yet work.) Use KVM VMs if you need live migration.

Using pve-zsync is not a workaround. It is a standard CLI tool. BUt I get what you mean. I suggest you open a feature request and sponsor it.

There are many ways, some of which are available to you using simple google search, and some are tied to your specific install. While people might not be inclined to answer topics already answered, I would suggest you at least specify basic info about your PM install. Like, do you use ZFS (then...

pve-zsync does that for you and it synces only differences. I use it when moving my VMs from cluster to cluster. Sync, stop, sync again, start on new node. config files are in /var/lib/pve-zsznc/.. It takes just 3 minutes of downtime, no matter how big the VM is.