xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, Ian Campbell <ian.campbell@citrix.com>
Subject: [PATCH OSSTEST] stubdom: Arrange for guest serial to go to a host logfile
Date: Wed, 7 Oct 2015 10:34:02 +0100	[thread overview]
Message-ID: <1444210442-27743-1-git-send-email-ian.campbell@citrix.com> (raw)
In-Reply-To: <1444145468.5302.223.camel@citrix.com>

By pointing the serial port at 'file:/var/log/dm-serial.log' it will
end up on mini-os's console and therefore in
/var/log/xen/qemu-dm-$guest.log.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 Osstest/TestSupport.pm | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
index 69da459..f9eba6b 100644
--- a/Osstest/TestSupport.pm
+++ b/Osstest/TestSupport.pm
@@ -1822,7 +1822,10 @@ END
     my $stubdom = guest_var_boolean($gho, 'stubdom');
     if ($stubdom) {
 	$cfg .= "device_model_stubdomain_override=1\n";
-	$cfg .= "serial='pty'\n";
+	# MINI-OS turns any open of a path starting /var/log/ into a
+	# fd pointing to mini-os's console. IOW any such path used
+	# here ends up in the host logs in /var/log/xen/qemu-dm-$guest.log
+	$cfg .= "serial='file:/var/log/dm-serial.log'\n";
     } else {
 	$cfg .= "serial='file:/dev/stderr'\n";
     }
-- 
2.5.3

  reply	other threads:[~2015-10-07  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 18:21 [xen-unstable test] 62646: tolerable FAIL - PUSHED osstest service owner
2015-10-06 15:31 ` Ian Campbell
2015-10-07  9:34   ` Ian Campbell [this message]
2015-10-07  9:59     ` [PATCH OSSTEST] stubdom: Arrange for guest serial to go to a host logfile Ian Jackson
2015-10-07 10:58   ` [xen-unstable test] 62646: tolerable FAIL - PUSHED 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=1444210442-27743-1-git-send-email-ian.campbell@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.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 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).