similar to: [RFC] Unify KVM kernel-space and user-space code into a single project

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

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

From: Borislav Petkov <bp at suse.de> So tools/ has been growing three, at a different stage of their development export.h headers and so we should unite into one. Add tools/include/ to the include path of virtio and liblockdep to pick the shared header now. Cc: Sasha Levin <sasha.levin at oracle.com> Cc: Peter Zijlstra <a.p.zijlstra at chello.nl> Cc: Paul Mackerras <paulus

From: Borislav Petkov <bp at suse.de> So tools/ has been growing three, at a different stage of their development export.h headers and so we should unite into one. Add tools/include/ to the include path of virtio and liblockdep to pick the shared header now. Cc: Sasha Levin <sasha.levin at oracle.com> Cc: Peter Zijlstra <a.p.zijlstra at chello.nl> Cc: Paul Mackerras <paulus

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

Em Tue, Feb 25, 2014 at 10:52:02PM +1030, Rusty Russell escreveu: > Borislav Petkov <bp at suse.de> writes: > > On Tue, Feb 25, 2014 at 12:09:23PM +1030, Rusty Russell wrote: > >> Should we get more ambitious and start a fake-kernel/ directory where > >> we can put userspace equivs/stubs of kernel functionality? > > > > Dunno - people like to do that

Em Tue, Feb 25, 2014 at 10:52:02PM +1030, Rusty Russell escreveu: > Borislav Petkov <bp at suse.de> writes: > > On Tue, Feb 25, 2014 at 12:09:23PM +1030, Rusty Russell wrote: > >> Should we get more ambitious and start a fake-kernel/ directory where > >> we can put userspace equivs/stubs of kernel functionality? > > > > Dunno - people like to do that

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

Hi, In this patch, I unify segment_32.h and segment_64.h into segment.h They have some common parts, but a considerable ammount of code still has to be around ifdefs. The only patch that is really important to paravirt is the first one, that moves a paravirt definition into the common header. The other two are just normal integration, and pretty much independent

Hi, In this patch, I unify segment_32.h and segment_64.h into segment.h They have some common parts, but a considerable ammount of code still has to be around ifdefs. The only patch that is really important to paravirt is the first one, that moves a paravirt definition into the common header. The other two are just normal integration, and pretty much independent

This series forms the kvm host part of paravirtual spinlock based against kvm tree. Please refer https://lkml.org/lkml/2013/8/6/178 for kvm guest part of the series. Please note that: kvm uapi: Add KICK_CPU and PV_UNHALT definition to uapi is a common patch for both guest and host. Srivatsa Vaddagiri (1): kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks

This series forms the kvm host part of paravirtual spinlock based against kvm tree. Please refer https://lkml.org/lkml/2013/8/6/178 for kvm guest part of the series. Please note that: kvm uapi: Add KICK_CPU and PV_UNHALT definition to uapi is a common patch for both guest and host. Srivatsa Vaddagiri (1): kvm hypervisor : Add a hypercall to KVM hypervisor to support pv-ticketlocks

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

This option, used for testing, causes the daemon to create the Unix domain socket (from guestfs_channel), listen on it, and accept a single connection. --- daemon/guestfsd.c | 65 ++++++++++++++++++++++++++++++++++++++--------------- daemon/guestfsd.pod | 9 ++++++++ 2 files changed, 56 insertions(+), 18 deletions(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index 8285d27..1bcdfa3

Rebased onto current acme/perf/core: -- From: Borislav Petkov <bp at suse.de> Date: Sun, 23 Feb 2014 12:04:53 +0100 Subject: [PATCH] tools: Unify export.h So tools/ has been growing three, at a different stage of their development export.h headers and so we should unite into one. Add tools/include/ to the include path of virtio and liblockdep to pick the shared header now. Cc: Sasha Levin

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

On Fri, Apr 11, 2014 at 01:59:30PM +0200, Jiri Olsa wrote: > hum, this breaks tarpkg test.. note that I needed attached patch to > make the test output verbose Bah, I could swear make -C tools/perf build-test passed before sending out. Alternatively, I might've been smoking something funny yesterday, though, too. Anyway, it is the MANIFEST - I keep forgetting this thing and acme

From: Borislav Petkov <bp at suse.de> So tools/ has been growing three, at a different stage of their development export.h headers and so we should unite into one. Add tools/include/ to the include path of virtio and liblockdep to pick the shared header now. Cc: Sasha Levin <sasha.levin at oracle.com> Cc: Peter Zijlstra <a.p.zijlstra at chello.nl> Cc: Paul Mackerras <paulus