similar to: Using serial port from a domU

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

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

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

Hello, I would like to use the kernel in the domU, so that a user can install it's own kernel. While starting the domU with pygrub I get the following error: "Error: Boot loader didn't return any data!" This is the configfile of the domU: -------------- # # Configuration file for the Xen instance lenny.vandervlis.nl, created # by xen-tools 3.9 on Sun Oct 19 15:46:03 2008. # #

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

Hello, im struggling with getting a Fedora 11 Domu up and running. My Host is a HP DL380 g6 with CentOS 5.5 and XEN 4 from gitco installed. The System runs several Linux-PV-DomUs like Debian Lenny, Ubuntu Lucid and CentOS-55 without any problems. But if i try to get stock F11 up and running. Using Virt-install, xm create with KS-Install and Converting a working HVM-Install did not suceed. The

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

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

I have installed xen on a node and while starting up a guest while in the kernel boot I am experiencing a hold/pause. The kernel stops in the boot sequence still loading the kernel at: stdout ... [ 3240.186441] xencons_init: Initializing xen vfb; pass xencons=tty to prevent this [ 3240.186538] Xen virtual console successfully installed as xvc0 [ 3240.186598] Event-channel device installed. [

Hello Dear everybody! I just installed CentOS 5.3 and try the built-in Xen 3.1 with it. But even the typical ttyLinux doesn''t work when the domain is created.-- it just doesn''t give me the login prompt while the domain ttylinux is booted. [root@soe-hd513-pc102 nimbus]# xm create ttylinux-xen.conf -c Using config file "./ttylinux-xen.conf". Started domain ttylinux

Hello, I have a problem since upgrading to the latest debian xen-kernel. In one of my domUs I had clamav installed. Every time I start clamav/reboot the domU it freezes and, seen from the dom0, in the domU something takes 100% of CPU. The only modifications I made were - the upgrade of the kernel from 2.6.18-xen-vserver-amd64 to 2.6.26-1-xen-amd64 - I added the following line to the file config

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?

Hi all, I''m trying hard to get a framebuffer console on a dom0 (Ubuntu 7.04/Debian Etch with (virtual)framebuffer support compiled it + Xen3.1) and already tried different tutorials, e.g. starting dom0 with kernel parameters - "xencons=xvc console=xvc0 console=tty1" or - "xencons=ttyS0 console=ttyS0 video=xenfb" and appending "S0:2345:respawn:/sbin/mingetty

Hi all, I''m trying hard to get a framebuffer console on a dom0 (Ubuntu 7.04/Debian Etch with (virtual)framebuffer support compiled it + Xen3.1) and already tried different tutorials, e.g. starting dom0 with kernel parameters - "xencons=xvc console=xvc0 console=tty1" or - "xencons=ttyS0 console=ttyS0 video=xenfb" and appending "S0:2345:respawn:/sbin/mingetty

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

Hi I have two box xen 3.2.1 and 3.3. On the 3.3 box I can''t use drbd as a device in the domu cfg. xm create -c test.cfg Using config file "/etc/xen/test.cfg". Error: Block device must have "phy", "file" or "tap" specified to type cat /etc/xen/test.cfg # Configuration file for the Xen instance test, created # by xen-tools 3.8 on Tue Sep 16

Hi to all! We're using CentOS 5.5 64bits for our Plesk 11. This week we had the following problem 3 times... Suddenly, the server stops responding in all services (SSH, Apache, Postfix, ...) but ping works! After wait a few minutes (or 2 hours some times) the server continues unresponsive until we reboot. After reboot we search on /var/log/messages but cannot find useful information...

I''m running xen 3.0.1 on the 2.6.12-26mdkxen0 mandriva kernel. (x86_64) When I set the serial line using the following configuration, my serial output is truncated as show in http://pastebin.ca/259403 title xen kernel (hd0,0)/xen.gz com1=115200n8 console=com1 xencons=serial module (hd0,0)/vmlinuz-2.6.12-26mdkxen0 root=/dev/sda2 module (hd0,0)/initrd-2.6.12-26mdkxen0.img The system is