diff options
| author | Greg Kurz | 2014-06-24 19:55:03 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin | 2014-06-29 18:39:43 +0200 |
| commit | 371df9f5e0f175a1d8f2e9f2e86cf65f952b1c56 (patch) | |
| tree | ddfbe5ebe5e121ad8d5d10231a8a7f9e734c0658 /tests | |
| parent | target-ppc: enable virtio endian ambivalent support (diff) | |
| download | qemu-371df9f5e0f175a1d8f2e9f2e86cf65f952b1c56.tar.gz qemu-371df9f5e0f175a1d8f2e9f2e86cf65f952b1c56.tar.xz qemu-371df9f5e0f175a1d8f2e9f2e86cf65f952b1c56.zip | |
vhost-net: disable when cross-endian
As of today, vhost assumes guest and host have the same endianness.
This is definitely not compatible with modern PPC64 and ARM that
can change endianness at runtime. Let's disable vhost-net and print
an error message when we detect such a case:
qemu-system-ppc64: vhost-net does not support cross-endian
qemu-system-ppc64: unable to start vhost net: 38: falling back on userspace virtio
This way users can continue to run VMs without changing their setup and
have a chance to know that performance will be impacted.
Suggested-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions