From: Kevin Zhao <kevin.zhao@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>, qemu-arm <qemu-arm@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Hanson <thomas.hanson@linaro.org>,
Gema Gomez-Solano <gema.gomez-solano@linaro.org>
Subject: [Qemu-devel] Help: Does Qemu support virtio-pci for net-device and disk device?
Date: Wed, 17 Aug 2016 20:08:11 +0800 [thread overview]
Message-ID: <CAN76PtR4dBm8DgTMGE73zSN1aYzbYY-ohnAveUbm_XQmWKm+bQ@mail.gmail.com> (raw)
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
AArch64. For virtio , the default address is virtio-mmio. After Libvirt
1.3.5, user can explicitly specify the address-type to pci and so libvirt
will pass the virtio-pci parameters to the Qemu.
Both my host and guest OS is Debian8, and Qemu version is 2.6.0.
Libvirt version is 1.3.5.
For net-device, I change the address-type to pci, and libvirt pass the
command below:
-device
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:0d:25:25,bus=pci.2,addr=0x1
After booting, the eth0 device disappear(eth0 occur when the address
is virtio-mmio),
but I can find another net-device enp2s1, also it can't work for dhcp:
Running lspci: 02:01.0 Ethernet controller: Red Hat, Inc Virtio network
device
I'm not sure whether it worked.
For disk device,* when I change the address-type to pci, the whole
qemu command is :*
https://paste.fedoraproject.org/409553/, but the VM can not boot
successfully. Does Qemu not support device disk of virtio-pci in AArch64
just as it in X86_64?
Thanks~Since I am not very familiar with Qemu, really looking forward
to your response.
Best Regards,
Kevin Zhao
next reply other threads:[~2016-08-17 12:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 12:08 Kevin Zhao [this message]
2016-08-17 16:13 ` [Qemu-devel] Help: Does Qemu support virtio-pci for net-device and disk device? Andrew Jones
2016-08-17 16:41 ` Andrea Bolognani
2016-08-18 6:38 ` Andrew Jones
2016-08-19 15:43 ` Andrea Bolognani
2016-08-19 17:51 ` Laine Stump
2016-08-17 17:00 ` Laine Stump
2016-08-18 7:41 ` Andrew Jones
2016-08-18 21:11 ` Laine Stump
2016-08-18 12:10 ` Marcel Apfelbaum
2016-08-18 21:20 ` Laine Stump
2016-08-18 12:43 ` Kevin Zhao
2016-08-18 13:51 ` Andrea Bolognani
2016-08-24 1:52 ` Kevin Zhao
2016-09-08 6:50 ` Kevin Zhao
2016-08-18 21:26 ` Laine Stump
2016-08-18 12:30 ` Kevin Zhao
2016-08-18 12:51 ` 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=CAN76PtR4dBm8DgTMGE73zSN1aYzbYY-ohnAveUbm_XQmWKm+bQ@mail.gmail.com \
--to=kevin.zhao@linaro.org \
--cc=gema.gomez-solano@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thomas.hanson@linaro.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).