qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gonglei <arei.gonglei@huawei.com>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] q35 : virtio-serial on pci bridge : bus not found
Date: Tue, 12 Aug 2014 20:09:26 +0800	[thread overview]
Message-ID: <53EA03F6.6070203@huawei.com> (raw)
In-Reply-To: <35b2ecf1-2df8-403c-82c9-ba6751846089@mailpro>

On 2014/8/12 18:51, Alexandre DERUMIER wrote:

> Hi, I can't use virtio-serial, with q35 machine, on a pci bridge (other devices works fine).
> 
> 
> Is it a known bug ?
> 

No, you should lay 'kvm: -device virtio-serial,id=spice,bus=pci.0' before
"-readconfig /usr/share/qemu-server/pve-q35.cfg",which can assure
the bus pci.0 has been created.

Best regards,
-Gonglei

> 
> error message:
> ---------------
> kvm: -device virtio-serial,id=spice,bus=pci.0,addr=0x9: Bus 'pci.0' not found
> 
> 
> architecture is:
> 
> pcie.0
>    --->pcidmi (i82801b11-bridge)
>          ------->pci.0 (pci-bridge)
> 
> 
> 
> /usr/bin/kvm -id 600 -chardev socket,id=qmp,path=/var/run/qemu-server/600.qmp,server,nowait 
> -mon chardev=qmp,mode=control -vnc unix:/var/run/qemu-server/600.vnc,x509,password
> -pidfile /var/run/qemu-server/600.pid -daemonize -name tankrechner -smp sockets=1,cores=1 
> -nodefaults -boot menu=on -vga qxl -cpu kvm64,+lahf_lm,+x2apic,+sep
> -spice tls-port=61002,addr=127.0.0.1,tls-ciphers=DES-CBC3-SHA,seamless-migration=on
> -device virtio-serial,id=spice,bus=pci.0,addr=0x9 
> -chardev spicevmc,id=vdagent,name=vdagent 
> -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 
> -m 1024 
> -readconfig /usr/share/qemu-server/pve-q35.cfg
> -device piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2 
> -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 
> -drive if=none,id=drive-ide2,media=cdrom,aio=native 
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200 
> -drive file=/mnt/vmfs-hdd-r5_3x698/images/600/vm-600-disk-1.raw,if=none,id=drive-virtio0,format=raw,aio=native,cache=none
> -device virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100
> -netdev type=tap,id=net0,ifname=tap600i0,script=/var/lib/qemu-server/pve-bridge,vhost=on
> -device virtio-net-pci,mac=EA:07:3A:31:12:7F,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300
> -rtc driftfix=slew,base=localtime 
> -machine type=q35
> 
> 
> with pve-q35.cfg
> 
> [device "ehci"]
>   driver = "ich9-usb-ehci1"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1d.7"
> 
> [device "uhci-1"]
>   driver = "ich9-usb-uhci1"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1d.0"
>   masterbus = "ehci.0"
>   firstport = "0"
> 
> [device "uhci-2"]
>   driver = "ich9-usb-uhci2"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1d.1"
>   masterbus = "ehci.0"
>   firstport = "2"
> 
> [device "uhci-3"]
>   driver = "ich9-usb-uhci3"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1d.2"
>   masterbus = "ehci.0"
>   firstport = "4"
> 
> [device "ehci-2"]
>   driver = "ich9-usb-ehci2"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1a.7"
> 
> [device "uhci-4"]
>   driver = "ich9-usb-uhci4"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1a.0"
>   masterbus = "ehci-2.0"
>   firstport = "0"
> 
> [device "uhci-5"]
>   driver = "ich9-usb-uhci5"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1a.1"
>   masterbus = "ehci-2.0"
>   firstport = "2"
> 
> [device "uhci-6"]
>   driver = "ich9-usb-uhci6"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1a.2"
>   masterbus = "ehci-2.0"
>   firstport = "4"
> 
> [device "audio0"]
>   driver = "ich9-intel-hda"
>   bus = "pcie.0"
>   addr = "1b.0"
> 
> 
> [device "ich9-pcie-port-1"]
>   driver = "ioh3420"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1c.0"
>   port = "1"
>   chassis = "1"
> 
> [device "ich9-pcie-port-2"]
>   driver = "ioh3420"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1c.1"
>   port = "2"
>   chassis = "2"
> 
> [device "ich9-pcie-port-3"]
>   driver = "ioh3420"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1c.2"
>   port = "3"
>   chassis = "3"
> 
> [device "ich9-pcie-port-4"]
>   driver = "ioh3420"
>   multifunction = "on"
>   bus = "pcie.0"
>   addr = "1c.3"
>   port = "4"
>   chassis = "4"
> [device "pcidmi"}
>   driver = "i82801b11-bridge"
>   bus = "pcie.0"
>   addr = "1e.0"
> 
> [device "pci.0"]
>   driver = "pci-bridge"
>   bus = "pcidmi"
>   addr = "1.0"
>   chassis_nr = "1"
> 
> [device "pci.1"]
>   driver = "pci-bridge"
>   bus = "pcidmi"
>   addr = "2.0"
>   chassis_nr = "2"
> 
> [device "pci.2"]
>   driver = "pci-bridge"
>   bus = "pcidmi"
>   addr = "3.0"
>   chassis_nr = "3"
> 
> 

  parent reply	other threads:[~2014-08-12 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1667d146-c97c-41a9-ab77-eeef7e986d5c@mailpro>
2014-08-12 10:51 ` [Qemu-devel] q35 : virtio-serial on pci bridge : bus not found Alexandre DERUMIER
2014-08-12 11:20   ` Alexandre DERUMIER
2014-08-12 12:09   ` Gonglei [this message]
2014-08-12 22:57     ` Alexandre DERUMIER

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=53EA03F6.6070203@huawei.com \
    --to=arei.gonglei@huawei.com \
    --cc=aderumier@odiso.com \
    --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).