search for: vmchannels

The change to "null vmchannel" didn't get reflected in the configure script which still checks for vmchannel in qemu. This patch tidies up this part of the configure script so we don't fail, provided we have support for user mode networking (which is required for null vmchannel). This patch didn't make it into 1.0.71. Rich. -- Richard Jones, Emerging Technologies, Red

This set of 10 patches removes the need for any vmchannel implementation, although we can still choose to use vmchannel if we want. In this so-called "null vmchannel" configuration, the appliance connects directly to a port on the library. The exact method is described in patch 9/10. This method still requires SLIRP (user mode networking) so it is not a panacea, because recent

There is a need for communication channel between host and various agents that are running inside a VM guest. The channel will be used for statistic gathering, logging, cut & paste, host screen resolution changes notifications, guest configuration etc. It is undesirable to use TCP/IP for this purpose since network connectivity may not exist between host and guest and if it exists the traffic

There is a need for communication channel between host and various agents that are running inside a VM guest. The channel will be used for statistic gathering, logging, cut & paste, host screen resolution changes notifications, guest configuration etc. It is undesirable to use TCP/IP for this purpose since network connectivity may not exist between host and guest and if it exists the traffic

Hi experts, When I start a VM using "virsh create vm.xml", I'm not able to connect to the vmchannel from host. The process libvirtd is running as root (modified qemu.conf to set user/group to root) already. The connect just hangs there even after the guest VM is up and running. However, if I start the VM using kvm directly (with same arguments as libvirtd in `ps auxwww`), the

Hi all. Having trouble figuring out the magic to set up VMChannel comms between EL6.x host/guests. My end goal is to enable fence_virt in the guest to talk to fence_virtd on the host via VMChannel. I'd prefer to use that instead of multicast because it is supposed to work even if networking in the guest is down/borked. My analysis is that there is a mismatch between what libvirt is feeding

This patch is in preparation for allowing libguestfs to use alternate "vmchannel" implementations. Although it's not a functional change, I think it is worthwhile on its own because use of the term "vmchannel" in the names of constants is inappropriate since (a) the "-net channel" option is now properly known upstream as "guestfwd", and (b) no one can

Hi, I am trying to set up vmchannel between the host and guest os. However, "sudo virsh start vm1" always gave me this error: ************************************************************* error: Failed to start domain vm1 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/5 bind(unix:/tmp/foo): Permission denied chardev:

This patch is for discussion only. The multiport virtio-console is not accepted upstream, and in any case is currently being rewritten for the nth time. Getting a test environment to test this out is also non-trivial. It look me about a day. You need to compile the alternate qemu (see URL in the patch + attached qemu patch on top of this). You also need to compile the alternate kernel - NOTE:

This also changes the name of the "vmchannel" buffer to just "buf", reflecting the fact that it's just used as a temporary buffer, and that the word vmchannel is overloaded. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages.

And with that, guestfish works on Mac OS X. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw -------------- next part -------------- >From

Notes: (1) Tis doesn't completely remove legacy serial ports yet. I couldn't work out how to make the Linux kernel see the virtconsole, so that is still using a serial port. (2) The guest network is completely unavailable if you apply this patch. We will need to add this back, possibly as an optional feature. Rich. -- Richard Jones, Virtualization Group, Red Hat

This attempts to implement the idea proposed in https://www.redhat.com/archives/libguestfs/2010-April/msg00087.html The idea is that an externally managed QEMU (manual, or via libvirt) can boot the appliance kernel/initrd. libguestfs can then be just told of the UNIX domain socket associated with the guest daemon. An example based on guestfish. 1. Step one, find the appliance kernel/initrd

...t;>> This can be easily extended. >>> >>> >> There shouldn't be an inherent limit in the userspace interface. >> >> > Well, qemu has those limits for all other interfaces (like number of > nics, serial ports, parallel ports), but if vmchannels are somehow > different in this regards there is no problem to dynamically grow their > number. > Having a limit in QEMU is fine, we just don't want the limit to be in the guest driver. It's relatively easy to increase the limit or make it dynamic in QEMU but if it requires...

...t;>> This can be easily extended. >>> >>> >> There shouldn't be an inherent limit in the userspace interface. >> >> > Well, qemu has those limits for all other interfaces (like number of > nics, serial ports, parallel ports), but if vmchannels are somehow > different in this regards there is no problem to dynamically grow their > number. > Having a limit in QEMU is fine, we just don't want the limit to be in the guest driver. It's relatively easy to increase the limit or make it dynamic in QEMU but if it requires...

-- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html -------------- next part -------------- >From 38588ad8f237f1a9987c832add6ed8ca07177194 Mon Sep 17

There's a new syntax check rule from gnulib. It requires that you write e.g., exit (EXIT_SUCCESS), not exit (0). And the same for 1/EXIT_FAILURE and any other constants. There were a lot of violations, including a few false positives, so I started with the exemptions (see the .x-sc file below). Then I converted the vast majority automatically, with this: maint: use EXIT_SUCCESS and

Hello, Here are two patches. One implements a virtio-serial device in qemu and the other is the driver for a guest kernel. While working on a vmchannel interface that is needed for communication between guest userspace and host userspace, I saw that most of the interface can be abstracted out as a "serial" device with "ports". Some requirements for a vmchannel are listed at

Hello, Here are two patches. One implements a virtio-serial device in qemu and the other is the driver for a guest kernel. While working on a vmchannel interface that is needed for communication between guest userspace and host userspace, I saw that most of the interface can be abstracted out as a "serial" device with "ports". Some requirements for a vmchannel are listed at

Signed-off-by: Hu Tao <hutao@cn.fujitsu.com> --- BUGS | 6 +++--- guestfs-release-notes.pod | 8 ++++---- guestfs-release-notes.txt | 8 ++++---- po-docs/ja.po | 8 ++++---- po-docs/libguestfs-docs.pot | 8 ++++---- po-docs/uk.po | 8 ++++---- 6 files changed, 23 insertions(+), 23 deletions(-) diff --git a/BUGS b/BUGS index