This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] (strange idea) unfriendly migration

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] (strange idea) unfriendly migration
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Fri, 29 Oct 2010 23:07:21 +0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 29 Oct 2010 12:08:46 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=XA3LTxzpDXg7p8VEASgx10I/rCbmlANFZSJfCZkYdLo=; b=sWiuBpAanC/2t0Fdfg6G5wWOGFmLqUmpMfvVUtJ9XH7zv7lw0r0Udwa0aEuW2LAIYM c/B3ZlRc4J3QskeCdYtr7BPiZTECSsnERHjDV3+G5/CT1zkfVVWedRwJ9VVXkIYh+Yo4 hJz1cf+jD04pZW8/aJiIejsN/2kvZFK9XjxWA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; b=ly9/QQHFI3jZXWDe5/vc208EUCb+5UsTYrygv3rydEJKRj5Dg6sTAevaiXo42Bv6kU ggF66Js/lcjWJyw6sJaUPf1QDk5BuuWA6FB/vsp63dtwVYtmRMD57FH//cN7ScnLfKZI ZO9xdBPcQDWKm8q79C/Ds9TqRacYyuOaRMqc4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Good day.

As we all know, xen requires assist from VM to migrate it. If VM will
acts wrong during migration, it will crash, or behave strangely until
reboot (nice sample - default -xen kernel in lenny).

We need to accept changes in domU during migration: other domain id,
new vbd/vif and so on.

This fine until we talks about friendly VM. But if VM is not very
friendly? For example, VM's user can upgrade kernel to different -xen,
which one working fine with normal mode, but incompatible with
migration? (Pretty typical situation for any kind of cloud environment
or hosting).

Here I have two ideas: 

1) We can make HVM domain for Xen (recursive) with PV-only guests. If we
migrate manageable Xen with friendly dom0, it will keep unfriendly
(wild) domU working without knowing about migration.

2) Stop. Do we really needs a big and serious dom0 for 'inner xen'?

Here main idea:

If we create HVM-based overlay for PV-guest to keep thing unchanged, we
can make migration much simpler.

I'm not perfectly know xen internals, but here things I know to be
changed during migration:

1) Wall-clock
2) TSC
3) event channel
4) dom-id
5) vif/vbd entries in xenstore.

And if we make very small and very fine working proxy level between
guest and xen, we can free guest from thinking about Very Nontrivial

What proxy helper shall do? Let's call every thing changed during
migration a 'migration point'. So, helper shall take every migration
point from xen and dom0 (from xenstore and xen memory areas) and convert
them to matching domU migration point with simple condition: Migration
point of domU shall never be changed during VM power cycle. Note: not a
'domain life' (migrating vm changing one domain to other). Again: values
in xenstore from domU is absolute and shall be never changed.

And from Xen/dom0 point of view proxy helper will do thing smoothly will
full compability with xen without needs to be adopted to different OS'es
and kernel versions (no move war PV vs -xen, etc).

This will make thing very xen-like: we move all logic away from domU to
separate area (note: helper have no more rights than  domU, so no more
code to privileged domain).

Scheme of works:

dom0      ----- XEN  ----- [proxy]
xenstore  ~~~~~~~~~~~~~~~~~[proxy]======[PV-domain]

---, ~~~~ - changed during migration
========= - permanent during migration.

wBR, George.

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] (strange idea) unfriendly migration, George Shuklin <=