similar to: [PATCH] AF_VMCHANNEL address family for guest<->host communication.

Hi, I had a VM running on c3rh2 under 'vmc' user: [vmc at c3rh2 .ssh]$ virsh list --all Id Name State ---------------------------------------------------- 1 vs2relocate_nonRoot running After the virsh migration command, "virsh migrate --live --unsafe vs2relocate_nonRoot qemu+ssh://vmc at c3rh1.kirkland.ibm.com/session", this VM

Hi all, I just upgraded a test copy of my samba server from version 3.0.10E to the latest, 3.0.23D - the RPM available for Red Hat AS4 on the samba.org site. There was no samba-common, just samba, samba-client and samba-winbind RPMs. I installed all three successfully. I backed up my configs before hand and replaces / adapted them afterwards. I successfully added this server to the

The patch enables x86_32 PAE unmodified guests on 64-bit Xen when the hvm feature is present. We tested only Linux at this point, and we''ll improve the functionality as we test other guests. The SVM needs the equivalent changes to the vmc.c to get this functionality working, but this patch does not break the build. Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>

Hi all, I just upgraded a test copy of my samba server from version 3.0.10E to the latest, 3.0.23D - the RPM available for Red Hat AS4 on the samba.org site. There was no samba-common, just samba, samba-client and samba-winbind RPMs. I installed all three successfully. I backed up my configs before hand and replaces / adapted them afterwards. I successfully added this server to the domain

Hi All, Hi All, Here is a situation where everyone can read to, but not write to or delete, the shares on our Samba server: We moved the file server a few weeks ago - split off some files to a new Windows file server - and users could read but not write files to the old Samba server after it was renamed (SAN to OLDSAN). It turned out SELinux was running, which I disabled, rebooted, and all

doc/swfdec-sections.txt | 1 libswfdec/swfdec_as_debugger.h | 12 +++- libswfdec/swfdec_as_frame.c | 36 +++++++++++- libswfdec/swfdec_as_frame.h | 1 libswfdec/swfdec_as_types.h | 2 vivified/core/.gitignore | 2 vivified/core/Makefile.am | 25 +++++++- vivified/core/vivi_application.c | 12 +--- vivified/core/vivi_application.h |

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

Hello, first , I would like to thank you for your great work with wine. When will be possible I fine implementation of ODBC support in wine? the actual with MDAC25 /27/28 are not very fine and a lot of people have a lot of problem .... where are a very high application number that need this feature for run proporty. Thanks a lot

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

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

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

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

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

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.

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

I'm pleased to announce the release of libguestfs 1.0.64, the library for accessing and modifying virtual machine disk images. Homepage: http://libguestfs.org/ Downloads: http://libguestfs.org/download/ Git repo: http://git.et.redhat.com/?p=libguestfs.git Fedora builds: http://koji.fedoraproject.org/koji/packageinfo?packageID=8391 NOTE at present there is a bug in qemu's

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

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

After this, and adding a small hack to work around the Gnulib/setenv problem, I was able to get an appliance to boot. The actual appliance I was booting was one that I copied off a Fedora machine. However there is still some problem with vmchannel which I'm looking into, so the daemon cannot talk to the library yet. Rich. -- Richard Jones, Virtualization Group, Red Hat