Linux basedStub-domainwhy, how and benchmark                         Anthony PERARD                                  @ Cit...
"Normal" case● Device Model (QEMU) in dom0
Solution: stub-domain● The Device Model in its own domain
How to do it?● Current one based on mini-os  ○ use newlib● But QEMU upstream need more● So, two solutions:  ○ Port another...
What do we need?● Change in Linux  ○ Need to use dom0 privileged command (memory    mapping)● QEMU  ○ set_hvm_param DM_DOM...
Status● Can start a domain with both console and  network● Stubdom memory: 40MB
TODO●   upstream those patches●   integrate it in Xen build system●   have a video working●   could reduce the size of the...
Lies, damned lies, andbenchmarks●   With 8 CPU AMD Opteron, 8GB●   dom0: Arch Linux 64bit●   domU: Arch Linux 64bit, 2GB o...
benchmark - Network
benchmark - Disk
benchmark - Boot timeBetween `xl create vm` and `ssh guest true`
Conclusion● No more competition, priority inversion in  dom0● Extra layer against security vulnerability in  QEMU● Little ...
Question ?
Upcoming SlideShare
Loading in...5
×

Linux based Stubdomains

696

Published on

As the current stubdomain based on minios is difficult to maintain, we have worked on a stubdomain based on Linux. This helps to use QEMU upsteam in the stubdom with little change.

So first I will present how a Linux based stubdomain is built and lauched, and the difficulties around it. Then, to see if this is a viable option, I will show disk and network benchmarks to compare it with a traditional QEMU in dom0 configuration.

To finish, I will present the current limitations of this type of stubdomains.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
696
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Linux based Stubdomains

  1. 1. Linux basedStub-domainwhy, how and benchmark Anthony PERARD @ Citrix
  2. 2. "Normal" case● Device Model (QEMU) in dom0
  3. 3. Solution: stub-domain● The Device Model in its own domain
  4. 4. How to do it?● Current one based on mini-os ○ use newlib● But QEMU upstream need more● So, two solutions: ○ Port another libc to mini-os ○ Linux based stubdom
  5. 5. What do we need?● Change in Linux ○ Need to use dom0 privileged command (memory mapping)● QEMU ○ set_hvm_param DM_DOMAIN ○ no backend initialisation● libXenLight● initramfs
  6. 6. Status● Can start a domain with both console and network● Stubdom memory: 40MB
  7. 7. TODO● upstream those patches● integrate it in Xen build system● have a video working● could reduce the size of the stubdom
  8. 8. Lies, damned lies, andbenchmarks● With 8 CPU AMD Opteron, 8GB● dom0: Arch Linux 64bit● domU: Arch Linux 64bit, 2GB of RAM● (kernel Linux 3.4.8)● iperf for network● dd for disk
  9. 9. benchmark - Network
  10. 10. benchmark - Disk
  11. 11. benchmark - Boot timeBetween `xl create vm` and `ssh guest true`
  12. 12. Conclusion● No more competition, priority inversion in dom0● Extra layer against security vulnerability in QEMU● Little impact on performance● Should it be the default?
  13. 13. Question ?
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×