February 7, 201412 yr I'm not sure if I've seen it clearly laid out here on these forums, how do you auto-start Xen guests (DOMU's)? I read something about putting the config file in a folder, XENDOMAINS? Is that right? Thanks!!
February 7, 201412 yr Put your config file on the flash drive and use the go script to create a symlink to /etc/xen/auto I think. Please post your steps when you get it working to help others. Thanks! Sent from my Nexus 5 using Tapatalk
February 7, 201412 yr Number 4 below will address autostarting VMs. Tom, A few recommendations... 1. Do not assign a set amount of memory to Dom0 and make syslinux.cfg look like this: label Xen 4.3.1 / unRAID OS kernel /syslinux/mboot.c32 append /xen dom0_max_vcpus=1 dom0_vcpus_pin --- /bzimage --- /bzroot label Xen 4.3.1 / unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode Since a lot of people use a Cache Directories (a memory hog), let Dom0 get assigned all the memory. That way if memory runs low, the VM has the issues / crash (as a previous use a few posts up experienced) and not unRAID. Even with all the memory assigned to Dom0 (unRAID), the VMs can still use / grab it but unRAID has the priority and will take back what it needs. Note - By default, this how most Linux Distros handle it. 2. You will probably want to dedicate at least one CPU to Dom0 by default. label Xen 4.3.1 / unRAID OS kernel /syslinux/mboot.c32 append /xen dom0_max_vcpus=1 dom0_vcpus_pin --- /bzimage --- /bzroot label Xen 4.3.1 / unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode a) Dedicating a CPU core only for dom0 makes sure dom0 always has free CPU time to process the IO requests for the domUs. b) When dom0 has a dedicated core there are less CPU context switches to do, giving better performance. c) Assigning more than one isn't going to make Dom0, write files faster to unRAID or make the VMs run any faster. 3. Cosmetics - I would put the version number of Xen in syslinux. As you know unRAID 4.3.2 and 4.4 are both due out this month around the same time. Depending on where we are at in the beta process and if / when you are comfortable updating to either 4.3.2 or 4.4 it will make supporting the users easier if they (and those of us supporting them) see / know which version of Xen they are running (assuming you eventually update to 4.3.2 or 4.4 through the beta process). 4. Make the following changes in /etc/default/xendomains: XENDOMAINS_SAVE= XENDOMAINS_RESTORE=false XENDOMAINS_AUTO=/etc/xen/auto <--- Symbolic link or point this to a directory you create on the unRAID Flash Drive. If we Symbolic link or copy our VM cfg files into the XENDOMAINS_AUTO folder the VMs will autostart on boot (there is an automatic delay from each VM starting so they do not start all at once). According to Tom... already put in almost all of that in -beta4.
Archived
This topic is now archived and is closed to further replies.