All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Timo Benk <timo.benk@gmx.de>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: irq and ioports not working in 3.0.4-1 ?
Date: Thu, 28 Jun 2007 20:36:51 +0100	[thread overview]
Message-ID: <C2A9CC63.11866%keir@xensource.com> (raw)
In-Reply-To: <46840B9C.6060006@gmx.de>


Now fixed in the staging tree. Line 64 of
tools/python/xen/xend/server/irqif.py should be 'domid = ...' rather than
'dom = ...'.

 -- Keir

On 28/6/07 20:27, "Timo Benk" <timo.benk@gmx.de> wrote:

> Keir Fraser wrote:
>> Is there a backtrace in /var/log/xen/xend.log?
> Yepp, xend.log is attached.
> 
> 
>> On 28/6/07 20:18, "Timo Benk" <timo.benk@gmx.de> wrote:
>> 
>>> Hi,
>>> 
>>> i tried to give a domain acces to the parallel port. Here is what i have
>>> done:
>>> 
>>> Domain-0 # cat /proc/ioports
>>> [...]
>>> 0378-037a : parport0
>>> 0778-077a : parport0
>>> [...]
>>> 
>>> Domain-0 # cat /proc/interrupts
>>> [...]
>>>   7:          0          0        Phys-irq  parport0
>>> [...]
>>> 
>>> Domain-0 # vi /etc/xen/vm/xendom1
>>> [...]
>>> ioports = [ "0378-037a", "0778-077a" ]
>>> irq = [ 7 ]
>>> [...]
>>> 
>>> Domain-0 # xm create xendom1
>>> Using config file "/etc/xen/vm/xendom1".
>>> Error: function takes exactly 3 arguments (2 given)
>>> 
>>> 
>>> Is this a (known?) bug or am i doing something stupid?
>>> 
>>> Greetings,
>>> -timo
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 
> 

      reply	other threads:[~2007-06-28 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 19:18 irq and ioports not working in 3.0.4-1 ? Timo Benk
2007-06-28 19:22 ` Keir Fraser
2007-06-28 19:27   ` Timo Benk
2007-06-28 19:36     ` Keir Fraser [this message]

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=C2A9CC63.11866%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=timo.benk@gmx.de \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.