nerf/defaultRoles #12
1 changed files with 15 additions and 0 deletions
15
nixos/roles/xen_guest.nix
Normal file
15
nixos/roles/xen_guest.nix
Normal file
|
@ -0,0 +1,15 @@
|
||||||
|
{...}: {
|
||||||
Gonne marked this conversation as resolved
Outdated
|
|||||||
|
imports = [ ];
|
||||||
|
boot = {
|
||||||
|
loader.grub = {
|
||||||
|
device = "nodev";
|
||||||
|
enable = true;
|
||||||
|
};
|
||||||
|
initrd = {
|
||||||
|
availableKernelModules = [ "ata_piix" "sr_mod" "xen_blkfront" ];
|
||||||
|
kernelModules = [ ];
|
||||||
|
};
|
||||||
|
extraModulePackages = [ ];
|
||||||
|
};
|
||||||
|
}
|
||||||
|
|
Loading…
Reference in a new issue
How does this file compare to the Xen-DomU config?
Ahh I was not aware of that, it is probably better to just load that file (even if we don't need some of the kernel modules that early).
(It doesn't really hurt).
But it does change logging behavior in a (I think) sensible way. But I'm unsure if we are prepared for that. Do we do anything
with the Xen console logs?
We currently don't log Xen console logs as far as I know, but I'd like to be closer to this file. Maybe log both to console and to disk until we collect the console log?
Ahh that probably doesn't even change anything because we log on that machines using journald and not syslogd. (We could, and journald has an option to forward logs to syslog). But for now it doesn't change anything (it would though the moment we decide to you syslog)