From: Horms <horms@verge.net.au>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Kazuo Moriwaka <moriwaka@valinux.co.jp>,
xen-devel@lists.xensource.com,
Akio Takebe <takebe_akio@jp.fujitsu.com>,
Magnus Damm <magnus@valinux.co.jp>,
Isaku Yamahata <yamahata@valinux.co.jp>,
Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: Re: [PATCH]: kexec: framework and i386 (Take VIII)
Date: Thu, 18 May 2006 12:35:43 +0900 [thread overview]
Message-ID: <20060518033541.GA13670@verge.net.au> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D4BA719@liverpoolst.ad.cl.cam.ac.uk>
On Wed, May 17, 2006 at 11:40:32AM +0100, Ian Pratt wrote:
> > kexec -l -t multiboot-x86 --append="console=com1 sync_console
> > conswitch=bb com1=115200,8n1,0x3f8 dom0_mem=48000" /root/xen
> > --module="/root/vmlinuz-xen root=/dev/hda1 ro
> > console=ttyS0,115200 clock=pit ip=on apm=power-off"
> > --module=/tmp/initramfs_data.cpio
>
> The 'clock=pit ip=on apm=power-off' options are specific to your system
> rather than being required for the kexec to work, right?
Yes, that is correct, a more generic and minimal invocation would be:
kexec -l -t multiboot-x86 /root/xen --module="/root/vmlinuz-xen root=/dev/hda1 ro"
--
Horms http://www.vergenet.net/~horms/
next prev parent reply other threads:[~2006-05-18 3:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 10:40 Re: [PATCH]: kexec: framework and i386 (Take VIII) Ian Pratt
2006-05-18 3:35 ` Horms [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-07 4:45 [PATCH]: kexec: framework and i386 (Take VI) Horms
2006-05-09 4:16 ` [PATCH]: kexec: framework and i386 (Take VII) Horms
2006-05-09 9:18 ` [PATCH]: kexec: framework and i386 (Take VIII) Horms
2006-05-09 13:28 ` Akio Takebe
2006-05-16 10:43 ` Akio Takebe
2006-05-16 10:44 ` Keir Fraser
2006-05-16 11:03 ` Akio Takebe
2006-05-16 12:39 ` Keir Fraser
2006-05-17 2:44 ` Horms
2006-05-17 4:53 ` Horms
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=20060518033541.GA13670@verge.net.au \
--to=horms@verge.net.au \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=magnus@valinux.co.jp \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=moriwaka@valinux.co.jp \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.