qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Kevin Zhao <kevin.zhao@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Question about a qemu Aarch64 error when adding several SCSI disks
Date: Fri, 24 Jun 2016 08:51:50 +0100	[thread overview]
Message-ID: <CAFEAcA82J89CWSQ7AFkTSLTjgKC+Qv-nus6eXkC3_pF2J6K5nw@mail.gmail.com> (raw)
In-Reply-To: <CAN76PtTSxkNDT+QQ3VicgyLC0LPYuo-7BaEp2AHkQXCfRLTUGg@mail.gmail.com>

On 24 June 2016 at 05:58, Kevin Zhao <kevin.zhao@linaro.org> wrote:
> Hi Peter,
>      Follow your advice, I have complied the Qemu v2.6.
> stack@u202158:~$ kvm --version
> QEMU emulator version 2.6.50 (v2.6.0-1280-g6f1d2d1-dirty), Copyright (c)
> 2003-2008 Fabrice Bellard
>      With this newest version, I use virt-manager to create the guest , the
> xml file is in the attachment. But the Qemu return error when creating:
>      error: internal error: process exited while connecting to monitor:
> qemu-system-aarch64: -device
> pci-bridge,chassis_nr=2,id=pci,bus=pci,addr=0x1: Duplicate ID 'pci' for
> device
>
>      The guest xml file in in attachment. But the XML worked when Qemu is
> v2.4.0.
>       Also I delete the items in the xml :
>   -  <controller type='pci' index='0' model='pcie-root'/>
>   -  <controller type='pci' index='1' model='dmi-to-pci-bridge'>
>   -    <model name='i82801b11-bridge'/>
>   -    <address type='pci' domain='0x0000' bus='0x00' slot='0x01'
> function='0x0'/>
>   -  </controller>
>   -  <controller type='pci' index='2' model='pci-bridge'>
>   -    <model name='pci-bridge'/>
>   -    <target chassisNr='2'/>
>   -    <address type='pci' domain='0x0000' bus='0x01' slot='0x01'
> function='0x0'/>
>   -  </controller>
>       Using virsh create guest.xml, got the error too :
>       error: internal error: process exited while connecting to monitor:
> qemu-system-aarch64: -device
> pci-bridge,chassis_nr=2,id=pci,bus=pci,addr=0x1: Duplicate ID 'pci' for
> device.

Sounds like maybe we just increased the error checking on
our command lines -- you can't have more than one device
with the same ID. I can't tell what the other device with the
same ID is, because this doesn't give all the command line.
If libvirt is generating invalid command lines, that would
be a libvirt bug.

thanks
-- PMM

  reply	other threads:[~2016-06-24  7:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 11:51 [Qemu-devel] Question about a qemu Aarch64 error when adding several SCSI disks Kevin Zhao
2016-06-22 12:04 ` Peter Maydell
2016-06-22 12:34   ` Kevin Zhao
2016-06-24  4:58     ` Kevin Zhao
2016-06-24  7:51       ` Peter Maydell [this message]
2016-06-24 11:35       ` Cole Robinson
2016-06-27 13:05         ` Kevin Zhao
2016-06-27 18:23           ` Cole Robinson
2016-06-28 13:34             ` Kevin Zhao
2016-06-22 12:08 ` Dr. David Alan Gilbert
2016-06-22 12:53   ` Kevin Zhao

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=CAFEAcA82J89CWSQ7AFkTSLTjgKC+Qv-nus6eXkC3_pF2J6K5nw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=kevin.zhao@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).