From: Avi Kivity <avi@redhat.com>
To: Eric Lacombe <goretux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [x86] - technical questions about HV implementation on Intel VT
Date: Tue, 21 Oct 2008 11:05:24 +0200 [thread overview]
Message-ID: <48FD9B54.4040109@redhat.com> (raw)
In-Reply-To: <200810201927.33580.goretux@gmail.com>
Eric Lacombe wrote:
> [...]
> So, when the host take control for the first time after the first vmexit, I
> would like the host to print informations and to "die correctly", so as I
> could read these information on the screen (ie, without being polluted with
> lots of debug messages that scroll on the screen).
>
You should add a serial console or netconsole to your hypervisor; that
means implementing a serial or network card driver.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-21 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 17:27 [x86] - technical questions about HV implementation on Intel VT Eric Lacombe
2008-10-21 9:05 ` Avi Kivity [this message]
2008-10-27 14:29 ` Eric Lacombe
2008-10-27 16:38 ` Avi Kivity
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=48FD9B54.4040109@redhat.com \
--to=avi@redhat.com \
--cc=goretux@gmail.com \
--cc=linux-kernel@vger.kernel.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).