unix:virtualization:xen:dom0
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
unix:virtualization:xen:dom0 [2020/10/05 17:02] – rodolico | unix:virtualization:xen:dom0 [2020/10/05 17:44] (current) – rodolico | ||
---|---|---|---|
Line 15: | Line 15: | ||
# and tell grub to update itself | # and tell grub to update itself | ||
update-grub | update-grub | ||
+ | # tell Xen to use the xl tool stack. It appears with newer Debian releases, this is the default | ||
+ | # so probably not necessary | ||
+ | # NOT TESTED, you may have to hand edit. | ||
+ | echo ' | ||
+ | # at this point, we are ready to go, so reboot the system into the Xen kernel | ||
+ | reboot | ||
</ | </ | ||
Line 23: | Line 29: | ||
At times, the DOM0 will attempt to grab all RAM and make it where no virtuals can exist. There may be other reasons to limit the amount of memory available to the DOM0, though I generally like to give it a bunch so it can cache things. | At times, the DOM0 will attempt to grab all RAM and make it where no virtuals can exist. There may be other reasons to limit the amount of memory available to the DOM0, though I generally like to give it a bunch so it can cache things. | ||
- | ==== | + | ==== DOM0 and UEFI ==== |
- | + | ||
- | ===== DOM0 and UEFI ===== | + | |
I have run into some serious issues trying to get a DOM0 to boot with UEFI. A fresh Devuan (Debian) install works just fine, then when the Xen kernel is brought up, the boot fails. I don't remember the exact issue, but it has been around for several years. | I have run into some serious issues trying to get a DOM0 to boot with UEFI. A fresh Devuan (Debian) install works just fine, then when the Xen kernel is brought up, the boot fails. I don't remember the exact issue, but it has been around for several years. | ||
Line 51: | Line 55: | ||
</ | </ | ||
+ | ==== set up iSCSI targets ==== | ||
+ | |||
+ | This is a manual operation, but there is a script that will do it automagically for you, if you like. See | ||
+ | [[unix: | ||
+ | |||
+ | ==== set up NFS mounts ==== | ||
Now, create an entry in /etc/fstab to automount / | Now, create an entry in /etc/fstab to automount / | ||
<code bash> | <code bash> | ||
Line 57: | Line 67: | ||
mount / | mount / | ||
</ | </ | ||
+ | |||
+ | === Real Life === | ||
+ | |||
+ | Honestly, what we do is a little more complex on the nfs mounts. We have configurations that may be different depending on which hypervisor they are one. Sometimes, when upgrading a Hypervisor, the configuration will need to be changed. | ||
+ | |||
+ | We also like to have several utilities shared between all of our DOM0' | ||
+ | |||
+ | Finally, sometimes we want to use an FBD (File Backed Device) off an nfs mount for some DOMU' | ||
+ | |||
+ | For this, we actually create three nfs exports: | ||
+ | xen-configs - stores configs for virtuals in a tree, depending on the type needed. | ||
+ | xen-images - holds FBD's | ||
+ | xen-store - ISO's, scripts anything that we may need for managing our work | ||
+ | |||
+ | We mount those in / | ||
+ | |||
===== Links ===== | ===== Links ===== |
unix/virtualization/xen/dom0.1601935365.txt.gz · Last modified: 2020/10/05 17:02 by rodolico