Re: [Xen-users] Problems with serial IO PCI card in DomU

["S. Kremer" <sk71@xxxxxx>]

Hi,

i tried this during runtime of xen with unbind/bind and new_slot for the
pciback.
After that i see the card in domU but i can not use the module that i
compile under dom0.
by using modprobe snx there is an error. I tried to compile the snx
module under domU but compilation ends with errors.

How can i use the serial adapter card with serial over ethernet? I found
ser2net but i don't know how i can use it in domU with hylafax to
redirect ttyS0 over ethernet to dom0.

Can you help me?


Am 20.01.2012 13:41, schrieb netz-haut - stephan seitz:
> I don't know which Kernel you're exactly running. I just peeked into a 
> squeeze's
> /boot/config-2.6.32-5-xen-amd64 and found
> 
> CONFIG_XEN_DOM0_PCI=y
> # CONFIG_XEN_PCI_PASSTHROUGH is not set
> CONFIG_PCI_XEN=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_PCIDEV_BACKEND=y
> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
> # CONFIG_XEN_PCIDEV_BE_DEBUG is not set
> CONFIG_XEN_PLATFORM_PCI=y
> 
> looks like pciback has been statically built into the kernel, so you should 
> be able
> to pciback.hide=(....) in your grub.cfg 
> 
> anyway, having CONFIG_XEN_PCI_PASSTHROUGH set by default is already on
> debians bugtracker:
> http://lists.debian.org/debian-kernel/2011/01/msg00700.html
> 
> 
> 
> 
> 
> 
> 
> -------- Weitergeleitete Nachricht --------
> Von: S. Kremer <sk71@xxxxxx <mailto:%22S.%20Kremer%22%20%3csk71@xxxxxx%3e> >
> Reply-to: "S. Kremer" <sk71@xxxxxx>
> An: xen-users@xxxxxxxxxxxxxxxxxxx <xen-users@xxxxxxxxxxxxxxxxxxx 
> <mailto:%22xen-users@xxxxxxxxxxxxxxxxxxx%22%20%3cxen-users@lists.xensource.com%3e>
>  >
> Betreff: Re: [Xen-users] Problems with serial IO PCI card in DomU
> Datum: Fri, 20 Jan 2012 07:46:42 +0100
> 
> 
> 
> Hi,
> 
> i get the following errors if i try to load the xen-pciback module
> 
> modprobe xen-pciback
> FATAL: Module xen_pciback not found.
> 
> modprobe pciback
> FATAL: Module pciback not found.
> 
> 
> find /lib -name "xen*" or  find /lib -name "pci*"
> 
> shows me no xen-pciback module
> 
> And lsmod shows me the following output
> 
> lsmod | grep pci
> pci_hotplug            21587  1 shpchp
> 
> 
> How can i redirect the ttyS0 over TCP/IP? I use a debian squeeze amd64
> system? And how can i use the redirected serial port in linux/windows
> client?
> 
> 
> Am 17.01.2012 23:26, schrieb netz-haut - stephan seitz:
>> Hi,
>>
>> I assume, you're running a different kernel in your domU.
>>
>> First, prepare your dom0:
>> - Blacklist the module in your dom0
>>     e.g. echo "blacklist snx" >> /etc/modprobe.d/blacklist-snx.conf
>> - Be sure to load the pci-back Module in dom0 (assuming this has been built 
>> as module)
>>     e.g. echo "xen-pciback" >> /etc/modules
>> - Hide the pci device in your dom0
>>     e.g. echo "options xen-pciback hide=(0000:08:03.0)" 
>> >>/etc/modprobe.d/xen-pciback.conf
>> In short words, be sure to disable that pci card in your dom0.
>> Maybe you'll want to have a look here : 
>> http://wiki.xensource.com/xenwiki/Assign_hardware_to_DomU_with_PCIBack_as_module
>> If xen-pciback has been statically built into your dom0 kernel, you could 
>> also try to add
>> pciback.hide=(0000:08:03.0) to your kernel parameters in your bootloader 
>> config.
>>
>> dom0 should NOT be able to use 08:03.0 anymore.
>>
>> Having this done, boot up your domU with the domU parameters, you've already 
>> added.
>> You didn't say how your domU is configured, personally I'ld always prefer 
>> the kernel and initrd inside the domU.
>> Install kernel-headers and build your snx module inside your domU.
>> Depending on your setup, there are many ways to get that module up in your 
>> domU, but building it inside a domU
>> is comparably painless when it comes to different compiler and/or kernel 
>> versions. Even if you think of updates.
>>
>> Now, modprobe snx inside your domU should drive the card.
>>
>> Anyway, I'ld doublecheck the necessity of pci-back/pci-front for relatively 
>> simple services like tty. In the long run,
>> an independent domU is much easier to handle. Using pci-back/pci-front, your 
>> domU has the potential capability
>> of kicking your whole box out of service. TTY can easily be redirected over 
>> TCP/IP. 
>>
>> Cheers,
>>
>>
>>
>>
>>
>>
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users