Hi Rich
I'm noe getting the below logs after running libguestfs-test-tool..
SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4
SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4
PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin
SELinux: sh: getenforce: command not found
guestfs_get_append: (null)
guestfs_get_autosync: 1
guestfs_get_backend: direct
guestfs_get_backend_settings: []
guestfs_get_cachedir: /var/tmp
guestfs_get_direct: 0
guestfs_get_hv: /usr/bin/kvm
guestfs_get_memsize: 768
guestfs_get_network: 0
guestfs_get_path: /usr/local/lib/guestfs
guestfs_get_pgroup: 0
guestfs_get_program: libguestfs-test-tool
guestfs_get_recovery_proc: 1
guestfs_get_selinux: 0
guestfs_get_smp: 1
guestfs_get_tmpdir: /tmp
guestfs_get_trace: 0
guestfs_get_verbose: 1
host_cpu: powerpc64
Launching appliance, timeout set to 600 seconds.
libguestfs: launch: program=libguestfs-test-tool
libguestfs: launch: version=1.26.1
libguestfs: launch: backend registered: unix
libguestfs: launch: backend registered: uml
libguestfs: launch: backend registered: direct
libguestfs: launch: backend=direct
libguestfs: launch: tmpdir=/tmp/libguestfskd0ua4
libguestfs: launch: umask=0002
libguestfs: launch: euid=1000
libguestfs: [00000ms] begin building supermin appliance
libguestfs: [00000ms] run supermin
libguestfs: command: run: /usr/bin/supermin
libguestfs: command: run: \ --build
libguestfs: command: run: \ --verbose
libguestfs: command: run: \ --if-newer
libguestfs: command: run: \ --lock /var/tmp/.guestfs-1000/lock
libguestfs: command: run: \ --copy-kernel
libguestfs: command: run: \ -f ext2
libguestfs: command: run: \ --host-cpu powerpc64
libguestfs: command: run: \ /usr/local/lib/guestfs/supermin.d
libguestfs: command: run: \ -o /var/tmp/.guestfs-1000/appliance.d
supermin: version: 5.1.8
supermin: package handler: debian/dpkg
supermin: acquiring lock on /var/tmp/.guestfs-1000/lock
supermin: if-newer: output does not need rebuilding
libguestfs: [00014ms] finished building supermin appliance
libguestfs: [00014ms] begin testing qemu features
libguestfs: command: run: /usr/bin/kvm
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -help
libguestfs: command: run: /usr/bin/kvm
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -version
libguestfs: qemu version 2.0
libguestfs: command: run: /usr/bin/kvm
libguestfs: command: run: \ -display none
libguestfs: command: run: \ -machine accel=kvm:tcg
libguestfs: command: run: \ -device ?
libguestfs: [00377ms] finished testing qemu features
[00378ms] /usr/bin/kvm \
-global virtio-blk-pci.scsi=off \
-nodefconfig \
-enable-fips \
-nodefaults \
-display none \
-M pseries \
-machine accel=kvm:tcg \
-m 768 \
-no-reboot \
-rtc driftfix=slew \
-global kvm-pit.lost_tick_policy=discard \
-kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
-initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
-device virtio-scsi-pci,id=scsi \
-drive
file=/tmp/libguestfskd0ua4/scratch.1,cache=unsafe,format=raw,id=hd0,if=none
\
-device scsi-hd,drive=hd0 \
-drive
file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none
\
-device scsi-hd,drive=appliance \
-device virtio-serial-pci \
-serial stdio \
-chardev socket,path=/tmp/libguestfskd0ua4/guestfsd.sock,id=channel0 \
-device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
-append 'panic=1 console=ttyS0 udevtimeout=600 no_timer_check acpi=off
printk.time=1 cgroup_disable=memory root=/dev/sdb selinux=0
guestfs_verbose=1 TERM=xterm'
kvm: -M pseries: Unsupported machine type
Use -machine help to list supported machines!
libguestfs: error: guestfs_launch failed, see earlier error messages
libguestfs-test-tool: failed to launch appliance
libguestfs: closing guestfs handle 0x10016848 (state 0)
libguestfs: command: run: rm
libguestfs: command: run: \ -rf /tmp/libguestfskd0ua4
The output of kvm machine help is as follows...
kvm -machine help
Supported machines are:
taihu taihu
mac99 Mac99 based PowerMAC
prep PowerPC PREP platform
g3beige Heathrow based PowerMAC (default)
bamboo bamboo
mpc8544ds mpc8544ds
ppce500 generic paravirt e500 platform
virtex-ml507 Xilinx Virtex ML507 reference design
none empty machine
ref405ep ref405ep
Can you help regarding this.
Thanks
On Wed, Jun 4, 2014 at 5:12 PM, abhishek jain <ashujain9727@gmail.com>
wrote:
> Hi Rich
>
> I'm able to solve this.
> I copied uImage to vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 and I'm now able
to
> proceed.
>
> Thanks a lot for the help despite being on vocations.:-)
>
>
>
> On Wed, Jun 4, 2014 at 4:38 PM, Richard W.M. Jones
<rjones@redhat.com>
> wrote:
>
>>
>>
>> On Wed, Jun 04, 2014 at 03:29:11PM +0530, abhishek jain wrote:
>> > supermin: kernel: SUPERMIN_KERNEL environment variable
/boot/uImage
>> > supermin: failed to find a suitable kernel (host_cpu=powerpc64).
>> >
>> > I looked for kernels in /boot and modules in /lib/modules.
>>
>> If you follow the code in src/kernel.ml you'll see that this means
>> supermin was unable to get the kernel version from the supplied kernel
>> file. The code is fairly simple to follow. I barely have internet
>> access here and in any case I don'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)
>> > libguestfs: command: run: rm
>> > libguestfs: command: run: \ -rf /tmp/libguestfsfPWXx0
>> >
>> >
>> >
>> > I think i need to enable virtio-serial in my kernel.
>> > I'll you let you know the result after enabling virtio-seriel
in the
>> kernel
>> > inn 5-10 min.
>> > Well sorry to disturb you on vocations.:-(
>> >
>> > Thanks
>> >
>> >
>> > On Wed, Jun 4, 2014 at 2:49 PM, Richard W.M. Jones
<rjones@redhat.com>
>> > wrote:
>> >
>> > > 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 07:21
>> 3.8.13-rt9-QorIQ-SDK-V1.4
>> > > >
>> > > >
>> > > > uname -a
>> > > > Linux t4240-ubuntu1310 3.8.13-rt9-QorIQ-SDK-V1.4 #10 SMP
Tue May 27
>> > > > 10:48:24 IST 2014 ppc64 ppc64 ppc64 GNU/Linux
>> > >
>> > > Well, assuming the modules directory matches the kernel
(uImage)
>> > > you could try:
>> > >
>> > > export SUPERMIN_KERNEL=/boot/uImage
>> > > export
SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4
>> > >
>> > > Are these homebrew kernels? I'm surprised that an
official Ubuntu
>> > > ppc kernel would have such a non-standard name. Anyway, if
homebrew
>> > > you'll also need to ensure the kernel supports all the
usual virtio
>> > > devices (especially virtio-serial, which is required by
libguestfs).
>> > >
>> > > Rich.
>> > >
>> > > --
>> > > Richard Jones, Virtualization Group, Red Hat
>> > > http://people.redhat.com/~rjones
>> > > Read my programming and virtualization blog:
>> http://rwmj.wordpress.com
>> > > virt-top is 'top' for virtual machines. Tiny program
with many
>> > > powerful monitoring features, net stats, disk stats, logging,
etc.
>> > > http://people.redhat.com/~rjones/virt-top
>> > >
>>
>> --
>> Richard Jones, Virtualization Group, Red Hat
>> http://people.redhat.com/~rjones
>> Read my programming and virtualization blog: http://rwmj.wordpress.com
>> virt-builder quickly builds VMs from scratch
>> http://libguestfs.org/virt-builder.1.html
>>
>
>