xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Kirk Allan <kallan@suse.com>
Cc: Charles Arnold <CARNOLD@suse.com>,
	Dieter Bloms <xensource.com@bloms.de>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] Xen 4.2 TODO (io and irq parameter are not evaluated by xl)
Date: Fri, 31 Aug 2012 18:35:47 +0100	[thread overview]
Message-ID: <1346434547.5820.10.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <50409CE002000076000B3B44@novprvoes0310.provo.novell.com>

On Fri, 2012-08-31 at 18:15 +0100, Kirk Allan wrote:

> > Charles, Kirk, could you comment here?
> 
> In one of my Window's vm config files, I was able to get the vm to
> boot using ioports=['3f8-3ff'].  My goal was to do serial debugging of
> the Windows vm.  I also added irq=[4] to the config file.  However, I
> was not able to actually get a debug session to work.  The physical
> machine running windbg received a string from the vm which gave me
> hope that it was working, but then it never received further data so
> the vm eventually booted without being attached to the debugger.

Thanks, the question was whether it would be useful to implement the
	ioports = '3f8-3ff'
	irq = 4
syntax as well as the
	ioports = ['3f8-3ff']
	irq = [4]
but it looks like you are actually using the array version anyway?

I think I'd rather avoid implementing both options unless there is a
strong reason to do so.

Ian.

  reply	other threads:[~2012-08-31 17:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14  9:05 Xen 4.2 TODO / Release Plan Ian Campbell
2012-08-14  9:52 ` Jan Beulich
2012-08-14 10:07 ` Xen 4.2 TODO (io and irq parameter are not evaluated by xl) Dieter Bloms
2012-08-14 10:18 ` Xen 4.2 TODO / Release Plan / ipxe gcc 4.7 Pasi Kärkkäinen
2012-08-14 10:20   ` Pasi Kärkkäinen
2012-08-14 12:59     ` Ian Campbell
2012-08-14 14:26       ` Keir Fraser
     [not found] ` <20120814100704.GA19704@bloms.de>
2012-08-14 12:57   ` [Xen-users] Xen 4.2 TODO (io and irq parameter are not evaluated by xl) Ian Campbell
2012-08-31 13:59   ` Ian Campbell
2012-08-31 15:01     ` Ian Campbell
2012-08-31 15:13       ` Ian Jackson
2012-08-31 15:23         ` Ian Campbell
2012-08-31 15:57           ` Ian Jackson
2012-08-31 16:01             ` Ian Campbell
2012-08-31 15:40       ` Jan Beulich
2012-08-31 15:51         ` Ian Campbell
2012-08-31 15:58           ` Jan Beulich
2012-08-31 17:15             ` Kirk Allan
2012-08-31 17:35               ` Ian Campbell [this message]
2012-08-31 17:59                 ` Kirk Allan
2012-09-03  9:46                   ` Ian Campbell
2012-08-31 19:37                 ` Dieter Bloms
2012-09-03  9:15                   ` Ian Campbell
2012-09-03  7:50                 ` Jan Beulich
2012-09-03  9:15                   ` Ian Campbell
2012-08-15 15:46 ` Xen 4.2 TODO / Release Plan George Dunlap

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=1346434547.5820.10.camel@dagon.hellion.org.uk \
    --to=ian.campbell@citrix.com \
    --cc=CARNOLD@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=kallan@suse.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xensource.com@bloms.de \
    /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).