Question about wiki to upgrade to 4.0

vigilian

Renowned Member
Oct 9, 2015
82
1
73
Hi
I would like to know about the line which says that no vm or CT running from 3.4...is it that we have to have a blank install of proxmox? So there is no way to make a vm from 3.4 working under 4.0?


Sent from Tapatalk
 
Hi,
running in the sense that there cannot be an started VM or CT on your node, you can have naturally stopped VMs located on the node. :)

VMs from 3.4 should work just fine under 4.0, but an something like an "live migration upgrade" isn't supported.
 
Ow thanks I was really worried about how to do an upgrade about it ^^


Sent from Tapatalk
 
but as you said in the wiki: cluster 3.x can not be mixed with 4.0. So what's the system here? I recreate a node with the same name and I have to recreate all the vm and just use the backup as the startup disk ?


Sent from Tapatalk
 
I mean that how will be upgrading the VM since the node will be destroyed? and the backup will be on the node, or the node partition won't be deleted just upgraded? And since the node is deleted I guess that the information of the VM will be deleted too no?


Sent from Tapatalk
 
If you follow the steps from http://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0 you actually don't have to restore any backups, but you should have backups in case something goes wrong (then a clean new install is the only way).
The node will not be destroyed, all will be just upgraded and so the data stays. :)
After the upgrade VM should runs as expected but for Containers you have to rebuild their network configs as this can not me migrated in a generic way.

I'd suppose you follow the process and upgrade the node, in 3.x nodes cannot see 4.0 nodes (corosync 1.x vs 2.x), so your nodename may stay the same.
On the first node you upgraded recreate the cluster and add the others to it with 'force' after you have upgraded them like described.
This won't touch your VM/CT config files or drives, it only creates the corosync config (which replaces cluster.conf from PVE3.x).

When you upgrade be careful and look that you do not miss a step.
 
I'm trying at a moment on a test system to be sure to understand the part of the recreation of the node. for the moment i'm just upgrading the system on the test system and see how it goes. thanks for the information I will give a followup


Sent from Tapatalk
 
On my test system I can't install proxmox-ve and pve-manager: error processing package proxmox-ve
Failed to get D-bus connection : unknown error -1


Sent from Tapatalk
 
So I assume that you are at the "Install Proxmox VE 4.0" step from the wiki and followed every step before with no error output whatsoever?

Did you reboot the system after you installed the new kernel?
 
yes i'm at this step. I did not receive any error during the process before. I did not reboot yet. Should I ? I was guessing that I had to wait the end of the whole process


Sent from Tapatalk