From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [Xen-users] Multiple serial ports in Windows HVM Date: Fri, 25 Jul 2014 08:52:23 +0100 Message-ID: <1406274743.29480.56.camel@dagon.hellion.org.uk> References: <37E70E4A0E073047B15F9D771CAD8F9F01CA98D7@BGSMSX101.gar.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <37E70E4A0E073047B15F9D771CAD8F9F01CA98D7@BGSMSX101.gar.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "White, Edmund H" , xen-devel Cc: "xen-users@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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.