Re: [Xen-devel] [Xen-users] Xen 4.2 TODO (io and irq parameter are not evaluated by xl)

["Kirk Allan" <kallan@xxxxxxxx>]

>>> On 8/31/2012 at 09:58 AM, in message
<5040FB490200007800097ED2@xxxxxxxxxxxxxxxxxxxx>, "Jan Beulich"
<JBeulich@xxxxxxxx> wrote: 
>>>> On 31.08.12 at 17:51, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> On Fri, 2012-08-31 at 16:40 +0100, Jan Beulich wrote:
>>> >>> On 31.08.12 at 17:01, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>>> > --- a/docs/man/xl.cfg.pod.5       Fri Aug 31 12:03:55 2012 +0100
>>> > +++ b/docs/man/xl.cfg.pod.5       Fri Aug 31 15:54:42 2012 +0100
>>> > @@ -402,6 +402,30 @@ for more information on the "permissive"
>>> >  
>>> >  =back
>>> >  
>>> > +=item B<ioports=[ "IOPORT_RANGE", "IOPORT_RANGE", ... ]>
>>> 
>>> Is this really with quotes, and requiring an array?
>> 
>> I was mostly just following
>> http://cmrg.fifthhorseman.net/wiki/xen#grantingaccesstoserialhardwaretoadomU 
> 
>> which suggested that this is the xm syntax too.
>> 
>>> > +
>>> > +=over 4
>>> > +
>>> > +Allow guest to access specific legacy I/O ports. Each B<IOPORT_RANGE>
>>> > +is given in hexadecimal and may either a span e.g. C<2f8-2ff>
>>> > +(inclusive) or a single I/O port C<2f8>.
>>> > +
>>> > +It is recommended to use this option only for trusted VMs under
>>> > +administrator control.
>>> > +
>>> > +=back
>>> > +
>>> > +=item B<irqs=[ NUMBER, NUMBER, ... ]>
>>> 
>>> Similarly here - is this really requiring an array? I ask because
>>> I had to look at this just last week for a colleague, and what
>>> we got out of inspection of examples/code was that a simple
>>> number (and a simple range without quotes above) are
>>> permitted too.
>> 
>> I had a look in create.py and opts.py and didn't see that, I suppose I
>> missed it.
>> 
>> I could implement support for either an array or a simple string/number
>> but it would complicate the code quite a bit. Is it really worth it?
> 
> 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, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel