xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: xen-devel@lists.xen.org
Subject: Re: reboot dom0 without vps downtime
Date: Fri, 17 Mar 2017 09:56:44 +0100	[thread overview]
Message-ID: <51a486a4-a549-c1fb-b4b6-0fa6e2656f79@suse.com> (raw)
In-Reply-To: <CACaajQs=Tt=9KqmuB8QwYqB+NJ+d4dt7cFykus+gtyMxNmRbeg@mail.gmail.com>

On 17/03/17 09:49, Vasiliy Tolstov wrote:
> 2017-03-17 11:47 GMT+03:00 Juergen Gross <jgross@suse.com>:
>> (Dropping xen-users)
>>
>> I have plans for the future, but I'm not sure when I'll have enough
>> time for it.
>>
>> Any help on this topic is welcome, of course!
>>
>> I think (at least) the following features are missing:
>>
>> - capability to specify a (new) dom0 kernel and initrd for reboot of
>>   dom0: both must be transferred to the hypervisor in a memory buffer
>>   which will be used for the reboot
>> - dom0 reboot capability in hypervisor using the kernel and initrd
>>   from the memory buffer, without destroying other domains
>> - dom0 has to check for presence of xenstore-stubdom before trying to
>>   create it. In case xenstore is already existing connect to it and
>>   re-establish needed connections to other domains, don't auto-start
>>   any other domains in this case
>>
>> I'm sure there are lots of other little pieces missing, but those can
>> be addressed after above main features are available.
> 
> 
> What about qemu processes (i'm interesting on hvm domains pvh or how
> they naming now)

For pvh domains qemu processes aren't mandatory. All mandatory backends
like disk and net must live in stubdoms for dom0 being rebootable, of
course.

For hvm domains you have to use qemu-stubdoms. Those are supported with
qemu-traditional only right now. Support of upstream qemu in a stubdom
is another feature which would be nice to have, but this is no blocking
point for dom0 reboot.


Juergen


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-17  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  7:09 reboot dom0 without vps downtime Vasiliy Tolstov
2017-03-17  8:21 ` Juergen Gross
2017-03-17  8:23   ` Vasiliy Tolstov
2017-03-17  8:47     ` Juergen Gross
2017-03-17  8:49       ` Vasiliy Tolstov
2017-03-17  8:56         ` Juergen Gross [this message]
2017-03-17 10:25           ` Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51a486a4-a549-c1fb-b4b6-0fa6e2656f79@suse.com \
    --to=jgross@suse.com \
    --cc=v.tolstov@selfip.ru \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).