similar to: access serial port in domU

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

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

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

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?

dear list, i''m trying to get a serial port working on my domU. I''m running debian etch (2.6.18-4-xen-amd64 and xen 3.0.3-1), same problem with debian testing I noticed that CONFIG_XEN_DISABLE_SERIAL is set to yes. But still serial access from dom0 works fine. after blacklisting the 8250/8250_pnp/serial_core drivers, i still cannot get serial access from domU (i do have the

I am new to this mailing list. I apologize if any needed information is missing. I know this is a bit much to ask of wine's current serial port implementation, I am hoping someone has maybe figured this out already? Or can help me further the debugging process, I'd rather be part of the solution then simply another complaint about wine's serial port. ***** problem description

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

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

Package: src:linux Version: 3.2.41-2 Severity: important 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

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

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

I''m having an issue forwarding through an Intel on-board graphics adapter. This is on a Dell Optiplex 780 with 8GB of RAM. The pass-through works perfectly fine if I have 2GB of RAM assigned to the HVM domU. If I try to assign 3GB or 4GB of RAM, I get the following on the console: [ 41.222073] br0: port 2(vif1.0) entering forwarding state [ 41.269854] (cdrom_add_media_watch()

Hi all, my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen installation when run perfectly in my other 3.0.2 (2.6.16) xen server. whe i start the domU with "xm create" i get these messages: Using config file "./debian.4-0.xen3.cfg". Started domain debian.4-0 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table

I am using ttylinux-xen file system image a a loopback device for the domain. I am mostly using the default configuration. I am not able to get networking on the domU. Are kernel "vmlinuz-2.6-xenU" as well as "2.6.11.12-xen0" both compiled w/o loadable module support? I guess it fails when it tries to initialize the iptables on the domU when it tries to do "modprobe".

Hello, I am using Xen 4.0.0_21091_06-0.1 on OpenSuse 11.3 64 bit, with a Windows XP Pro SP3 32 bit guest, and my workstation keeping locking up, even the NumLock and CapsLock keys being unresponsive when it does. Where should I begin troubleshooting? Thanks, Todd CPU info: ___________________________________________________________________________ processor : 0 vendor_id : GenuineIntel

Hi all, I have another problem with starting domainU (xenolinux). I took me pretty much quite some time and i can not figure out why starting a new domain is failing. I will really appreciate if somebody can help me with this error. The error I get when booting xen-domainU is: /======================= Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev

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, I have got xen compiled and installed properly.Domain 0 is created on the Xen port of Linux-2.6.11.10.But I am unable to boot the host domains. This is what one of my XenU config file contains [root@xion /]# cat /etc/xen/ttylinux kernel = "/boot/vmlinuz-2.6.11.10-xenU" memory = 64 name = "ttylinux" nics = 1 vif = [ ''mac=bb:00:00:00:00:11,

Hi, I've been getting these warnings in syslog since I've been running (Linux) kernels 2.6.31.x and up (I'm currently at 2.6.32.2), they do not show up on 2.6.30.x kernels. Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. ------------[ cut here ]------------ WARNING: at