From: Ian Campbell <Ian.Campbell@citrix.com>
To: "White, Edmund H" <edmund.h.white@intel.com>,
xen-devel <xen-devel@lists.xen.org>
Cc: "xen-users@lists.xen.org" <xen-users@lists.xen.org>
Subject: Re: [Xen-users] Multiple serial ports in Windows HVM
Date: Fri, 25 Jul 2014 08:52:23 +0100 [thread overview]
Message-ID: <1406274743.29480.56.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <37E70E4A0E073047B15F9D771CAD8F9F01CA98D7@BGSMSX101.gar.corp.intel.com>
On Thu, 2014-07-24 at 20:08 +0000, White, Edmund H wrote:
> I have just moved from Xen 4.3 to 4.4. With 4.3 I used the xm toolstack, and I could define multiple serial ports in the config for my Windows domU like so:
>
> serial = [ "tcp::4464,server,nowait", "file:/home/ed/logs/Tgt64bcom2.log" ]
I had no idea xm would accept a list here. We should probably look at
extending libxl/xl to support that. Is that something you think you
could take a look at?
> However, the xl toolstack in 4.4 won't accept a list in the serial definition. If I change it to:
>
> serial = "tcp::4464,server,nowait"
> serial = "file:/home/ed/logs/Tgt64bcom2.log"
>
> I end up with a single serial port connected to the file.
Right, the second one has overwritten the first.
> How can I get two serial ports, with the first connected to a socket and the second connected to a file?
Until someone implements support for lists of serial devices as a
workaround you can pass arbitrary arguments to the qemu device model
using
device_model_args=["--a thing", "--b another"]
It looks like the xm serial translated pretty directly into arguments to
-serial.
Ian.
next parent reply other threads:[~2014-07-25 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37E70E4A0E073047B15F9D771CAD8F9F01CA98D7@BGSMSX101.gar.corp.intel.com>
2014-07-25 7:52 ` Ian Campbell [this message]
2014-07-25 17:40 ` [Xen-users] Multiple serial ports in Windows HVM White, Edmund H
2014-07-28 9:38 ` Ian Campbell
2014-07-28 16:41 ` White, Edmund H
2014-07-28 16:46 ` 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=1406274743.29480.56.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=edmund.h.white@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@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).