FuSa SIG/Features: Difference between revisions
From Xen
Jump to navigationJump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Features = |
= Features = |
||
* See https://wiki.xenproject.org/wiki/FuSa_SIG/Roadmap |
|||
* Dom0less reboot/Domain reset - Xen should be able to reboot a DomU. This may involve saving the kernel and other artefacts and reseting the devices, etc. |
|||
* Dom0less vcpu pinning - User should be able to pin a dom0less vcpu to a specific physical cpu |
|||
* Control domain / Hardware domain split - Currently dom0 is the control domain (ie privileged). It can create and destroy other domains and perform special operations. It is also the hardware domain as all the hardware gets assigned to it by default. We wish to split the responsibility between Control domain and hardware domain. IOW, the control domain needs to be separate from the hardware domain. The hardware domain will have the PV or VirtIO backends. |
|||
* XSM module to implement security policy - domctl/sysctl and various hypercalls need to have more granular security controls for different types of domains (control, hardware, driver and domU) |
|||
