error: Cannot check QEMU binary qemu-system-ppc: No such file or directory

Bug #1317987 reported by john.d@servergy.com
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Expired
Medium
Unassigned

Bug Description

trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system
Welcome to virsh, the virtualization interactive terminal.

Type: 'help' for help with commands
       'quit' to quit

virsh # define vm01.xml
error: Failed to define domain from vm01.xml
error: Cannot check QEMU binary qemu-system-ppc: No such file or directory

(trusty)root@jade-rev4:/home2/qemu#
(trusty)root@jade-rev4:/home2/qemu#
(trusty)root@jade-rev4:/home2/qemu# cat vm01.xml
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Ubuntu-VM01</name>
  <uuid>38bbffe5-47e9-4a3b-84b1-1af5ff3f7194</uuid>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='ppc' machine='ppce500'>hvm</type>
    <kernel>jade-kernel-2.0.bin</kernel>
    <initrd>jade-initrd-2.0.bin</initrd>
    <cmdline>console=ttyS0</cmdline>
  </os>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>destroy</on_reboot>
  <on_crash>destroy</on_crash>
  <devices>
    <emulator>qemu-system-ppc</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='jade-ubuntu-14.04.qcow2.netinstall'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <controller type='usb' index='0'/>
    <controller type='pci' index='0' model='pci-root'/>
    <memballoon model='virtio'/>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-no-shutdown'/>
  </qemu:commandline>
</domain>

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libvirt-bin 1.2.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-24.46-powerpc-e500mc 3.13.9
Uname: Linux 3.13.0-24-powerpc-e500mc ppc
ApportVersion: 2.14.1-0ubuntu3
Architecture: powerpc
CurrentDesktop: XFCE
Date: Fri May 9 12:06:14 2014
KernLog:

ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libvirt
UpgradeStatus: Upgraded to trusty on 2014-04-29 (10 days ago)
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf']

Revision history for this message
john.d@servergy.com (john-d-0) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1317987] [NEW] error: Cannot check QEMU binary qemu-system-ppc: No such file or directory

Thanks for submitting this bug. Can you confirm whether
the qemu-system-ppc package is installed? Please show the
results of

 dpkg -l | grep qemu-system-ppc
 dpkg -l | grep openbios-ppc

 status: incomplete
 importance: medium

Changed in libvirt (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
john.d@servergy.com (john-d-0) wrote :

Hi,

(trusty)root@jade-rev4:/home2/qemu# dpkg -l | egrep "qemu-system-pcc|openb"
ii netcat-openbsd 1.105-7ubuntu1 powerpc TCP/IP swiss army knife
ii openbios-ppc 1.1-1ubuntu1 all PowerPC Open Firmware
ii openbsd-inetd 0.20091229-2ubuntu3 powerpc OpenBSD Internet Superserver
(trusty)root@jade-rev4:/home2/qemu#

I can run a vm manually :

(trusty)root@jade-rev4:/home2/qemu# cat go3.sh
exec qemu-system-ppc -M ppce500 -nographic -kernel jade-kernel.bin \
                -initrd jade-initrd-2.0.bin -m 1G -enable-kvm -drive \
         file=jade-ubuntu-14.04.qcow2,if=virtio -append "console=ttyS0 syboot=break" \
         -no-shutdown -no-reboot -name Ubuntu-$$

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1317987] Re: error: Cannot check QEMU binary qemu-system-ppc: No such file or directory

Quoting <email address hidden> (<email address hidden>):
> Hi,
>
> (trusty)root@jade-rev4:/home2/qemu# dpkg -l | egrep "qemu-system-pcc|openb"

Just to make sure, could you replace qemu-system-pcc with qemu-system-ppc? Since
you say below that you can run it I assume that'll show the right thing.

Revision history for this message
john.d@servergy.com (john-d-0) wrote :

Here you go

