search for: fullvirt

This patch isn't quite finished. I also need to modify the virt-inspector "query mode" so that it can display the architecture. Nevertheless, text and XML output works for both Linux and Windows guests. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 75 OCaml packages (the

...with the physical machine. The VM's do not necessarily need to communicate with the rest of the world. The physical machine needs to communicate with the rest of the world. I use: - CentOS-6.4_64 - Virtual Machine Manager 0.9.0 - xen 4.2.3 - libvirt 0.10.2.7-5 - VM's show Hypervisor = xen (fullvirt) - Emulator = qemu-dm - NIC points to Shared device name virbr0 - on the host, virbr0 has IQ 192.168.122.1 I have been fighting this for 2 weeks, now. I tried to follow several advises which resulted in either the VM's not connecting to anything, or my host losing its connection to the rest of...

...: build: 4941 files, after adding hostfiles supermin: build: 4944 files, after munging supermin: failed to find a suitable kernel (host_cpu=powerpc64). I looked for kernels in /boot and modules in /lib/modules. If this is a Xen guest, and you only have Xen domU kernels installed, try installing a fullvirt kernel (only for supermin use, you shouldn't boot the Xen guest with it). libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above libguestfs-test-tool: failed to launch appliance libguestfs: closing guestfs handle 0x10016848 (state 0) libguestfs: command: run:...

...ostfiles > supermin: build: 4944 files, after munging > supermin: failed to find a suitable kernel (host_cpu=powerpc64). > > I looked for kernels in /boot and modules in /lib/modules. > > If this is a Xen guest, and you only have Xen domU kernels > installed, try installing a fullvirt kernel (only for > supermin use, you shouldn't boot the Xen guest with it). > libguestfs: error: /usr/bin/supermin exited with error status 1, see debug > messages above > libguestfs-test-tool: failed to launch appliance > libguestfs: closing guestfs handle 0x10016848 (state 0) &...

...libguestfs fails with an error message kind of that: > $ libguestfs-supermin-helper: failed to find a suitable kernel. > I looked for kernels in /boot and modules in /lib/modules. > If this is a Xen guest, and you only have Xen domU kernels > installed, try installing a fullvirt kernel (only for > libguestfs use, you shouldn't boot the Xen guest with it). > So this is correct because hypervisor's file system is minimalist and therefore contains > kernel files neither in /boot nor in /lib/modules. Ah I see, this is a slightly different problem. If t...

...+0530, abhishek jain wrote: > > supermin: failed to find a suitable kernel (host_cpu=powerpc64). > > > > I looked for kernels in /boot and modules in /lib/modules. > > > > If this is a Xen guest, and you only have Xen domU kernels > > installed, try installing a fullvirt kernel (only for > > supermin use, you shouldn't boot the Xen guest with it). > > libguestfs: error: /usr/bin/supermin exited with error status 1, see > debug > > messages above > > libguestfs-test-tool: failed to launch appliance > > libguestfs: closing guestfs...

...ppliance = (null) supermin helper [00000ms] inputs[0] = /usr/lib64/guestfs/supermin.d febootstrap-supermin-helper: failed to find a suitable kernel. I looked for kernels in /boot and modules in /lib/modules. If this is a Xen guest, and you only have Xen domU kernels installed, try installing a fullvirt kernel (only for febootstrap use, you shouldn't boot the Xen guest with it). libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs) libguestfs-test-tool: failed to launch appliance libguestfs: closin...

...: build: 4941 files, after adding hostfiles supermin: build: 4944 files, after munging supermin: failed to find a suitable kernel (host_cpu=powerpc64). I looked for kernels in /boot and modules in /lib/modules. If this is a Xen guest, and you only have Xen domU kernels installed, try installing a fullvirt kernel (only for supermin use, you shouldn't boot the Xen guest with it). libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above libguestfs-test-tool: failed to launch appliance libguestfs: closing guestfs handle 0x10016848 (state 0) libguestfs: command: run:...

...d: 6486 files, after removing unreadable files supermin: build: 6489 files, after munging supermin: failed to find a suitable kernel (host_cpu=x86_64). I looked for kernels in /boot and modules in /lib/modules. If this is a Xen guest, and you only have Xen domU kernels installed, try installing a fullvirt kernel (only for supermin use, you shouldn't boot the Xen guest with it). libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above libguestfs: trace: launch = -1 (error) libguestfs: trace: close libguestfs: closing guestfs handle 0x5627c93af260 (state 0) libgues...

Glad Buddy.:-) It worked. Thanks a lot. I'm having some urgent deliverable and this would really help me alot. Thanks again. Would love to trouble you again . On Thu, May 29, 2014 at 9:34 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Thu, May 29, 2014 at 09:30:45PM +0530, abhishek jain wrote: > [...] > > checking for main in -lreadline... no > >

...#39;t know what's in that uImage file, so I suggest compiling supermin yourself, running the command by hand, and adding printf's to src/kernel.ml in supermin to find the problem. Rich. > > If this is a Xen guest, and you only have Xen domU kernels > installed, try installing a fullvirt kernel (only for > supermin use, you shouldn't boot the Xen guest with it). > libguestfs: error: /usr/bin/supermin exited with error status 1, see debug > messages above > libguestfs-test-tool: failed to launch appliance > libguestfs: closing guestfs handle 0x10016848 (state 0) &...

...no_kernels (host_cpu) = eprintf "\ -supermin: failed to find a suitable kernel. +supermin: failed to find a suitable kernel (host_cpu=%s). I looked for kernels in /boot and modules in /lib/modules. If this is a Xen guest, and you only have Xen domU kernels installed, try installing a fullvirt kernel (only for -supermin use, you shouldn't boot the Xen guest with it).\n"; +supermin use, you shouldn't boot the Xen guest with it).\n" + host_cpu; exit 1 and find_dtb debug copy_kernel kernel_name wildcard dtb = @@ -200,7 +212,8 @@ and has_modpath kernel_name = |...

...ging >> > supermin: failed to find a suitable kernel (host_cpu=powerpc64). >> > >> > I looked for kernels in /boot and modules in /lib/modules. >> > >> > If this is a Xen guest, and you only have Xen domU kernels >> > installed, try installing a fullvirt kernel (only for >> > supermin use, you shouldn't boot the Xen guest with it). >> > libguestfs: error: /usr/bin/supermin exited with error status 1, see >> debug >> > messages above >> > libguestfs-test-tool: failed to launch appliance >> > lib...

* Richard W.M. Jones: > On Sat, Apr 26, 2014 at 02:27:07PM +0200, Hilko Bengen wrote: >> --- >> src/kernel.ml | 43 ++++++++++++++++++++++++++++--------------- >> 1 file changed, 28 insertions(+), 15 deletions(-) >> >> diff --git a/src/kernel.ml b/src/kernel.ml >> index ed5aea3..436b1b0 100644 >> --- a/src/kernel.ml >> +++ b/src/kernel.ml

On Wed, Jun 04, 2014 at 02:25:58PM +0530, abhishek jain wrote: > Hi RIch > > > Below are the details of the powerpc ubuntu system ... > > ls -l /boot/ > total 10200 > -rw-r--r-- 1 root root 5224765 Nov 22 2013 uImage > -rw-r--r-- 1 root root 5192861 Nov 22 2013 uImage.orig > > > ls -l /lib/modules/ > total 4 > drwxr-xr-x 3 ubuntu ubuntu 4096 Jun 3

...> root@e91c89e0874d:/# libguestfs-test-tool > [...] > supermin: failed to find a suitable kernel (host_cpu=x86_64). > > I looked for kernels in /boot and modules in /lib/modules. > > If this is a Xen guest, and you only have Xen domU kernels > installed, try installing a fullvirt kernel (only for > supermin use, you shouldn't boot the Xen guest with it). > libguestfs: error: /usr/bin/supermin exited with error status 1, see debug messages above > libguestfs: trace: launch = -1 (error) > libguestfs: trace: close > libguestfs: closing guestfs handle 0x5627c...

...aravirt libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vnc libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: 127.0.0.1:1 but for hv systems xl is being passed libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -domain-name libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: fullvirt libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vnc libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: 127.0.0.1:0 libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -vncunused libxl: debug: libxl_dm.c:1213:libxl__spawn_local_dm: -serial libxl: debug: libxl_dm.c:1213:libxl__spawn_...

On 11/21/2013 05:56 PM, Richard W.M. Jones wrote: > [Adding Itamar: Any suggestions on where Vitaly could get help on this > RHEV-M API problem?] > > On Thu, Nov 21, 2013 at 02:27:08PM +0000, Исаев Виталий Анатольевич wrote: >> Dear libguestfs developers, >> >> We are developing the protected enterprise system based on several >> Red Hat technologies (Red Hat

...he rest of the world. > > The physical machine needs to communicate with the rest of the world. > > > I use: > > - CentOS-6.4_64 > > - Virtual Machine Manager 0.9.0 > > - xen 4.2.3 > > - libvirt 0.10.2.7-5 > > - VM?s show Hypervisor = xen (fullvirt) > > - Emulator = qemu-dm > > - NIC points to Shared device name virbr0 > > - on the host, virbr0 has IQ 192.168.122.1 > > > I have been fighting this for 2 weeks, now. I tried to follow several > advises which resulted in either the VM?s not connecting to an...

...0ms] inputs[0] = /usr/lib64/guestfs/supermin.d > > febootstrap-supermin-helper: failed to find a suitable kernel. > > I looked for kernels in /boot and modules in /lib/modules. > > If this is a Xen guest, and you only have Xen domU kernels > > installed, try installing a fullvirt kernel (only for > > febootstrap use, you shouldn't boot the Xen guest with it). > > libguestfs: error: cannot find any suitable libguestfs supermin, fixed > or old-style appliance on LIBGUESTFS_PATH (search > path: /usr/lib64/guestfs) > > libguestfs-test-tool: failed...