The second solution is not a hack.
Whole xen development community is moving from single dom0 to
multiple service domains, each performing single set of tasks
(storage domain, supplemental domain for HVM and so on).
If you want to load dom0 with encryption too, let me ask: how you
want to manage CPU time for that? One domain may perform lot of IO
and other want more CPU. If you put encryption to dom0 you can not
give most of CPU to 'cpu-hungry' task, because you should never
limit dom0 in cpu usage. If encryption is happens within
specialized domU, you can limit it CPU usage (while limiting IO to
it SR, of cause) an so on.
Main issue is 'how to make it looking not like hack, but as
legitimate solution?'. If you have guts and will, you can create
new SR, which will bring specialized VM online during pbd-plug
operation.
SM stuff is written in python and somehow simple to debug (easier
than xapi ocaml code). You can even supply some data to VM via
PV-agrs.
30.06.2013 04:46, Grant McWilliams ÐÐÑÐÑ:
|