forumuser@kogels.net
2005-Jul-03 18:47 UTC
[Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
Hi, After getting some nice feedback in this mailing list about drivers, I decided to compile xen0 -and xenU kernels so I can access my ISDN card from within the xenU domain. After booting my xen0 kernel my ISDN card is recognized perfectly: ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/none/1.1.2.2/1.1.2.2 CAPI Subsystem Rev 1.1.2.8 capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs) capifs: Rev 1.1.2.3 HiSax: Linux Driver for passive ISDN cards HiSax: Version 3.5 (kernel) HiSax: Layer1 Revision 2.46.2.5 HiSax: Layer2 Revision 2.30.2.4 HiSax: TeiMgr Revision 2.20.2.3 HiSax: Layer3 Revision 2.22.2.3 HiSax: LinkLayer Revision 2.59.2.4 HiSax: Total 1 card defined HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: AVM PCI driver Rev. 1.29.2.4 PCI: Obtained IRQ 22 for device 0000:01:0e.0 AVM PCI: stat 0x2020a AVM PCI: Class A Rev 2 HiSax: AVM Fritz!PCI config irq:22 base:0x7860 AVM PCI: ISAC version (0): 2086/2186 V1.1 AVM Fritz PnP/PCI: IRQ 22 count 0 AVM PCI/PnP: reset AVM PCI/PnP: S1 0 AVM Fritz PnP/PCI: IRQ 22 count 3 HiSax: DSS1 Rev. 2.32.2.3 HiSax: 2 channels added HiSax: MAX_WAITING_CALLS added Now I started up my xenU domain which does not show anything about found ISDN cards, but I am not worried as I don''t see any message about network cards either which work perfectly. But when starting my Asterisk server in the xenU domain I get some errors: Jul 3 18:10:36 ERROR[865]: Unable to register channel ''/dev/ttyI0'' Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed, returning -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so failed! So it looks that an unpriviliged domain cannot access my ISDN card? Digging further, I decided to boot a xen0 domain as guest instead of xenU. Now my ISDN card is recognized although not installed(?) ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/none/1.1.2.2/1.1.2.2 CAPI Subsystem Rev 1.1.2.8 capi20: Rev 1.1.2.7: started up with major 68 (middleware+capifs) capifs: Rev 1.1.2.3 HiSax: Linux Driver for passive ISDN cards HiSax: Version 3.5 (kernel) HiSax: Layer1 Revision 2.46.2.5 HiSax: Layer2 Revision 2.30.2.4 HiSax: TeiMgr Revision 2.20.2.3 HiSax: Layer3 Revision 2.22.2.3 HiSax: LinkLayer Revision 2.59.2.4 HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: AVM PCI driver Rev. 1.29.2.4 FritzPCI: No PCI card found HiSax: Card AVM Fritz PnP/PCI not installed ! Asterisk doesn''t complain anymore although I am not sure if it works... Does anyone know why xenU is not allowed to access my ISDN /dev/ttyI0? Thanks, Rene _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Williamson
2005-Jul-04 01:18 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
> Now I started up my xenU domain which does not show anything about found > ISDN cards, but I am not worried as I don''t see any message about network > cards either which work perfectly.The default configuration uses a virtual network card - network traffic gets sent via dom0, which owns the *real* network card.> But when starting my Asterisk server in the xenU domain I get some errors: > Jul 3 18:10:36 ERROR[865]: Unable to register channel ''/dev/ttyI0'' > Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed, returning > -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so failed! > > So it looks that an unpriviliged domain cannot access my ISDN card?The XenU kernel won''t support any real hardware devices, only Xen''s virtual devices.> Digging further, I decided to boot a xen0 domain as guest instead of xenU. > Now my ISDN card is recognized although not installed(?)> HiSax: AVM PCI driver Rev. 1.29.2.4 > FritzPCI: No PCI card found > HiSax: Card AVM Fritz PnP/PCI not installed ! > > Asterisk doesn''t complain anymore although I am not sure if it works... > > Does anyone know why xenU is not allowed to access my ISDN /dev/ttyI0?You need to give the domain direct access to the ISDN card. This is important because only one domain can own a PCI card at once. Multiple drivers fighting over a PCI card will end in tears... You need to hide the PCI device from dom0 so that it doesn''t try to drive it: add "physdev_dom0_hide=(xx.yy.z)" to Xen''s commandline, substituting the config address of your card (you can find this in the output of "lspci"). When you boot, check "xm dmesg" for an explicit line from Xen saying that it''s hiding the PCI device. If there isn''t one then something''s wrong - you''ll have to debug this first. Once hiding the device works, you need to give the domain access to it. You need to add this to the config file - the syntax for this is (I think) described in the user manual. Once you''ve done those things, boot the xen0 kernel in the domain and it should work. Let us know if you get stuck. Cheers, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
forumuser@kogels.net
2005-Jul-05 13:07 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
Hi Mark,
Making some progress now. However, I still have some problems although it
looks I can access the ISDN card so now and then.
This is what I have done:
title Xen 2.0 / XenLinux 2.6.11 rks
kernel /boot/xen.gz dom0_mem=64000 console=vga physdev_dom0_hide=(01:0d.0)
module /boot/vmlinuz-2.6.11-rks-xen0 root=/dev/hda3 ro console=tty0
And in my guest OS I put the line: pci = [''01,0e,0''] so I will
have access
to my ISDN PCI card. Asterisk is not complaining anymore, but no calls are
ISDN calls are "seen" by my gues OS.
Using lspvc -v I found out that the ISDN card did not got an IRQ, so I
inserted the card in another PCI-slot and rebooted the system. Now I get
the message that shows me an IRQ has been found:
ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/1.1.2.2/1.1.2.2
dss1_divert module successfully installed
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (kernel)
HiSax: Layer1 Revision 2.46.2.5
HiSax: Layer2 Revision 2.30.2.4
HiSax: TeiMgr Revision 2.20.2.3
HiSax: Layer3 Revision 2.22.2.3
HiSax: LinkLayer Revision 2.59.2.4
HiSax: Total 0 card defined
hisax_isac: ISAC-S/ISAC-SX ISDN driver v0.1.0
hisax_fcpcipnp: Fritz!Card PCI/PCIv2/PnP ISDN driver v0.0.1
HiSax: Card 1 Protocol EDSS1 Id=fcpcipnp0 (0)
HiSax: DSS1 Rev. 2.32.2.3
HiSax: 2 channels added
HiSax: MAX_WAITING_CALLS added
PCI: Obtained IRQ 21 for device 0000:01:0d.0
hisax_fcpcipnp: found adapter Fritz!Card PCI at 0000:01:0d.0
The only thing that worries me is the line "HiSax: Total 0 card
defined".
lspci -v looks ok now:
0000:01:0d.0 Network controller: AVM Audiovisuelles MKTG & Computer System
GmbH A1 ISDN [Fritz] (rev 02)
Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH
FRITZ!Card ISDN Controller
Flags: medium devsel, IRQ 21
Memory at febfff60 (32-bit, non-prefetchable) [size=32]
I/O ports at 7860 [size=32]
However, no calls are recognized by the card....
Now I start my guest OS (changing the pci = [''01,0e,0''] to
pci [''01,0d,0''] which sees my ISDN card:
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (kernel)
HiSax: Layer1 Revision 2.46.2.5
HiSax: Layer2 Revision 2.30.2.4
HiSax: TeiMgr Revision 2.20.2.3
HiSax: Layer3 Revision 2.22.2.3
HiSax: LinkLayer Revision 2.59.2.4
hisax_isac: ISAC-S/ISAC-SX ISDN driver v0.1.0
hisax_fcpcipnp: Fritz!Card PCI/PCIv2/PnP ISDN driver v0.0.1
HiSax: Card 1 Protocol EDSS1 Id=fcpcipnp0 (0)
HiSax: DSS1 Rev. 2.32.2.3
HiSax: 2 channels added
HiSax: MAX_WAITING_CALLS added
PCI: Obtained IRQ 21 for device 0000:01:0d.0
hisax_fcpcipnp: found adapter Fritz!Card PCI at 0000:01:0d.0
But again, no calls are recognized.
I have the feeling that this is an IRQ problem. I restarted the system
several times and I got it working once....
Does xen do anything special with interrupts I should be aware of?
Thanks,
Rene
>> Now I started up my xenU domain which does not show anything about
found
>> ISDN cards, but I am not worried as I don''t see any message
about
>> network
>> cards either which work perfectly.
>
> The default configuration uses a virtual network card - network traffic
> gets
> sent via dom0, which owns the *real* network card.
>
>> But when starting my Asterisk server in the xenU domain I get some
>> errors:
>> Jul 3 18:10:36 ERROR[865]: Unable to register channel
''/dev/ttyI0''
>> Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed,
>> returning
>> -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so failed!
>>
>> So it looks that an unpriviliged domain cannot access my ISDN card?
>
> The XenU kernel won''t support any real hardware devices, only
Xen''s
> virtual
> devices.
>
>> Digging further, I decided to boot a xen0 domain as guest instead of
>> xenU.
>> Now my ISDN card is recognized although not installed(?)
>
>> HiSax: AVM PCI driver Rev. 1.29.2.4
>> FritzPCI: No PCI card found
>> HiSax: Card AVM Fritz PnP/PCI not installed !
>>
>> Asterisk doesn''t complain anymore although I am not sure if it
works...
>>
>> Does anyone know why xenU is not allowed to access my ISDN /dev/ttyI0?
>
> You need to give the domain direct access to the ISDN card. This is
> important
> because only one domain can own a PCI card at once. Multiple drivers
> fighting over a PCI card will end in tears...
>
> You need to hide the PCI device from dom0 so that it doesn''t try
to drive
> it:
> add "physdev_dom0_hide=(xx.yy.z)" to Xen''s commandline,
substituting the
> config address of your card (you can find this in the output of
"lspci").
>
> When you boot, check "xm dmesg" for an explicit line from Xen
saying that
> it''s
> hiding the PCI device. If there isn''t one then
something''s wrong - you''ll
> have to debug this first.
>
> Once hiding the device works, you need to give the domain access to it.
> You
> need to add this to the config file - the syntax for this is (I think)
> described in the user manual.
>
> Once you''ve done those things, boot the xen0 kernel in the domain
and it
> should work. Let us know if you get stuck.
>
> Cheers,
> Mark
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Mark Williamson
2005-Jul-05 13:12 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
> Making some progress now. However, I still have some problems although it > looks I can access the ISDN card so now and then. > > This is what I have done: > > title Xen 2.0 / XenLinux 2.6.11 rks > kernel /boot/xen.gz dom0_mem=64000 console=vga > physdev_dom0_hide=(01:0d.0) module /boot/vmlinuz-2.6.11-rks-xen0 > root=/dev/hda3 ro console=tty0Looks good. Do you see the appropriate message from Xen at boot time, confirming that the card really is hidden?> And in my guest OS I put the line: pci = [''01,0e,0''] so I will have access > to my ISDN PCI card. Asterisk is not complaining anymore, but no calls are > ISDN calls are "seen" by my gues OS. > > Using lspvc -v I found out that the ISDN card did not got an IRQ, so I > inserted the card in another PCI-slot and rebooted the system. Now I get > the message that shows me an IRQ has been found:This is strange, it should just work. I guess your machine is probably sharing IRQs but that should work with Xen too.> The only thing that worries me is the line "HiSax: Total 0 card defined". > > lspci -v looks ok now: > 0000:01:0d.0 Network controller: AVM Audiovisuelles MKTG & Computer System > GmbH A1 ISDN [Fritz] (rev 02) > Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH > FRITZ!Card ISDN Controller > Flags: medium devsel, IRQ 21 > Memory at febfff60 (32-bit, non-prefetchable) [size=32] > I/O ports at 7860 [size=32]Looks sane. Can you confirm that the card doesn''t appear in dom0? Try lspci (and inspect the boot output). We don''t want the domains to fight.> But again, no calls are recognized.Can you try doing an outgoing call (e.g. fax someone) and see if that works?> I have the feeling that this is an IRQ problem. I restarted the system > several times and I got it working once.... > > Does xen do anything special with interrupts I should be aware of?I guess it could be an IRQ problem. We''ve not seen this behaviour before (that I know of) but I guess it could have been tickled by some quirk of your machine setup. Cheers, Mark> > Thanks, > Rene > > >> Now I started up my xenU domain which does not show anything about found > >> ISDN cards, but I am not worried as I don''t see any message about > >> network > >> cards either which work perfectly. > > > > The default configuration uses a virtual network card - network traffic > > gets > > sent via dom0, which owns the *real* network card. > > > >> But when starting my Asterisk server in the xenU domain I get some > >> errors: > >> Jul 3 18:10:36 ERROR[865]: Unable to register channel ''/dev/ttyI0'' > >> Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed, > >> returning > >> -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so failed! > >> > >> So it looks that an unpriviliged domain cannot access my ISDN card? > > > > The XenU kernel won''t support any real hardware devices, only Xen''s > > virtual > > devices. > > > >> Digging further, I decided to boot a xen0 domain as guest instead of > >> xenU. > >> Now my ISDN card is recognized although not installed(?) > >> > >> HiSax: AVM PCI driver Rev. 1.29.2.4 > >> FritzPCI: No PCI card found > >> HiSax: Card AVM Fritz PnP/PCI not installed ! > >> > >> Asterisk doesn''t complain anymore although I am not sure if it works... > >> > >> Does anyone know why xenU is not allowed to access my ISDN /dev/ttyI0? > > > > You need to give the domain direct access to the ISDN card. This is > > important > > because only one domain can own a PCI card at once. Multiple drivers > > fighting over a PCI card will end in tears... > > > > You need to hide the PCI device from dom0 so that it doesn''t try to drive > > it: > > add "physdev_dom0_hide=(xx.yy.z)" to Xen''s commandline, substituting the > > config address of your card (you can find this in the output of "lspci"). > > > > When you boot, check "xm dmesg" for an explicit line from Xen saying that > > it''s > > hiding the PCI device. If there isn''t one then something''s wrong - > > you''ll have to debug this first. > > > > Once hiding the device works, you need to give the domain access to it. > > You > > need to add this to the config file - the syntax for this is (I think) > > described in the user manual. > > > > Once you''ve done those things, boot the xen0 kernel in the domain and it > > should work. Let us know if you get stuck. > > > > Cheers, > > Mark > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
forumuser@kogels.net
2005-Jul-06 11:38 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
Hi, Ok, tried another day swapping the cards to get this working, but no luck :-( To answer your questions: Output of "xm dmesg" (last few lines) (XEN) Scrubbing DOM0 RAM: .done. (XEN) Hiding PCI device 01:08.0 from DOM0 (XEN) Scrubbing Free RAM: ...done. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). So Dom0 is hiding my ISDN card (note that the ISDN card is now in another PCI slot) I am not sure how to dial out as I am using Asterisk normally. Let me see if I can get this working. Also, I will try to install the ISDN card in another PC installing xen to see if this makes a difference. I will give some feedback when this all has been completed. Rene>> Making some progress now. However, I still have some problems although >> it >> looks I can access the ISDN card so now and then. >> >> This is what I have done: >> >> title Xen 2.0 / XenLinux 2.6.11 rks >> kernel /boot/xen.gz dom0_mem=64000 console=vga >> physdev_dom0_hide=(01:0d.0) module /boot/vmlinuz-2.6.11-rks-xen0 >> root=/dev/hda3 ro console=tty0 > > Looks good. Do you see the appropriate message from Xen at boot time, > confirming that the card really is hidden? > >> And in my guest OS I put the line: pci = [''01,0e,0''] so I will have >> access >> to my ISDN PCI card. Asterisk is not complaining anymore, but no calls >> are >> ISDN calls are "seen" by my gues OS. >> >> Using lspvc -v I found out that the ISDN card did not got an IRQ, so I >> inserted the card in another PCI-slot and rebooted the system. Now I get >> the message that shows me an IRQ has been found: > > This is strange, it should just work. I guess your machine is probably > sharing IRQs but that should work with Xen too. >> The only thing that worries me is the line "HiSax: Total 0 card >> defined". >> >> lspci -v looks ok now: >> 0000:01:0d.0 Network controller: AVM Audiovisuelles MKTG & Computer >> System >> GmbH A1 ISDN [Fritz] (rev 02) >> Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH >> FRITZ!Card ISDN Controller >> Flags: medium devsel, IRQ 21 >> Memory at febfff60 (32-bit, non-prefetchable) [size=32] >> I/O ports at 7860 [size=32] > > Looks sane. Can you confirm that the card doesn''t appear in dom0? Try > lspci > (and inspect the boot output). We don''t want the domains to fight. > >> But again, no calls are recognized. > > Can you try doing an outgoing call (e.g. fax someone) and see if that > works? > >> I have the feeling that this is an IRQ problem. I restarted the system >> several times and I got it working once.... >> >> Does xen do anything special with interrupts I should be aware of? > > I guess it could be an IRQ problem. We''ve not seen this behaviour before > (that I know of) but I guess it could have been tickled by some quirk of > your > machine setup. > > Cheers, > Mark > >> >> Thanks, >> Rene >> >> >> Now I started up my xenU domain which does not show anything about >> found >> >> ISDN cards, but I am not worried as I don''t see any message about >> >> network >> >> cards either which work perfectly. >> > >> > The default configuration uses a virtual network card - network >> traffic >> > gets >> > sent via dom0, which owns the *real* network card. >> > >> >> But when starting my Asterisk server in the xenU domain I get some >> >> errors: >> >> Jul 3 18:10:36 ERROR[865]: Unable to register channel ''/dev/ttyI0'' >> >> Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed, >> >> returning >> >> -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so failed! >> >> >> >> So it looks that an unpriviliged domain cannot access my ISDN card? >> > >> > The XenU kernel won''t support any real hardware devices, only Xen''s >> > virtual >> > devices. >> > >> >> Digging further, I decided to boot a xen0 domain as guest instead of >> >> xenU. >> >> Now my ISDN card is recognized although not installed(?) >> >> >> >> HiSax: AVM PCI driver Rev. 1.29.2.4 >> >> FritzPCI: No PCI card found >> >> HiSax: Card AVM Fritz PnP/PCI not installed ! >> >> >> >> Asterisk doesn''t complain anymore although I am not sure if it >> works... >> >> >> >> Does anyone know why xenU is not allowed to access my ISDN >> /dev/ttyI0? >> > >> > You need to give the domain direct access to the ISDN card. This is >> > important >> > because only one domain can own a PCI card at once. Multiple drivers >> > fighting over a PCI card will end in tears... >> > >> > You need to hide the PCI device from dom0 so that it doesn''t try to >> drive >> > it: >> > add "physdev_dom0_hide=(xx.yy.z)" to Xen''s commandline, substituting >> the >> > config address of your card (you can find this in the output of >> "lspci"). >> > >> > When you boot, check "xm dmesg" for an explicit line from Xen saying >> that >> > it''s >> > hiding the PCI device. If there isn''t one then something''s wrong - >> > you''ll have to debug this first. >> > >> > Once hiding the device works, you need to give the domain access to >> it. >> > You >> > need to add this to the config file - the syntax for this is (I think) >> > described in the user manual. >> > >> > Once you''ve done those things, boot the xen0 kernel in the domain and >> it >> > should work. Let us know if you get stuck. >> > >> > Cheers, >> > Mark >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xensource.com >> > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
forumuser@kogels.net
2005-Jul-07 17:49 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
Hi, Well, I did some tests and finally it''s working! I put my ISDN card in another PC, booted xen2.0 using the demo CD, bu also nothing! Then I inserted Knoppix wich did work. Looking at the wihc drivers have been loaded, I noticed something odd. The driver was not the fspcipnp hisax driver, but just a normal hisax module. This is strange because the xen2.0 demo CD discovered my Fritz!PCI ISDN card as a Fritz!PCI/PCIv2/PnP card using the fspcipnp driver. So, I recompiled my kernel using the Fritz!PCI driver, rebooted the PC, and bingo, calls er recognized (in xen0). Then I added the physdev_dom0_hide=(01:0d.0) statement to grub, rebooted again, and xen0 did not show any calls anymore, good! Then I started up xenU which did accept the calls, great! So the bottom line is that the wrong driver was used by the demo cd and my first compiled kernels. Everything looks fine now. Anyone who helped me the last week, thanks! Rene> Hi, > > Ok, tried another day swapping the cards to get this working, but no luck > :-( > > To answer your questions: > > Output of "xm dmesg" (last few lines) > > (XEN) Scrubbing DOM0 RAM: .done. > (XEN) Hiding PCI device 01:08.0 from DOM0 > (XEN) Scrubbing Free RAM: ...done. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen). > > So Dom0 is hiding my ISDN card (note that the ISDN card is now in another > PCI slot) > > I am not sure how to dial out as I am using Asterisk normally. Let me see > if I can get this working. Also, I will try to install the ISDN card in > another PC installing xen to see if this makes a difference. I will give > some feedback when this all has been completed. > > Rene > > > > >>> Making some progress now. However, I still have some problems although >>> it >>> looks I can access the ISDN card so now and then. >>> >>> This is what I have done: >>> >>> title Xen 2.0 / XenLinux 2.6.11 rks >>> kernel /boot/xen.gz dom0_mem=64000 console=vga >>> physdev_dom0_hide=(01:0d.0) module /boot/vmlinuz-2.6.11-rks-xen0 >>> root=/dev/hda3 ro console=tty0 >> >> Looks good. Do you see the appropriate message from Xen at boot time, >> confirming that the card really is hidden? >> >>> And in my guest OS I put the line: pci = [''01,0e,0''] so I will have >>> access >>> to my ISDN PCI card. Asterisk is not complaining anymore, but no calls >>> are >>> ISDN calls are "seen" by my gues OS. >>> >>> Using lspvc -v I found out that the ISDN card did not got an IRQ, so I >>> inserted the card in another PCI-slot and rebooted the system. Now I >>> get >>> the message that shows me an IRQ has been found: >> >> This is strange, it should just work. I guess your machine is probably >> sharing IRQs but that should work with Xen too. >>> The only thing that worries me is the line "HiSax: Total 0 card >>> defined". >>> >>> lspci -v looks ok now: >>> 0000:01:0d.0 Network controller: AVM Audiovisuelles MKTG & Computer >>> System >>> GmbH A1 ISDN [Fritz] (rev 02) >>> Subsystem: AVM Audiovisuelles MKTG & Computer System GmbH >>> FRITZ!Card ISDN Controller >>> Flags: medium devsel, IRQ 21 >>> Memory at febfff60 (32-bit, non-prefetchable) [size=32] >>> I/O ports at 7860 [size=32] >> >> Looks sane. Can you confirm that the card doesn''t appear in dom0? Try >> lspci >> (and inspect the boot output). We don''t want the domains to fight. >> >>> But again, no calls are recognized. >> >> Can you try doing an outgoing call (e.g. fax someone) and see if that >> works? >> >>> I have the feeling that this is an IRQ problem. I restarted the system >>> several times and I got it working once.... >>> >>> Does xen do anything special with interrupts I should be aware of? >> >> I guess it could be an IRQ problem. We''ve not seen this behaviour >> before >> (that I know of) but I guess it could have been tickled by some quirk of >> your >> machine setup. >> >> Cheers, >> Mark >> >>> >>> Thanks, >>> Rene >>> >>> >> Now I started up my xenU domain which does not show anything about >>> found >>> >> ISDN cards, but I am not worried as I don''t see any message about >>> >> network >>> >> cards either which work perfectly. >>> > >>> > The default configuration uses a virtual network card - network >>> traffic >>> > gets >>> > sent via dom0, which owns the *real* network card. >>> > >>> >> But when starting my Asterisk server in the xenU domain I get some >>> >> errors: >>> >> Jul 3 18:10:36 ERROR[865]: Unable to register channel ''/dev/ttyI0'' >>> >> Jul 3 18:10:36 WARNING[865]: chan_modem.so: load_module failed, >>> >> returning >>> >> -1 Jul 3 18:10:36 WARNING[865]: Loading module chan_modem.so >>> failed! >>> >> >>> >> So it looks that an unpriviliged domain cannot access my ISDN card? >>> > >>> > The XenU kernel won''t support any real hardware devices, only Xen''s >>> > virtual >>> > devices. >>> > >>> >> Digging further, I decided to boot a xen0 domain as guest instead of >>> >> xenU. >>> >> Now my ISDN card is recognized although not installed(?) >>> >> >>> >> HiSax: AVM PCI driver Rev. 1.29.2.4 >>> >> FritzPCI: No PCI card found >>> >> HiSax: Card AVM Fritz PnP/PCI not installed ! >>> >> >>> >> Asterisk doesn''t complain anymore although I am not sure if it >>> works... >>> >> >>> >> Does anyone know why xenU is not allowed to access my ISDN >>> /dev/ttyI0? >>> > >>> > You need to give the domain direct access to the ISDN card. This is >>> > important >>> > because only one domain can own a PCI card at once. Multiple drivers >>> > fighting over a PCI card will end in tears... >>> > >>> > You need to hide the PCI device from dom0 so that it doesn''t try to >>> drive >>> > it: >>> > add "physdev_dom0_hide=(xx.yy.z)" to Xen''s commandline, substituting >>> the >>> > config address of your card (you can find this in the output of >>> "lspci"). >>> > >>> > When you boot, check "xm dmesg" for an explicit line from Xen saying >>> that >>> > it''s >>> > hiding the PCI device. If there isn''t one then something''s wrong - >>> > you''ll have to debug this first. >>> > >>> > Once hiding the device works, you need to give the domain access to >>> it. >>> > You >>> > need to add this to the config file - the syntax for this is (I >>> think) >>> > described in the user manual. >>> > >>> > Once you''ve done those things, boot the xen0 kernel in the domain and >>> it >>> > should work. Let us know if you get stuck. >>> > >>> > Cheers, >>> > Mark >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xensource.com >>> > http://lists.xensource.com/xen-users >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sascha Retzki
2005-Jul-07 18:22 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
On Thu, Jul 07, 2005 at 07:49:23PM +0200, forumuser@kogels.net wrote:> So the bottom line is that the wrong driver was used by the demo cd and my > first compiled kernels. Everything looks fine now.The question is: why? :-) I mean, your kernels have been compiled by you on the assumption that the demo cd picked the right driver? If yes, why did the demo-cd picked the wrong one? What has been changed so the "is_this_really_the_card_I_am_responsible_for()" of the driver worked? Or is it just that they are mostly compatible in the init-functions? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
forumuser@kogels.net
2005-Jul-08 21:24 UTC
Re: [Xen-users] Accessing /dev/ttyI0 in guest domain not possible?
Good question. It could be that an unpatched xen kernel has the same problem though. If not, then there must be something in the xen patch which is responsible...> On Thu, Jul 07, 2005 at 07:49:23PM +0200, forumuser@kogels.net wrote: >> So the bottom line is that the wrong driver was used by the demo cd and >> my >> first compiled kernels. Everything looks fine now. > > The question is: why? :-) > > I mean, your kernels have been compiled by you on the assumption that the > demo cd picked the right driver? > If yes, why did the demo-cd picked the wrong one? What has been changed so > the "is_this_really_the_card_I_am_responsible_for()" of the driver worked? > > Or is it just that they are mostly compatible in the init-functions? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users