similar to: Serial Passthrough broken in Debian Wheezy?

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

Greetings, Using Xen 3.1 and Fedora 7, is it possible to export the serial interface such that I can access external devices on COM1 or COM2? I am uncertain if PCI pass-thru is needed or if there''s nothing to configure for this to work in a fully virtualized Linux guest. Any help would be greatly appreciated. Regards, Tony Johnson _______________________________________________

On Wed, 2014-11-05 at 17:56 +0100, Jonas Meurer wrote: [...] > So the question is: why does the VM run stable on xen1 while it > crashes all the time on xen2. If I compare xen1 and xen2, only > real difference is mainboard (Supermicro X8 on xen1; Supermicro > X9 on xen2) and CPU (Xeon L5939 on xen1; E5-2609 on xen2) > > As a next step I'll put the harddisks into another

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, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.

Hi all I have a problem switch in our data centre, which is connected to a linux server via a serial cable. I know I can / could access the switch from my Windows PC back at the office, using hyperterm, but trying to access it using minicom just doesn't seem to work. I have changed the comms in minincom to use /dev/tty0 & the baud rate to 9600, yet I can't seem to connect with

Package: logcheck Version: 1.2.27 Severity: wishlist hello, in ignore.d.server/oidentd you have: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ oidentd\[[0-9]+\]: Connection from \ [._[:alnum:]-]+ \([0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\):[0-9]{1,5}$ anyway, some oidentd logs don't have a hostname: oidentd[34562]: Connection from 241.145.24.135:2353 therefore you have to add: ^\w{3} [

Hi everyone, I would realy appreciate your help and guidense with a problem I have. Im trying to set up a SMS Gateway as a alert system for my network. Although the Aircard is picked up as a usb device and has a driver in the kernel, it does not have a /dev/XXX device name. So my question is how do I create this /dev/XXX device and make it persistent. I have installed CentOS as my base with

Hey again, Am 2014-08-19 12:26, schrieb Jonas Meurer: > I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU with > the > stock kernel. The dom0 runs the same linux kernel and > xen/4.1.4-3+deb7u1. the bug is still reproducible with the latest kernel and Xen packages from Debian Wheezy. Unfortunately it seems like a corner case, somehow related to the hardware

reassign 758622 linux-image-3.16.0-4-amd64 thanks Hi Ben, thanks for your response. Am 2014-11-05 21:40, schrieb Ben Hutchings: > On Wed, 2014-11-05 at 17:56 +0100, Jonas Meurer wrote: > [...] >> So the question is: why does the VM run stable on xen1 while it >> crashes all the time on xen2. If I compare xen1 and xen2, only >> real difference is mainboard (Supermicro X8

Hi there, i have a problem with the NOTIFYCMD in the upsmon.conf file. My line in the config looks like this: NOTIFYCMD "/etc/nut/upsnotify.sh" Now this ist my "/etc/nut/upsnotify.sh": #!/bin/bash EMAIL='mail at domain.de' SMS1='+49123456789' SMS2='+491987654231' #eMail versenden echo -e "Die USV mit dem Namen '$UPSNAME' hat seinen

How, exactly, does CentOS-6.3 with udev recognize an USB modem when it is plugged in. How is it indicated? What other configuration is required? I can find the modem in /sys/class/tty and I can get the attributes using udevadm but I do not see anything in ps that refers to the modem device. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne

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 :

Hi list-people! Is there anybody who has expiriences with sms gateway on Centos? Our customer has a Siemens modem (connected via serial port) and finds any tool for sending and receving sms. I found something like gammu and smstools but I'm not sure with it.. Have you any tips? Thanks a lot! JJ.

hello, What is the current situation with xen on amd64? the debian/sid archive keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile a 2.6.22 dom0 kernel with debian xen patches applied on my amd64 system. I have linux-source-2.6.22 and linux-patch-debian-2.6.22 installed, and followed the instructions from the workaround for

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

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kernel and Xen packages >

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

Hello, I''m working on a project and trying to pass through a PS/2 mouse + keyboard to a hardware VM. I''ve played with numerous things (including the obvious, using USB), but after finding no alternative, it seems like the best way to approach this would be to modify qemu-dm to pipe through data from /dev/input/eventwhatever to the keyboard/mouse that qemu provides (and then