In XenServer 5.6 there was the autostart feature
on VMs. When the autostart checkbox on the VM was enabled, the VMs
would start automatically after the XenServer host environment was
powered up. In XenServer 6, this feature is removed from the XenCenter
console. There are multiple blogposts that describe how to re-enable the
autostart feature from the commandline. But that is not needed. You can
use the new vApp feature. With vApps you can accomplish the same, but
better. vApps is a logical grouping of multiple VMs. For example you can
create a vApp “core infrastructure”, put your domaincontroller and
licenseserver in it and some additional servers. In a vApp you can also
define the order in which VMs are started and also a delay time between
the startup sequence. So vApps is much more flexible than autostart. You
can find vApp in XenCenter under Pool –> Manage vApps.
List the vApps: xe appliance-list
Start a vApp: xe appliance-start uuid=<appliance-uuid>
Add above command to /etc/rc.local
So forget the autostart feature, use vApps. Even with the free version of XenServer you can use it.
- Create a new vApp
- Assign VMs. A VM can be added to only one vApp at a time
- Change VM startup sequence. Add delays between sequences.
List the vApps: xe appliance-list
Start a vApp: xe appliance-start uuid=<appliance-uuid>
Add above command to /etc/rc.local
So forget the autostart feature, use vApps. Even with the free version of XenServer you can use it.
Post a Comment
Post a Comment