similar to: Setting up serial ports on kvm guests

I have been investigating pci pass-through for virtualized guests and the documentation I have found seems to me to lack a certain consistency in its example. This may be due to my not understanding what it is trying to inform me. What I wish to do is to configure a pci multi-port serial i/o card for use by a single virtual host. I start by running lspci -v on the host to identify the serial

These are the messages that I get when trying to attach a virtio disk to or perform a shutdown of the problem vm guest. Add hardware This device could not be attached to the running machine. Would you like to make the device available after the next guest shutdown? Requested operation is not valid: cannot do live update a device on inactive domain Traceback (most recent call last): File

Hi all, I've disabled cgroups v1 on my system with the kernel boot option "systemd.unified_cgroup_hierarchy=1". Since doing so, USB hotplugging fails to work, seemingly due to a permissions problem with BPF. Please note that the technique I'm going to describe worked just fine for hotplugging USB devices to running domains until this change. Attaching / detaching USB devices

On Mon, Jan 20, 2020 at 09:00:15PM +0100, Pol Van Aubel wrote: > Hi, > > Quoting Pavel Hrdina (2020-01-20 14:29:36) > > On Sat, Jan 18, 2020 at 11:17:11PM +0100, Pol Van Aubel wrote: > > > Hi all, > > > > > > I've disabled cgroups v1 on my system with the kernel boot option > > > "systemd.unified_cgroup_hierarchy=1". Since doing

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

Hi, Quoting Pavel Hrdina (2020-01-21 12:53:49) > On Mon, Jan 20, 2020 at 09:00:15PM +0100, Pol Van Aubel wrote: > > Hi, > > > > Quoting Pavel Hrdina (2020-01-20 14:29:36) > > > On Sat, Jan 18, 2020 at 11:17:11PM +0100, Pol Van Aubel wrote: > > > > Hi all, > > > > > > > > I've disabled cgroups v1 on my system with the kernel

We are in the process of migrating one of our embedded apps to use uart by default instead of sio in RELENG_7 in prep for the day when sio eventually disappears. Unfortunately, the application doesnt want to work with uart with puc backed devices, but still works with sio. Stranger still, the app works with the uart driver when uart attaches to the built in com port on the isa bus. However,

The vm host shows this: # setserial -g /dev/ttyS* /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 /dev/ttyS1, UART: 16950/954, Port: 0xd040, IRQ: 17 /dev/ttyS2, UART: 16950/954, Port: 0xd048, IRQ: 17 /dev/ttyS3, UART: 16950/954, Port: 0xd050, IRQ: 17 # # ll /dev/ttyS* crw-rw----. 1 root dialout 4, 64 Nov 10 12:18 /dev/ttyS0 crw-rw----. 1 root dialout 4, 65 Nov 10 12:18 /dev/ttyS1 crw-rw----. 1

This is a fairly standard and old machine with 2 COM ports. Recently (last Friday) I decided to update my RELENG_7 system and also to transition from sio to uart. This what I had before the upgrade: kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 kernel: sio0: type 16550A kernel: sio0: [FILTER] kernel: sio1: <16550A-compatible COM port> port

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE

Hi Julien > On some board, there is no alias to the UART. To avoid modification in > the device tree, dt-uart should also search device by path. > > To distinguish an alias from a path, dt-uart will check the first character. > If it''s a / then it''s path, otherwise it''s an alias. > > Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> >

Besides single-port serial cards, also accept multi-port ones and such providing mixed functionality (e.g. also having a parallel port). Reading PCI_INTERRUPT_PIN before ACPI gets enabled generally produces an incorrect IRQ (below 16, whereas after enabling ACPI it frequently would end up at a higher one), so this is useful (almost) only when a system already boots in ACPI mode. Signed-off-by:

We have upgraded a box from 6.2 to 6.3-RELEASE. Afterwards the box does not recognize its ST Lab I-160 serial card with Netmos 9845 Chipset. It worked flawlessly on 6.2 with puc(4) driver. >From dmesg: pci1: <simple comms, UART> at device 8.0 (no driver attached) ~# pciconf -l -v | grep -B 4 UART none2@pci1:8:0: class=0x070002 card=0x00041000 chip=0x98459710 rev=0x01 hdr=0x00

Prior to c/s 23811:f1349a968a5a LSR_THRE was checked only once, while there it got promoted into the surrounding loop''s condition. Since that bit may not clear for an extended period of time (i.e. when no new output is generated), it must not be used in this way indefinitely. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/char/ns16550.c +++

On Sat, Aug 01, 2015 at 12:58:40PM +0000, Tal Lubko via Syslinux wrote: > Hi > > I would like SYSLINUX to get input from UART and act accordingly. > For example, I want to choose what rootfs to load according to the sequence received from UART. > So I'd like to know if SYSLINUX a the infrastructure for doing this Yes, Syslinux supports serial ports a.k.a. UARTS. Since the very

Hi, I am trying to attach a usb device to my virtualbox node using libvirt. My node is already running, I stop my node and then I am trying to add this usb device. I have a separate xml file defined for usb. It looks like this: *<device> <hostdev mode='subsystem' type='usb'> <source> <vendor id='0x4321'/> <product

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

Hi all, I want to attach cdrom by libvirt.py .But can't find a func in libvirt.py can finish this work. Who can help me ? Regard -- Seven Ling E-mail: jiejie.ling at qq.com

On 01/28/18 20:15, Fred Smith wrote: > On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: >> I'm upgrading from CentOS6 to CentOS 7. >> >> I run 2 weather stations on C6 and have one of them attached to >> ttyS0 which is on the motherboard, and the other to ttyS2 which in >> on an add-on PCI serial card. >> >> I'm migrating the

Tal Lubko via Syslinux <syslinux at zytor.com> writes: > What I'm planning to do is to write COM32 image that will open UART > channel and wait for input (until timeout arrives). In case input > arrives, it will parse and validate it and act accordingly. > My solution doesn't involve user interaction. This is exactly what the Syslinux command interpreter does, if