From: Anthony Liguori <aliguori@us.ibm.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Jeremy Katz <katzj@redhat.com>,
Xen development list <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0/3] domUloader
Date: Wed, 18 Jan 2006 22:31:22 -0600 [thread overview]
Message-ID: <43CF161A.3060309@us.ibm.com> (raw)
In-Reply-To: <20060118232122.GZ16322@tpkurt.wlan.garloff.de>
On a side note, one thing we all have to think about is how a boot
loader would work with something like a virtual framebuffer.
It may be time to start thinking about writing a first class domU
bootloader. Something that just sets up a page table that maps the pfns
linearly and enough XenBus to read from a virtual disk. We can reuse
code from grub for filesystem parsing (or even write it from
scratch--it's not that hard to just read from a filesystem).
We could also use mini-OS as a base.
Regards,
Anthony Liguori
Kurt Garloff wrote:
>Hi Jeremy,
>
>On Wed, Jan 18, 2006 at 01:06:04PM -0500, Jeremy Katz wrote:
>
>
>>The other concern with mounting is that there have been some cases where
>>changes to filesystems have broken reading new filesystems with older
>>kernels. It's a lot easier to get the library that supports more (and
>>less has to be supported, so you're less likely to need to make changes)
>>than to upgrade your kernel for dom0
>>
>>
>
>I tend to disagree.
>As the dom0 kernel drives the hardware and hardware drivers seems
>to be the more prominent reason for moving to new kernel versions,
>I would assume the dom0 kernel to be updated more likely than the
>domU kernels.
>And actually, filesystem forward compatibility is not that bad.
>
>I'm not saying this can't be an issue, but I suspect it won't be
>for most people.
>
>Cheers,
>
>
next prev parent reply other threads:[~2006-01-19 4:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 23:43 [PATCH 0/3] domUloader Kurt Garloff
2006-01-17 11:52 ` Anthony Liguori
2006-01-17 14:34 ` Kurt Garloff
2006-01-17 17:28 ` Adam Heath
2006-01-17 21:28 ` Kurt Garloff
2006-01-17 21:41 ` Anthony Liguori
2006-01-18 18:06 ` Jeremy Katz
2006-01-18 23:21 ` Kurt Garloff
2006-01-19 4:31 ` Anthony Liguori [this message]
2006-01-19 17:19 ` Jeremy Katz
2006-01-20 20:36 ` Stephen Tweedie
2006-01-20 23:08 ` Philip R. Auld
2006-01-23 14:19 ` Kurt Garloff
2006-01-23 14:59 ` Philip R. Auld
2006-01-17 12:33 ` [PATCH] " Tim Deegan
[not found] ` <1137607621.22846.17.camel@bree.local.net>
2006-01-19 13:06 ` Tim Deegan
2006-01-20 12:43 ` Kurt Garloff
2006-01-23 13:39 ` Tim Deegan
2006-03-22 18:59 ` Matt Ayres
2006-03-22 22:01 ` Kurt Garloff
2006-04-17 19:56 ` Matt Ayres
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 10:17 Edwards, Nigel (Nigel Edwards)
2006-01-26 13:06 ` Mark Williamson
2006-01-26 13:37 ` Philip R. Auld
2006-01-26 14:01 ` Ian Campbell
2006-01-26 14:20 ` Philip R. Auld
2006-01-26 18:28 ` Kurt Garloff
2006-01-26 18:31 ` Mark Williamson
2006-01-26 18:57 ` Philip R. Auld
2006-01-26 19:14 ` Kurt Garloff
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=43CF161A.3060309@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=garloff@suse.de \
--cc=katzj@redhat.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.