ok, I managed to access your xml file via the mailing list archives.
So, it does look correct in terms of virtio-net. One thing of note is that kvm
guests can't transmit or recieve packets in parallel, since virtio-net only has
one TX and RX queue. This tends to reduce performance on W
I'm assuming the para-virtualized network driver is probably not being used
either based on the template.
If you take a close look at the xml for the interface, you should be able to
confirm that or not.
The templates tend to package all the para-virtualized drivers together, so
they're normall
Will give that a try. I'm curious why you think changing the disk drivers
over to virtio will have an effect on the network throughput.
- Steve
On Fri, Jul 1, 2022 at 10:55 AM Simon Weller
wrote:
> Unfortunately, I can't open the xml via the mailing list, but based on the
> template you're usin
So there’s no way to change that?
> On Thursday, Jun 30, 2022 at 11:37 PM, Wei ZHOU (mailto:ustcweiz...@gmail.com)> wrote:
> Hi Jeremy,
>
> Yes, threads is set to always 1.
>
> -Wei
>
> On Fri, 1 Jul 2022 at 06:46, Jeremy Hansen
> wrote:
>
> > So I was able to figure out how to specify cpu model
Unfortunately, I can't open the xml via the mailing list, but based on the
template you're using, it's not setup for Virtio-blk or virtio-scsi. Change the
template to Virtio-SCSI 64bit and the correct interface drive type will be
specified in the XML.
From: S.Fu
