All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chun Yan Liu" <cyliu@suse.com>
To: Ian.Campbell@citrix.com, Ian Jackson <Ian.Jackson@eu.citrix.com>,
	stefano.stabellini@eu.citrix.com
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Xen-devel] [RFC PATCH V2 0/2] support xen HVM direct kernel boot
Date: Tue, 10 Jun 2014 21:09:56 -0600	[thread overview]
Message-ID: <539839040200006600036D54@soto.provo.novell.com> (raw)
In-Reply-To: <1401867299-7715-1-git-send-email-cyliu@suse.com>



>>> On 6/4/2014 at 03:34 PM, in message
<1401867299-7715-1-git-send-email-cyliu@suse.com>, Chunyan Liu <cyliu@suse.com>
wrote: 
> After your valuable suggestions, I'll continue the work to support 
> stubdom. But since stubdom currently uses qemu-xen-traditional and 
> will switch to qemu upstream in future, in a period of time, stubdom 
> HVM direct kernel boot won't be in working status. So, before 
> continuing the stubdom support work, I updated existing patch series, 
> adding proper error messages for rombios and stubdom limitation, 
> adding man page descriptions and other trival updates to make it a 
> complete working patch series. For those using seabios and non stubdom, 
> they can use now. 

Hi, Stefan, Ian J. & Ian C.,

I don't know if it's proper but could we merge current patch series first and
stubdom compatible work continued next? We do have some customers they
want to use it in guest installation. And considering: a) current patch series and
future stubdom compatible version will keep same user interface. b) stubdom
HVM direct kernel boot won't really work until stubdom-dm switches to qemu
upstream, maybe not soon? (I didn't see it in xen 4.5 development). c) how many
users will actually use stubdom and at the same time using direct kernel boot?

Regards,
Chunyan




> xen side patch: pass kernel/initrd/append parameters to qemu-dm 
> qemu side patch: reuse load_linux() for xen hvm direct kernel boot. 
>     Different from pc_memory_init which does lots of ram alloc work 
>     and rom/bios loading work, for xen, we only need to init a basic 
>     fw_cfg device used by load_linux() to store ADDRs and 
>     linuxboot.bin/multiboot.bin to retrive ADDRs, then load_linux(), 
>     after that, do real add option rom work to add 
>     linuxboot.bin/multiboot.bin to system option rom. Other things 
>     would be done by seabios smoothly. 
>  
> v1 is here: 
> http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06233.html 
>  
> Chunyan Liu (2): 
>   xen: pass kernel initrd to qemu 
>   qemu: support xen hvm direct kernel boot 
>  
> _______________________________________________ 
> Xen-devel mailing list 
> Xen-devel@lists.xen.org 
> http://lists.xen.org/xen-devel 
>  
>  

WARNING: multiple messages have this Message-ID (diff)
From: "Chun Yan Liu" <cyliu@suse.com>
To: Ian.Campbell@citrix.com, Ian Jackson <Ian.Jackson@eu.citrix.com>,
	stefano.stabellini@eu.citrix.com
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Xen-devel] [RFC PATCH V2 0/2] support xen HVM direct kernel boot
Date: Tue, 10 Jun 2014 21:09:56 -0600	[thread overview]
Message-ID: <539839040200006600036D54@soto.provo.novell.com> (raw)
In-Reply-To: <1401867299-7715-1-git-send-email-cyliu@suse.com>



>>> On 6/4/2014 at 03:34 PM, in message
<1401867299-7715-1-git-send-email-cyliu@suse.com>, Chunyan Liu <cyliu@suse.com>
wrote: 
> After your valuable suggestions, I'll continue the work to support 
> stubdom. But since stubdom currently uses qemu-xen-traditional and 
> will switch to qemu upstream in future, in a period of time, stubdom 
> HVM direct kernel boot won't be in working status. So, before 
> continuing the stubdom support work, I updated existing patch series, 
> adding proper error messages for rombios and stubdom limitation, 
> adding man page descriptions and other trival updates to make it a 
> complete working patch series. For those using seabios and non stubdom, 
> they can use now. 

Hi, Stefan, Ian J. & Ian C.,

I don't know if it's proper but could we merge current patch series first and
stubdom compatible work continued next? We do have some customers they
want to use it in guest installation. And considering: a) current patch series and
future stubdom compatible version will keep same user interface. b) stubdom
HVM direct kernel boot won't really work until stubdom-dm switches to qemu
upstream, maybe not soon? (I didn't see it in xen 4.5 development). c) how many
users will actually use stubdom and at the same time using direct kernel boot?

Regards,
Chunyan




> xen side patch: pass kernel/initrd/append parameters to qemu-dm 
> qemu side patch: reuse load_linux() for xen hvm direct kernel boot. 
>     Different from pc_memory_init which does lots of ram alloc work 
>     and rom/bios loading work, for xen, we only need to init a basic 
>     fw_cfg device used by load_linux() to store ADDRs and 
>     linuxboot.bin/multiboot.bin to retrive ADDRs, then load_linux(), 
>     after that, do real add option rom work to add 
>     linuxboot.bin/multiboot.bin to system option rom. Other things 
>     would be done by seabios smoothly. 
>  
> v1 is here: 
> http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06233.html 
>  
> Chunyan Liu (2): 
>   xen: pass kernel initrd to qemu 
>   qemu: support xen hvm direct kernel boot 
>  
> _______________________________________________ 
> Xen-devel mailing list 
> Xen-devel@lists.xen.org 
> http://lists.xen.org/xen-devel 
>  
>  

  parent reply	other threads:[~2014-06-11  3:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  7:34 [Qemu-devel] [RFC PATCH V2 0/2] support xen HVM direct kernel boot Chunyan Liu
2014-06-04  7:34 ` Chunyan Liu
2014-06-04  7:34 ` [Qemu-devel] [RFC PATCH V2 1/2] xen: pass kernel initrd to qemu Chunyan Liu
2014-06-04  7:34   ` Chunyan Liu
2014-06-06 15:12   ` [Qemu-devel] " Ian Campbell
2014-06-06 15:12     ` Ian Campbell
2014-06-12  9:58   ` [Qemu-devel] " Ian Campbell
2014-06-12  9:58     ` Ian Campbell
2014-06-13  5:43     ` [Qemu-devel] [Xen-devel] " Chun Yan Liu
2014-06-13  5:43       ` Chun Yan Liu
2014-06-13  8:28       ` [Qemu-devel] " Ian Campbell
2014-06-13  8:28         ` Ian Campbell
2014-06-16  7:14         ` [Qemu-devel] " Chun Yan Liu
2014-06-16  7:14           ` Chun Yan Liu
2014-06-16  9:57           ` [Qemu-devel] " Ian Campbell
2014-06-16  9:57             ` Ian Campbell
2014-06-04  7:34 ` [Qemu-devel] [RFC PATCH V2 2/2] qemu: support xen hvm direct kernel boot Chunyan Liu
2014-06-04  7:34   ` Chunyan Liu
2014-06-11  3:09 ` Chun Yan Liu [this message]
2014-06-11  3:09   ` [Xen-devel] [RFC PATCH V2 0/2] support xen HVM " Chun Yan 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=539839040200006600036D54@soto.provo.novell.com \
    --to=cyliu@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.