similar to: Bug#708344: xen: serial passthrough broken in Debian Wheezy

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Hello, I just discovered a strange bug with serial passthrough in xen 4.1 on Debian Wheezy. The Dom0 has a GSM modem connected to serial port. The serial port is passed through to a DomU with options 'irq = [ 4 ]' and 'ioports = [ '3f8-3ff ]'. This worked as expected on Debian Squeeze with Xen 4.0 and Linux kernel 2.6.32 (both for Dom0 and DomU). On Debian Wheezy with Xen

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Hello, With Xen-4, is it still possible to access some serial device (an UPS in my case) from a domU ? I can''t get it to work : ttyS0 is here in dom0 ( as shown by commands like grep serial /proc/ioports ; dmesg | grep ttyS ; stty -aF /dev/ttyS0 ) but not from a domU : $ grep serial /proc/ioports $ dmesg | grep ttyS $ stty -aF /dev/ttyS0 stty: /dev/ttyS0: Input/output error $ ls

I am having problem when I am trying to access serial port in domU. I found a solution from the wiki.xensource.com as in the following lines: ___________________________________________________________________________ To have access to the serial port in DomU, we need to prevent Dom0 from taken hold of this piece of hardware add to /etc/hotplug/blacklist the following modules to exclude from

Hi everyone! I just wanted to share all the bits of information I needed while trying to get a serial modem to work under a Xen guest :) I found other howtos but every one was missing something. So, my setup consists of dom0 and domU with CentOS 5.2, kernel 2.6.18-92.1.10.el5xen and Xen 3.2.1 To get /dev/ttyS0 to work under domU: - Tell Xen to use something else for its console: in

Just something to be added: - This procedure doesn''t work with a Fedora 9 DomU - Maybe you have to blacklist some modules in the Dom0: AFAIK you have to rmmod (better: blacklist on boot using modprobe.conf) these modules: serial_core 8250 and 8250_pnp ----- Ursprüngliche Mail ---- Von: Federico Fanton <fake@panizzolo.it> An: xen-users@lists.xensource.com Gesendet: Freitag, den

I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem?

Hello Can anyone share a known working config for xen which would transfer a serial interface ( add-on card preferably, mine uses e880-e887 : 0000:03:05.0 / ec00-ec07 : 0000:03:05.0 ) to a DomU ? I've been trying with the stock packages from Centos 5.5 ( fully updated) and also with gitco's 3.4.3 but after 2 days of googling and testing we still fail to access the serial

Hello, I already worked with Samba (3.0.?) several month now on my NSLU2 with SlugOS BE. A few days ago the version was updated to 3.2.0 and no connection was possible afterwards. I searched the net but without relevant hits. I've created a new config file from scratch but got the same error again: root@LKG65AAA4:~$ netstat -an |egrep ':(137|138|139|445)' netstat: no support for

Hi everyone, I would realy appreciate your help and guidense with a problem I have. Im trying to set up a SMS Gateway as a alert system for my network. Although the Aircard is picked up as a usb device and has a driver in the kernel, it does not have a /dev/XXX device name. So my question is how do I create this /dev/XXX device and make it persistent. I have installed CentOS as my base with

Hi List, We have a problem in connecting ADS server from SAMBA. Whenever we try to contact the ADS server from the Samba its giving error as LDAP_NO_RESULTS_RETURNED. We have varified the code also, in the code also its giving three possibilities to raise that error message, I am pasting the portion of code here, File name: libads/ldap.c Function name: ads_server_info Code snippet

Hi. I''m trying to setup the serial port access from the domU following the instructions at http://wiki.xensource.com/xenwiki/InstallationNotes. So I addedd these configurations to the domU cfg file: irq = [ 4 ] ioports = [ "3f8-3ff" ] When I create this new domU I get this error: Error: function takes exactly 3 arguments (2 given) Is it a bug? I read on this list that you

Hi there, Im using for long time winbind + squid for my proxy server and it has been working very good... No problems at all. Some months ago, I decided to get rid of Netbios protocol and start to use only dns for name resolution on my domain. That's when my problem begin. All my windows servers and workstations are doing fine without netbios but I cant get winbind to work without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run a ldap backednd smaba 3.0.21c domain. I have 1 PDC, and 6 BDC's. On all the BDC's I can run 'pdbedit -Lw' but I get an error on the PDC. I turned the debuging up to 5, here's the output: pdbedit -Lw INFO: Current debug levels: all: True/5 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0

So, I made a mistake a bought four systems with the Intel Core i3 processors, without doing my homework to make sure that these systems actually supported VTd. Turns out there''s plenty of information out there indicating that the Core i3 processors do *not* support VTd. I was counting on VTd for two applications: Graphics Passthrough and passing through a PCIe 4-port serial card. Of

I have been trying to access a personal share being hosted by my schools netapp server and have been unable to do so using both version 3.04 and version 3.06 of samba. I have read the mailing list archives and found one set of posts related to the problem however there was no solution posted, so I am asking if anyone knows how to solve this problem. The previos posts that I am talking about are

Hi list-people! Is there anybody who has expiriences with sms gateway on Centos? Our customer has a Siemens modem (connected via serial port) and finds any tool for sending and receving sms. I found something like gammu and smstools but I'm not sure with it.. Have you any tips? Thanks a lot! JJ.

Package: logcheck Version: 1.2.27 Severity: wishlist hello, in ignore.d.server/oidentd you have: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ oidentd\[[0-9]+\]: Connection from \ [._[:alnum:]-]+ \([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\):[0-9]{1,5}$ anyway, some oidentd logs don't have a hostname: oidentd[34562]: Connection from 241.145.24.135:2353 therefore you have to add: ^\w{3} [

Hi folks. I discovered this odd behaviour a few days ago while playing with SAMBA_3 for the first time. The following points apply to samba-3.0.0beta and to cvs-20030807. 1. (tested with tdbsam) If I create a user entry with pdbedit, the domain name field is not set to the domain specified in the configuration file. For me it's getting set to the local machine name. If I logon to a