similar to: Serial Port Access in DomU

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

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

Back in January there was a mail thread on this subject ( http://lists.xensource.com/archives/html/xen-devel/2005-01/msg00659.html ), however I see that blkfront still does not include ioctl support for disk geometry. So, any application that uses "sfdisk -g" to get the geometry of a partition, or disk, will fail when run in DomU. Is this a deliberate omission? Nick Logan

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 am using xen-unstable version and I can use the serial port to debug DomU openSuSE Linux with kgdb very well. But it doesn''t work when I am trying to debug DomU WinXP with windbg. I happened to find this link http://www.evilbitz.com/2006/12/13/howto-debugging-a-remote-windows-hvm-under-xen-using-windbg/, but it still doesn''t work for me. Any suggestions about this?

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

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 Litle hack to allow 2 serial port''s in HVM. in config set seriala=/dev/ttyS0 serialb=/dev/ttyS1 it''s work for me. some body else was intresting that. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

Hi everybody! I need to use a GSM modem attached to a serial port from domU running Linux 2.6.11 on Xen 2.0.6 (or I could go with -testing if needed). I don''t use it for networking, but for text messaging - it talks to a database and some other processes, i.e. I''d really like to avoid having the userspace driver in dom0. Is that somehow possible? I only know about dedicating

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?

we have got asterisk 1.0 (over 1 yrs old) version and very old zaptel version. That code is working only with 8 or less ports (accumulative) on digium fxs/fxo cards (2 cards with 4 ports each). the questoin is, what if we want 12 ports?..well, really, i don't understand the limitations? is it simply zaptel driver code fix? or kernel fix? or technology limitation? donno any tips would

Hi all, i have a CentoOS based Xen Dom0 running gitco xen3.3.1. I''m experiencing problems with debian Lenny FV domU. After some days of perfect working the VM start to consume all cpu and than i can only connect via ssh to VM and nothing work, neither the "top" command! Any idea? Thanks a lot and regards, Francesco

I have a file with 3 cols as: x y value 1 1 0.5000 1 2 1.8333 1 3 4.3333 2 1 0.7500 2 2 0.7500 2 3 4 3 1 0.7500 3 2 1.4167 3 3 5.1667 I read them in using p <- read.table("data.txt", header=TRUE) My questoin: how to draw a image to show the values at different positions (x, y)? I would like to see different colors for

Hi, Small questoin: when running the P2v hard disk image, and I want to convert a phyical machine to oVirt, to which machine do I connect when the GUI starts? one of the nodes or the hosted engine? (i'm not talking about the URL). Thanks

Hello, I´m trying to map one network interface of a Dual-Port e1000 Server Adapter to a DomU (firewall). In Dom0 the adaper is seen with lspci as: 06:00.0 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) 06:00.1 Ethernet controller: Intel Corporation 631xESB/632xESB DPT LAN Controller Copper (rev 01) My goal is to map only 06:00.1 to DomU so I used this

Hi list, We, an OSS advocacy group, setup a Xen 3.1 machine composed of : . a 64 bits dom0 running Debian stable amd64 . 2 hvm domUs running OpenBSD amd64 . 2 hvm domUs running NetBSD i386 This machine is to be hosted and reachable from the Internet, but it will only have one public IP. Naturally, our first tought was to port-forward using iptables / netfilter. We didn''t really

Hi. I forward ported XenLinux/IA64 domU portion and put it at http://people.valinux.co.jp/~yamahata/xen-ia64/20080207/xen_ia64-20080207.patch This patch is for 551e4fb2465b87de9d4aa1669b27d624435443bb of git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git It boots as domU and disk/network work. This patch is for those who are interested in XenLinux/IA64 upstream merge activity. Many

Hi, I am running xen-hypervisor over qemu. Now while running domU I want to write on an IO port, which I''ll be handling inside Qemu. Basically, this is a communication mechanism for me to communicate with qemu. I am writing on port number ''0x378'' as a root user using "outl" function. But when I run this code in domU, it does not reach qemu. So my question is: