>>Quick questions - can 3.4 nodes coexist with 4.0 nodes on a cluster?
3.4 nodes will not see 4.0 nodes.
It's possible to upgrade all nodes to jessie/proxmox 4.0, at the same time,
without reboot host. (and without stop the vms)
Then live migration is possible. (and reboot host when it's node)
Woot! and Wow!
Quick questions - can 3.4 nodes coexist with 4.0 nodes on a cluster?
I did see that you can't live migrate VM's from one to the other.
On 7 October 2015 at 00:07, Martin Maurer wrote:
> Hi all!
>
> We are proud to announce the final release of our Proxmox VE 4.0 - based
> on the
Hi all!
We are proud to announce the final release of our Proxmox VE 4.0 - based
on the great Debian Jessie.
Watch our short introduction video - What's new in Proxmox VE 4.0?
http://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-4-0
Linux Containers (LXC)
The new
Please can you use PVE::LXC::lock_container()
> + #begin critical path: from here we need to lock the container
> + PVE::LXC::lock_aquire($vmid);
> + if (PVE::LXC::check_running($vmid)) {
> + PVE::LXC::lock_release($vmid);
> + die "Cannot run command on active
---
src/PVE/API2/LXC/Config.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/API2/LXC/Config.pm b/src/PVE/API2/LXC/Config.pm
index c363850..cd1a9cd 100644
--- a/src/PVE/API2/LXC/Config.pm
+++ b/src/PVE/API2/LXC/Config.pm
@@ -252,7 +252,7 @@ __PACKAGE__->register_metho
* the filesystem specific command will be called automatically by fsck (at the
moment ext4)
* the -y flag ensures that the filesystem can be fixed automcatically in
a non-interactive session
* the -f flag forces a filesystem check even if the fs seems clean
---
src/PVE/CLI/pct.pm | 46
