Search results

As above online is a bit more than a move / copy command due to the VM being online and the current disk being read / write and changes having to be handled.

What browser / client?

It will work fine as a cluster, however will be unable to do things like live migration between nodes until you have run apt-get dist-upgrade on all due to PVE version miss match. I would say upgrade one reboot to make sure no issues with new kernel / grub on your hardware. Then upgrade all...

If you want to do this as a one off use : pvecm expected 1 If you want this to be automatic each time your need to adjust the quorum votes on the master to 2 so it makes quorum. However this does defeat a clusters protection.

Your need to power off the VM if it's started on new host. Copy the VM config file back to the old host and manually add the correct config file lines to add back the LVM's. The config files are held at : /etc/pve/qemu-server/< VMID>.conf Your need to use another VM's config file to view the...

Does the VM on the new host show an entry for the old LVM disk that's only on the original node? Also for the LVM storage do you have the shared box ticked?

Then it won't be quick, as you don't have a shared storage format. If your looking at a one off migration then may be worth looking at a migration within the VM/OS. If you want to have the ability to do quick migrations in future with small downtime then shared storage is worth looking at.

That's a mistake in the WIKI most probably a copy and paste mistake, can safely be ignored. Edit - as below an upgrade on its own won't touch any running VM's however without a reboot / migration out and back in you won't benefit from new kernel or QEMU versions.

As fabian I do not see this on the link you sent, and is defiantly not required.

What is your storage that the VM's are running on?

What page within the Wiki did you see that? Have done multiple upgrades with no issues.

What storage are you using?

Do you have any connections between the servers running at 1Gbps? I know there has been some improvements recently on LM to use a different network than vmbr0. However not sure if same has been done for storage migrations, so if your default is 1Gbps your be hitting the bandwidth limit here.

No specific order, just make sure you do apt-get dist-upgrade instead of just apt-get upgrade. This will have no impact to any running VM's, however your find probably will bring along a new kernel upgrade so a boot into this when you can do would be a good idea.

How does task manager CPU graphs look during benchmark? What is Windows 10 power profile set to, do remember only server editions of Windows are designed for use within a VM so may never get the same performance. But there will be I'm sure some Optimisations to get an increase. However right...

Either upgrade and then add node or install node with the exact same version. However as there is no reason to not be running the latest PVE version I would say to upgrade first.

Do you have the CPU model set as host pass through?

Have you checked to make sure all your cores show in Windows OS?

As long as you don't use krbd and just use the inbuilt KVM RBD driver. And watch out during OSD rebuilds for RAM OOM.

For HA your really need a shared storage to make it any sense to do. And as you don't have any private network between the two servers it makes any form of shared storage pretty unrealistic. Have you checked with your DC about a seperate private network?