From: Zachary Amsden <zach@vmware.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt_ops xen booting
Date: Tue, 19 Sep 2006 17:30:43 -0700 [thread overview]
Message-ID: <45108BB3.7020306@vmware.com> (raw)
In-Reply-To: <20060920001110.GD7474@sequoia.sous-sol.org>
Chris Wright wrote:
> Just a note to let you know we've got domU booting with paravirt_ops
> XenoLinux. There's still some minor cleanups to do:
>
> - soft watchdog firing
> - inconsistent device probing
> - console on tty1
>
> Then onto smp support, and removing the rest of the limitations
> of the current patchset.
>
Congrats! ¡Mucho dolce vitale!
Should we just allow paravirt to disable soft watchdog? It really
doesn't make a lot of sense for paravirt - it should be the hypervisor's
responsibility, and it can break easily across discontinuous time jumps.
Zach
next prev parent reply other threads:[~2006-09-20 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 0:11 paravirt_ops xen booting Chris Wright
2006-09-20 0:30 ` Zachary Amsden [this message]
2006-09-20 1:02 ` Chris Wright
2006-09-20 1:45 ` Zachary Amsden
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=45108BB3.7020306@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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).