A Fault Tolerant Virtualization Server Based on Xen Jrgen Gro - - PowerPoint PPT Presentation

▶
a fault tolerant virtualization server based on xen
SMART_READER_LITE
LIVE PREVIEW

A Fault Tolerant Virtualization Server Based on Xen Jrgen Gro - - PowerPoint PPT Presentation

Oct 21, 2022 185 likes •424 views

A Fault Tolerant Virtualization Server Based on Xen Jrgen Gro Virtualization Kernel Developer SUSE Linux GmbH, jgross@suse.com Status Quo Standard Xen Virtualization Server dom0 HVM pv Net- Block- xenstore qemu backend backend

slide-1
SLIDE 1

A Fault Tolerant Virtualization Server Based on Xen

Jürgen Groß

Virtualization Kernel Developer SUSE Linux GmbH, jgross@suse.com

slide-2
SLIDE 2

Status Quo

slide-3
SLIDE 3

3

Standard Xen Virtualization Server

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Block- backend Net- backend

slide-4
SLIDE 4

4

Single Points of Failure in Xen Server

  • Hypervisor
  • Dom0
  • Xenstore
  • pv-Backends
  • LAN/SAN peripherals in case of single path
slide-5
SLIDE 5

5

Standard Xen Virtualization Server

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Block- backend Net- backend

slide-6
SLIDE 6

6

Kinds of Failures

  • Software errors (crashes, hangups)
  • Fatal Hardware errors
  • Non-fatal Hardware errors triggering software errors
  • Planned downtimes due to software updates
  • Planned downtimes due to hardware maintenance
slide-7
SLIDE 7

Eliminating Single Points of Failure

slide-8
SLIDE 8

8

Xen Server Today

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Block- backend Net- backend

slide-9
SLIDE 9

9

Use Multipathing

  • LAN and SAN resources still accessible in case of

path failure

  • Dom0 does multipathing for domUs
slide-10
SLIDE 10

10

Use Multipathing

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Block- backend Net- backend

slide-11
SLIDE 11

11

Move Xenstore Into Own Domain

  • Mandatory step for eliminating dom0 being single

point of failure

  • Xenstore is still single point of failure, but dom0 high

load won't slow it down any more

slide-12
SLIDE 12

12

Move Xenstore Into Own Domain

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Block- backend Net- backend

slide-13
SLIDE 13

13

Create Driver Domains

  • LAN

‒ One per interface card ‒ Multipathing done in guests ‒ Net-backend no longer single point of failure ‒ Driver domain can act as a managed switch

  • Block

‒ Multipathing still done in backend ‒ Further decoupling from dom0

slide-14
SLIDE 14

14

Create Driver Domains

LAN: one per interface adapter

SAN LAN dom0 Hypervisor HVM pv xenstore qemu Net- back Block- back Net- back

slide-15
SLIDE 15

15

Introduce pv-SAN Backend

  • Now one driver domain per interface card
  • Multipathing done in guests
  • Block-backend no longer a single point of failure
  • In case of SAN topology aware guests PCI-

passthrough of FC-cards to guest no longer necessary

  • Driver domain acts as a SAN switch
slide-16
SLIDE 16

16

Introduce pv-SAN Backend

  • ne per interface adapter

SAN LAN dom0 Hypervisor HVM pv xenstore qemu SAN- back Net- back SAN- back Net- back

slide-17
SLIDE 17

17

Use Stub Domains for HVM domUs

SAN LAN dom0 Hypervisor HVM pv xenstore stub qemu SAN- back Net- back SAN- back Net- back

slide-18
SLIDE 18

18

Make dom0 Restartable

SAN LAN dom0 Hypervisor HVM pv xenstore stub qemu SAN- back Net- back SAN- back Net- back

slide-19
SLIDE 19

How to Reach This Goal?

slide-20
SLIDE 20

20

TODO: Verification, Configuration

  • Xenstore domain
  • LAN driver domain
  • Block driver domain
  • Stub domains for HVM
slide-21
SLIDE 21

21

TODO: Implementation

  • Dom0 restart
  • SAN pv backend
  • Tooling for automatic creation of driver domains for

each interface card

  • Tooling for automatic restart of crashed infrastructure

domains (dom0, driver domains)

  • Support for software updates of infrastructure domains
  • Support for hotplug of interface cards
  • Support for live migration
slide-22
SLIDE 22

Thank you.

22

Who is interested? SUSE: ✔

slide-23
SLIDE 23

23