All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Hong-Hua.Yin@freescale.com" <Hong-Hua.Yin@freescale.com>,
	"david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>,
	"agraf@suse.de" <agraf@suse.de>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Li Zhang <zhlcindy@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QEMU: PCI bus name on PowerPC platforms
Date: Wed, 05 Mar 2014 22:43:55 +1100	[thread overview]
Message-ID: <53170DFB.5050005@ozlabs.ru> (raw)
In-Reply-To: <49b80c368134449bb2b9093204aef6b6@BL2PR03MB210.namprd03.prod.outlook.com>

On 03/05/2014 09:42 PM, Hong-Hua.Yin@freescale.com wrote:
> Hi Gibson,
> 
> I noticed your patch http://git.qemu.org/?p=qemu.git;a=commitdiff;h=89dfd6e1
> and have some question about PCI bus name on PowerPC.
> 
> When I use libvirt to start VM on PowerPC platforms, it failed as below: 
> # virsh start sdk
> error: Failed to start domain sdk
> error: internal error: early end of file from monitor: possible problem:
> qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1: Bus 'pci' not found



I just tried current upstresm QEMU and it handles bus=pci fine, it prints
an error on bus=pci.0 so I am confused - what qemu are you trying?

I am adding our libvirt developer Li, she might help with this.


> Exactly it should be 'pci.0' according to the default qdev core logic.
> 
> But currently in libvirt it only recognize PCI bus name as 'pci.0' on x86_64/i686 Arch.
> -------------------------------------------------------------------
> libvirt/src/qemu/qemu_capabilities.c
>     /* Currently only x86_64 and i686 support PCI-multibus. */
>     if (qemuCaps->arch == VIR_ARCH_X86_64 ||
>         qemuCaps->arch == VIR_ARCH_I686) {
>         virQEMUCapsSet(qemuCaps, QEMU_CAPS_PCI_MULTIBUS);
> 
> libvirt/src/qemu/qemu_capabilities.h:
>     QEMU_CAPS_PCI_MULTIBUS       = 52, /* bus=pci.0 vs bus=pci */
> -------------------------------------------------------------------
>
> Looking at 'info qtree' output it seems "pseries" is the only PPC machine type 
> using "pci" (out of those we managed to run):
> 
> $ ./ppc64-softmmu/qemu-system-ppc64 -M ?
> Supported machines are:
> virtex-ml507         Xilinx Virtex ML507 reference design
> pseries              pSeries Logical Partition (PAPR compliant) (default)
> prep                 PowerPC PREP platform
> bamboo               bamboo
> ref405ep             ref405ep
> taihu                taihu
> mpc8544ds            mpc8544ds
> g3beige              Heathrow based PowerMAC
> mac99                Mac99 based PowerMAC
> ppce500              generic paravirt e500 platform
> none                 empty machine
> 
> 1) virtex-ml507
> 2) pseries
> Warning: Disabling some instructions which are not emulated by TCG (0x0, 0x4)
>     bus: pci
> 3) prep
>     bus: pci.0
> 4) bamboo
>     bus: pci.0
> 5) ref405ep
> qemu-system-ppc64: Could not load PowerPC BIOS 'ppc405_rom.bin'
> 6) taihu
> qemu-system-ppc64: Could not load PowerPC BIOS 'ppc405_rom.bin'
> 7) mpc8544ds
>     bus: pci.0
> 8) g3beige
>     bus: pci.0
> 9) mac99
>     bus: pci.0
> 10) ppce500
>     bus: pci.0
> 
> 
> Could pseries also use 'pci.0' as PCI bus name? 
> If yes, could we set QEMU_CAPS_PCI_MULTIBUS in libvirt for all the 
> PowerPC platforms? Otherwise, we need detect the machine to fix this issue.
> 
> The discussion in libvirt mailing list is here:
> https://www.redhat.com/archives/libvir-list/2014-March/msg00228.html
> 
> I think we need reach an agreement in QEMU and then work on libvirt.
	>
> Best Regards,
> Olivia
> 


-- 
Alexey

  reply	other threads:[~2014-03-05 11:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 10:42 [Qemu-devel] QEMU: PCI bus name on PowerPC platforms Hong-Hua.Yin
2014-03-05 11:43 ` Alexey Kardashevskiy [this message]
2014-03-05 13:35   ` Paolo Bonzini
2014-03-05 13:40     ` Daniel P. Berrange
2014-03-05 14:12       ` Paolo Bonzini
2014-03-05 14:21         ` Daniel P. Berrange
2014-03-05 14:33           ` Paolo Bonzini
2014-03-05 14:40             ` Daniel P. Berrange
2014-04-10  9:24             ` Daniel P. Berrange
2014-04-11 11:40               ` Alexey Kardashevskiy
2014-04-11 12:27                 ` Eric Blake
2014-04-11 12:29                   ` Alexander Graf
2014-03-05 14:35           ` Andreas Färber
2014-03-05 14:38             ` Andreas Färber
2014-03-05 14:44               ` Paolo Bonzini
2014-03-05 15:15     ` Alexey Kardashevskiy
2014-03-06  2:25       ` Hong-Hua.Yin
2014-03-06  7:04       ` Hong-Hua.Yin
2014-03-06  7:07         ` Alexey Kardashevskiy
2014-03-06  7:21           ` Hong-Hua.Yin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53170DFB.5050005@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=Hong-Hua.Yin@freescale.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=zhlcindy@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.