similar to: serial port from domU

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

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

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, 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

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

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

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

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

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, 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

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__

Hello List If i have a PCI=[08:00.0](example) in any DomU config file the xm shutdown <ID> shuts down this DomU and the Dom0! Otherwise i shutdown this DomU from inside the DomU with halt or shutdown -r now, the Dom0 shuts down to. This happend on Xen 3.4.2 and Xen 4.0 (Kernel 2.6.18.8-xen, 2.6.18.8-xen0) The Operating System to Compile xen was Debian Lenny and the Dom0 os. Without

I've had several recent crashes of the nouveau kernel driver over the past month or so. My suspicion is that Firefox is causing it. The screen goes black and then the computer reboots. Nothing much in the syslogs, however I've managed to get netconsole output. It happens very infrequently and I'm afraid I don't know how to reproduce it, however I'll be more than happy to

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

http://bugs.freedesktop.org/show_bug.cgi?id=15233 Summary: geforce 7800gs and AGP 3.0 DBI function Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hallo, we use XEN with IA64. The console is not redirected to /dev/ttyS0. We need this port to configure an external storage with minicom but we cannot use it. We also see with modinfo no 8250 module which should control the serial port. We use XEN 3.0.3. Is there a workaround available? regards Bernd _______________________________________________ Xen-users mailing list