From: Ian Campbell <ian.campbell@citrix.com>
To: "Hu, Robert" <robert.hu@intel.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OSSTest -- debian-hvm-install, how to see the progress of guest auto installation
Date: Fri, 31 Jul 2015 08:53:27 +0100 [thread overview]
Message-ID: <1438329207.30740.9.camel@citrix.com> (raw)
In-Reply-To: <9E79D1C9A97CFD4097BCE431828FDD31D4AC2D@SHSMSX103.ccr.corp.intel.com>
On Fri, 2015-07-31 at 07:20 +0000, Hu, Robert wrote:
> Hi,
>
> During the hvm guest auto installation, how can I inspect its progress?
It's serial console is logged to the qemu-dm log, something like
/var/log/xen/qemu-dm-$guestname.log I think.
> Currently I encountered some problems during hvm auto-installation;
> after waited long time, several minutes, I vnc to it, it is black screen.
Right, I think that's expected because the installer is running on the
serial console now.
Currently the qemu-dm log is a mess of ANSI escape codes. If you "cat
/var/log/..." then your terminal will decode it and show the last thing on
the screen (hopefully an error dialog).
My series "fixes to ts-debian-hvm-install" posted to xen-devel on Monday
incorporates a switch to using DEBIAN_FRONTEND=text which produces a more
useful text log from the installer (the same as is used for host kernel
today).
>
> I'm using debian 7.2 for guest installation. And I saw Ian C. 's patch
> commit c60b6d20b0fd29836a224fdaf9f0d06272144b46
> Author: Ian Campbell <ian.campbell@citrix.com>
> Date: Mon Jul 6 14:45:12 2015 +0100
>
> ts-debian-hvm-install: Arrange for installed guest to use a serial
> console
>
> So that the guest boot will be logged somewhere useful (the qemu-dm
> log).
>
> It still seems to pickup a "quiet" from somewhere, so it's not as
> useful as it might be, but it is an improvement.
>
> debian 7.2 shall using kernel < 3.15,
Debian 7 (and all point releases) is using a 3.2 kernel.
> not sure if this commit causes the problem I'm meeting.
This commit will have changed where the guest console log will go but I
don't expect it to have caused whatever the underlying problem you are
seeing is.
Ian.
next prev parent reply other threads:[~2015-07-31 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 7:20 OSSTest -- debian-hvm-install, how to see the progress of guest auto installation Hu, Robert
2015-07-31 7:50 ` Wei Liu
2015-07-31 8:02 ` Hu, Robert
2015-07-31 7:53 ` Ian Campbell [this message]
2015-07-31 8:01 ` Hu, Robert
2015-07-31 8:29 ` Hu, Robert
2015-07-31 8:45 ` Ian Campbell
2015-07-31 8:47 ` Hu, Robert
2015-07-31 8:58 ` Ian Campbell
2015-08-04 10:30 ` Hu, Robert
2015-08-04 10:33 ` Ian Campbell
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=1438329207.30740.9.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=robert.hu@intel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.