similar to: working config for xen which would transfer a serial interface

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

hi, i have centos 4.2. I have install a PCI card having serial port. when the os is booted it detects the new hardware ( serial port) .a device is also created /dev/ttyS0. the port works very goog on the same pc in windows XP. but when i connect any serial device to that port in linux it does not work. in /proc/ioports there is entry for that port as 0000-001f : dma1 0020-003f :

This is just a reposting of the patch that enables endian checks, with addition of trivial patches that drop __bitwise__ and __CHECK_ENDIAN__ everywhere. I plan to include this in my pull request unless I hear otherwise. Michael S. Tsirkin (8): linux/types.h: enable endian checks for all sparse builds tools: enable endian checks for all sparse builds Documentation/sparse: drop __bitwise__

This is just a reposting of the patch that enables endian checks, with addition of trivial patches that drop __bitwise__ and __CHECK_ENDIAN__ everywhere. I plan to include this in my pull request unless I hear otherwise. Michael S. Tsirkin (8): linux/types.h: enable endian checks for all sparse builds tools: enable endian checks for all sparse builds Documentation/sparse: drop __bitwise__

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()

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

Hi, I setup an asterisk system (asterisk 1.8-rc3, dahdi-linux-2.4.0 with dahdi-extra from Tzafrirs git, kernel 2.6.35.4). The hardware is an older pc system with Celeron CPU (2.5 GHz) with a Beronet BN4S0 ISDN card. The system starts without any errors. I discovered a severe issue. The kernel panics on a very small load. The first call normally gets through. If I start the second or third call

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 upgraded a test machine from OpenSuSE 11.1 to 11.2. I have found following bug: the server is a 2x quadcore intel box also 2x4=8cpu If you limit the dom0 cpu with dom0-cpus= [1-7]: - [xenwatch_cb] is running 100% cpu and makes var log entry every 65 sec BUG: soft lockup - CPU#X stuck for 61s! - xm commands not work - xend is dead if set dom0-cpus to 0 or 8: - everything looks

> ------------------------------ > > Message: 4 > Date: Wed, 2 Jun 2010 11:07:39 -0700 > From: Dale Johannesen <dalej at apple.com> > Subject: Re: [LLVMdev] Generating Floating point constants > To: St?phane Letz <letz at free.fr> > Cc: llvmdev at cs.uiuc.edu > Message-ID: <AEC895CC-E887-4329-8743-FA606BD401F6 at apple.com> > Content-Type:

Hi! I am trying to export a PCI device (an AVM Fritzcard PCI ISDN card...) to a domU but when starting my domU I am getting this error: "pciback pci-4-0: 22 Couldn''t locate PCI device (0000:00:06.0)! perhaps already in-use?" My system is running both debian etch in dom0 and domU... Below you can find (hopefully) all important information... Sincerely, Gaubatz Patrick

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

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

Hi, I am trying to build the Linux kernel with LLVM. 'ARCH=um' appears to work, now I am trying to get 'ARCH=x86' to work. So far it seems there is something wrong with the boot vga code (it finds no video modes), the acpi code, and the serial console code. I am now trying to compile drivers/ with llvm-gcc and the rest with gcc-4.2 (I have a wrapper script), I am compiling to

I have a box running CentOS 5.x 32 bit. I noticed these kernels are installed. [root at ns1 log]# rpm -qa |grep kern |sort kernel-2.6.18-194.11.1.el5 kernel-2.6.18-194.3.1.el5 kernel-2.6.18-194.8.1.el5 kernel-PAE-devel-2.6.18-194.11.1.el5 kernel-PAE-devel-2.6.18-194.3.1.el5 kernel-PAE-devel-2.6.18-194.8.1.el5 [root at ns1 log]# uname -a Linux ns1.xx.net 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10

Hi all.. I have found some problems on smbfs module in 2.4.18 kernel. I compiled it by myself (not the very first kernel compilation in my life ;-)) and then I have got it. Looks like it touch smbfs module as when I recompile 2.4.18 modules with smbfs sources changed to sources of smbfs from 2.4.17 problem disappears!! My mainboard is Abit BE6 with Pentium III 450 MHz. I am using SuSE 7.3 with

One problem I've discovered in cpuspeed is that there are drivers missing: # cd /lib/modules/2.6.18-194.8.1.el5/kernel/drivers/cpufreq # ll total 72 -rwxr--r-- 1 root root 14408 Jul 1 21:40 cpufreq_conservative.ko -rwxr--r-- 1 root root 16168 Jul 1 21:40 cpufreq_ondemand.ko -rwxr--r-- 1 root root 7624 Jul 1 21:40 cpufreq_powersave.ko -rwxr--r-- 1 root root 12524 Jul 1 21:40

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