Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Amit Shah
On Thu, 2019-07-18 at 09:15 +, Jan Beulich wrote: > On 17.07.2019 20:40, Andrew Cooper wrote: > > On 17/07/2019 14:02, Jan Beulich wrote: > > > On 17.07.2019 13:26, Andrew Cooper wrote: > > > > We do not want to be grovelling around in the old Xen's > > > > datastructures, > > > > because that

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Juergen Gross
On 18.07.19 11:40, Roger Pau Monné wrote: On Thu, Jul 18, 2019 at 11:00:23AM +0200, Juergen Gross wrote: On 17.07.19 00:27, Andrew Cooper wrote: On 16/07/2019 05:20, Sarah Newman wrote: On 7/15/19 8:48 PM, Juergen Gross wrote: On 15.07.19 21:31, Sarah Newman wrote: On 7/15/19 11:57 AM, Foer

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Roger Pau Monné
On Thu, Jul 18, 2019 at 11:00:23AM +0200, Juergen Gross wrote: > On 17.07.19 00:27, Andrew Cooper wrote: > > On 16/07/2019 05:20, Sarah Newman wrote: > > > On 7/15/19 8:48 PM, Juergen Gross wrote: > > > > On 15.07.19 21:31, Sarah Newman wrote: > > > > > On 7/15/19 11:57 AM, Foerster, Leonard wrote:

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Paul Durrant
> -Original Message- [snip] > > Longer term vision: > > * Have a tiny hypervisor between Guest and Xen that handles the common cases > -> this enables (almost) zero downtime for the guest > -> the tiny hypervisor will maintain the guest while the underlying xen > is kexecing

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Paul Durrant
> -Original Message- > From: Xen-devel On Behalf Of Juergen > Gross > Sent: 18 July 2019 10:00 > To: Andrew Cooper ; Sarah Newman ; > Foerster, Leonard > ; xen-devel@lists.xenproject.org > Subject: Re: [Xen-devel] Design session report: Live-Updating Xen >

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Jan Beulich
On 17.07.2019 20:40, Andrew Cooper wrote: > On 17/07/2019 14:02, Jan Beulich wrote: >> On 17.07.2019 13:26, Andrew Cooper wrote: >>> We do not want to be grovelling around in the old Xen's datastructures, >>> because that adds a binary A=>B translation which is >>> per-old-version-of-xen, meaning t

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-18 Thread Juergen Gross
On 17.07.19 00:27, Andrew Cooper wrote: On 16/07/2019 05:20, Sarah Newman wrote: On 7/15/19 8:48 PM, Juergen Gross wrote: On 15.07.19 21:31, Sarah Newman wrote: On 7/15/19 11:57 AM, Foerster, Leonard wrote: ... A key cornerstone for Live-update is guest transparent live migration ... -

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-17 Thread Andrew Cooper
On 17/07/2019 14:02, Jan Beulich wrote: > On 17.07.2019 13:26, Andrew Cooper wrote: >> On 17/07/2019 08:09, Jan Beulich wrote: >>> On 17.07.2019 01:51, Andrew Cooper wrote: On 15/07/2019 19:57, Foerster, Leonard wrote: > * dom0less: bootstrap domains without the involvement of dom0 >

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-17 Thread Jan Beulich
On 17.07.2019 13:26, Andrew Cooper wrote: > On 17/07/2019 08:09, Jan Beulich wrote: >> On 17.07.2019 01:51, Andrew Cooper wrote: >>> On 15/07/2019 19:57, Foerster, Leonard wrote: * dom0less: bootstrap domains without the involvement of dom0 -> this might come in handy to at

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-17 Thread Andrew Cooper
On 17/07/2019 08:09, Jan Beulich wrote: > On 17.07.2019 01:51, Andrew Cooper wrote: >> On 15/07/2019 19:57, Foerster, Leonard wrote: >>> * dom0less: bootstrap domains without the involvement of dom0 >>> -> this might come in handy to at least setup and continue dom0 >>> on target x

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-17 Thread Jan Beulich
On 17.07.2019 01:51, Andrew Cooper wrote: > On 15/07/2019 19:57, Foerster, Leonard wrote: >> * dom0less: bootstrap domains without the involvement of dom0 >> -> this might come in handy to at least setup and continue dom0 >> on target xen >> -> If we have this this m

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-16 Thread Andrew Cooper
On 15/07/2019 19:57, Foerster, Leonard wrote: > Here is the summary/notes from the Xen Live-Update Design session last week. > I tried to tie together the different topics we talked about into some > sections. > > https://cryptpad.fr/pad/#/2/pad/edit/fCwXg1GmSXXG8bc4ridHAsnR/ > > -- > Leonard > >

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-16 Thread Andrew Cooper
On 16/07/2019 05:20, Sarah Newman wrote: > On 7/15/19 8:48 PM, Juergen Gross wrote: >> On 15.07.19 21:31, Sarah Newman wrote: >>> On 7/15/19 11:57 AM, Foerster, Leonard wrote: >>> ... A key cornerstone for Live-update is guest transparent live migration >>> ... -> for live migration:

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-15 Thread Sarah Newman
On 7/15/19 8:48 PM, Juergen Gross wrote: On 15.07.19 21:31, Sarah Newman wrote: On 7/15/19 11:57 AM, Foerster, Leonard wrote: ... A key cornerstone for Live-update is guest transparent live migration ... -> for live migration: domid is a problem in this case     -> randomize and pray

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-15 Thread Juergen Gross
On 15.07.19 21:31, Sarah Newman wrote: On 7/15/19 11:57 AM, Foerster, Leonard wrote: ... A key cornerstone for Live-update is guest transparent live migration ... -> for live migration: domid is a problem in this case     -> randomize and pray does not work on smaller fleets     ->

Re: [Xen-devel] Design session report: Live-Updating Xen

2019-07-15 Thread Sarah Newman
On 7/15/19 11:57 AM, Foerster, Leonard wrote: ... A key cornerstone for Live-update is guest transparent live migration ... -> for live migration: domid is a problem in this case -> randomize and pray does not work on smaller fleets -> this is not a probl