(trusty)root@jade-rev4:/home2/qemu# dpkg -l | egrep "qemu-system-ppc|openbio"
ii openbios-ppc 1.1-1ubuntu1 all PowerPC Open Firmware
ii qemu-system-ppc 2.0.0~rc1+dfsg-0ubuntu3.1 powerpc QEMU full system emulation binaries (ppc)

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

thanks. If I take your vm1.xml and specify a full path, so

<emulator>/usr/bin/qemu-system-ppc</emulator>

then virsh define is happy. Please let us know if that still doesn't work for you.

Revision history for this message
john.d@servergy.com (john-d-0) wrote :

Hi
 I do get further with full pathnames for the kernel,initrd, and disk image; However there are issues with
the xml file that was generated from the args file:

(trusty)root@jade-rev4:/home2/qemu# cat go14.04.args
qemu-system-ppc -M ppce500 -nographic -kernel /home2/qemu/jade-kernel-2.0.bin -initrd /home2/qemu/jade-initrd-2.0.bin -m 1024 -enable-kvm -drive file=/home2/qemu/jade-ubuntu-14.04.qcow2.netinstall,if=virtio -append "console=ttyS0" -no-shutdown -no-reboot -name Ubuntu-VM01

(trusty)root@jade-rev4:/home2/qemu#

virsh domxml-from-native qemu-argv go14.04.args > vm01.xml

(trusty)root@jade-rev4:/home2/qemu# virsh -c qemu:///system
Welcome to virsh, the virtualization interactive terminal.

Type: 'help' for help with commands
       'quit' to quit

virsh # define vm01.xml
Domain Ubuntu-VM01 defined from vm01.xml

virsh # start Ubuntu-VM01
error: Failed to start domain Ubuntu-VM01
error: internal error: early end of file from monitor: possible problem:
Can't open directory /proc/device-tree/cpus/
qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found

virsh # exit

(trusty)root@jade-rev4:/home2/qemu# ls /proc/device-tree/
#address-cells dcsr@f00000000 name
aliases fsl,dpaa pcie@ffe200000
bman-portals@ff4000000 interrupt-parent pcie@ffe201000
chosen localbus@ffe124000 qman-portals@ff4200000
compatible memory #size-cells
cpus model soc@ffe000000

(trusty)root@jade-rev4:/home2/qemu# ls /proc/device-tree/cpus
#address-cells PowerPC,e500mc@1 PowerPC,e500mc@4 PowerPC,e500mc@7
name PowerPC,e500mc@2 PowerPC,e500mc@5 #size-cells
PowerPC,e500mc@0 PowerPC,e500mc@3 PowerPC,e500mc@6

What is the root cause of the PCI config error ?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

You're still able to run the same vm by hand (as was the case in comment #3)?

What sort of host are you running on?

If you add '-L /usr/share/qemu', to your command line, does that help?

If instead of building your own kernel, you download a cdimage like http://cdimages.ubuntu.com/ubuntu-server/daily/current/utopic-server-powerpc.iso, and boot that, does that work for you?

Revision history for this message
john.d@servergy.com (john-d-0) wrote :

Hi;
I'll try your other images listed - if they are e500pc kernels (FreeScale P4080 SOC ) ; Our boot kernel is unique so far and is only used for boot IPL ;

Isn't this product suppose to work as well as Intel qemu + kvm ?

 I appreciate your help ; but these issues are related to out of box behavior ;

The PowerPC qemu ; qtemu related tools are no where near as full feature and functional as x86 ;

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I'm trying to determine (without the kernel and initrds to reproduce with) whether the issue is in upstream qemu or in libvirt. If you can still run qemu-system-ppc by hand just fine, then we need to figure out whether and why libvirt is doing something different so we can fix it.

Changed in libvirt (Ubuntu):
status: Incomplete → In Progress
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I believe this is fixed in wily. Can anyone confirm?

Changed in libvirt (Ubuntu):
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]

Changed in libvirt (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.