Final Proxmox VE 5.1 is planned for October 2017 (mid/end): Ceph Luminous, Kernel 4.13, latest ZFS, LXC 2.1 https://forum.proxmox.com/threads/planning-proxmox-ve-5-1-ceph-luminous-kernel-4-13-latest-zfs-lxc-2-1.36943/
I guess I should have mentioned your name Monday to get that information without figuring it out on my own. I didn't know about that, so I couldn't have meant it, but yes, it does seem to match up.
Turns out if you move a disk after converting to a template, the disk name changes from having "base" prefix to "vm" prefix, which isn't allowed to be used with linked clone. One solution is full clone then convert to template again. Seems like either blocking the disk move while template or...
I too didn't notice the hidden migrate all option under more for a node. I was expecting to see it when right clicking a node in the navigation pane or node list (similar to the options shown when right clicking a vm). Perhaps that could be added? Regardless, I agree VMs should auto live migrate...
Subscribing. Also having this issue (more than once now) on pve-manager/4.2-15/6669ad2c (running kernel: 4.4.10-1-pve)
Looks like some progress has been made (https://lkml.org/lkml/2016/7/12/919)
I agree this feature would be very useful. Even if that means adding vlan bridges (bridge with vlan tag set) to the resource pool which could be added to the vm (rather than specifying vlan tag within vm interface settings) based on user's permissions to pools.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.