From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCHv9 0/9] Xen: extend kexec hypercall for use with pv-ops kernels Date: Mon, 21 Oct 2013 13:26:56 +0100 Message-ID: <52651D90.1090502@citrix.com> References: <1381251310-29449-1-git-send-email-david.vrabel@citrix.com> <52650014.9020001@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52650014.9020001@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: David Vrabel Cc: "Xu, Jiajun" , "Xu, YongweiX" , Keir Fraser , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 21/10/13 11:21, David Vrabel wrote: > On 21/10/13 04:11, Xu, YongweiX wrote: >> Hi, David >> I have tried to use kexec with upstream xen source(C/S:27758) which has been put your patches and didn't not work on Dom0. Step as below: >> 1. use upstream xen and tools with your patch >> 2. use kexec-tools with branch "remotes/origin/xen-v6" >> 3. kexec -l -t multiboot-x86 /boot/xen.gz --module="/boot/vmlinuz-xen root=/dev/sda1 o" --module="/boot/initrd-xen.img" > > kexec segfaults for me here because of a missing command line for Xen. > Specifying one with --command-line="console=com1 etc" will work around this. > >> 4. kexec -e >> The phenomenon was that the kernel didn't change, but the network broke. >> >> Is there any problem in my operation? > > Yes, you're trying something that is not supported -- see the comment at > the top of kexec/arch/i386/kexec-multiboot-x86.c. Only ELF32 images are > supported. Huh. It does sort of work. There's a 3 minute or so delay between starting purgatory and Xen starting. I don't have time to look into this use case (kexec'ing into Xen) so if you care you'll have to do some digging yourself. David