search for: vcon1

...2", O_RDWR); ret = read(fd, buf, 100); ret = write(fd, string, strlen(string)); A name property, if set by the host, is exposed in /sys/class/virtio-console/vconNN/name that can be used to create symlinks by udev scripts, example: /dev/vcon/org.libvirt.channel.0 -> /dev/vcon1 For requirements, use-cases and some history see http://www.linux-kvm.org/page/VMchannel_Requirements Signed-off-by: Amit Shah <amit.shah at redhat.com> --- drivers/char/Kconfig | 6 + drivers/char/virtio_console.c | 1099 +++++++++++++++++++++++++++++++++++----- include...

...2", O_RDWR); ret = read(fd, buf, 100); ret = write(fd, string, strlen(string)); A name property, if set by the host, is exposed in /sys/class/virtio-console/vconNN/name that can be used to create symlinks by udev scripts, example: /dev/vcon/org.libvirt.channel.0 -> /dev/vcon1 For requirements, use-cases and some history see http://www.linux-kvm.org/page/VMchannel_Requirements Signed-off-by: Amit Shah <amit.shah at redhat.com> --- drivers/char/Kconfig | 6 + drivers/char/virtio_console.c | 1099 +++++++++++++++++++++++++++++++++++----- include...

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain backward compatibility, the first port to be spawned (port at id 0) is to be a console port, to be bound to hvc. This keeps new

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain backward compatibility, the first port to be spawned (port at id 0) is to be a console port, to be bound to hvc. This keeps new

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain backward compatibility, the first port to be spawned (port at id 0) is to be a console port, to be bound to hvc. This keeps new

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain backward compatibility, the first port to be spawned (port at id 0) is to be a console port, to be bound to hvc. This keeps new

(Rusty, would it improve the chances of getting this patch in your tree if this description were written with latex instead of without it?) Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain

(Rusty, would it improve the chances of getting this patch in your tree if this description were written with latex instead of without it?) Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. To maintain