From: Maarten <1861875@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1861875] Re: VDE networking barely working
Date: Tue, 04 Feb 2020 14:40:33 -0000 [thread overview]
Message-ID: <158082723344.8247.14571828801571348763.launchpad@chaenomeles.canonical.com> (raw)
In-Reply-To: 158082639262.26675.4971489062247211077.malonedeb@soybean.canonical.com
** Description changed:
Running qemu with a vde_switch and slirpvde:
vde_switch -F -sock /tmp/qemu_vde_switch -M /tmp/qemu_vde_mgmt
slirpvde -s /tmp/qemu_vde_switch -dhcp
- qemu-system-x86_64 -m 2048 -smp 2 -serial mon:stdio -display none
- -vga none -nodefaults -accel hax
- -net nic,macaddr=52:54:00:0e:e0:61,model=virtio
- -net vde,sock=/tmp/qemu_vde_switch -device virtio-rng-pci
- -drive file=worker.qcow2,if=virtio
- -drive file=cloud-init.iso,format=raw,if=virtio
+ qemu-system-x86_64 -m 2048 -smp 2 -serial mon:stdio -display none -vga none -nodefaults -accel hax -net nic,macaddr=52:54:00:0e:e0:61,model=virtio -net vde,sock=/tmp/qemu_vde_switch -device virtio-rng-pci -drive file=worker.qcow2,if=virtio -drive file=cloud-init.iso,format=raw,if=virtio
There is some network connectivity, ping and curl work, but bigger
- transfers like apt-get update break with the following errors printed in
- the output of vde_switch:
+ transfers like apt-get update or iperf break with the following errors
+ printed in the output of vde_switch:
vde_switch: send_sockaddr port 2: No buffer space available
vde_switch: send_sockaddr port 2: No buffer space available
vde_switch: send_sockaddr port 2: No buffer space available
I've tried to change the MTU size and model of the adapter inside of the
VM, but nothing worked.
OS: macOS 10.15.2
qemu: 4.2.0
vde2 (vde_switch / slirpvde): 2.3.2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1861875
Title:
VDE networking barely working
Status in QEMU:
New
Bug description:
Running qemu with a vde_switch and slirpvde:
vde_switch -F -sock /tmp/qemu_vde_switch -M /tmp/qemu_vde_mgmt
slirpvde -s /tmp/qemu_vde_switch -dhcp
qemu-system-x86_64 -m 2048 -smp 2 -serial mon:stdio -display none -vga none -nodefaults -accel hax -net nic,macaddr=52:54:00:0e:e0:61,model=virtio -net vde,sock=/tmp/qemu_vde_switch -device virtio-rng-pci -drive file=worker.qcow2,if=virtio -drive file=cloud-init.iso,format=raw,if=virtio
There is some network connectivity, ping and curl work, but bigger
transfers like apt-get update or iperf break with the following errors
printed in the output of vde_switch:
vde_switch: send_sockaddr port 2: No buffer space available
vde_switch: send_sockaddr port 2: No buffer space available
vde_switch: send_sockaddr port 2: No buffer space available
I've tried to change the MTU size and model of the adapter inside of
the VM, but nothing worked.
OS: macOS 10.15.2
qemu: 4.2.0
vde2 (vde_switch / slirpvde): 2.3.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1861875/+subscriptions
next prev parent reply other threads:[~2020-02-04 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:26 [Bug 1861875] [NEW] VDE networking barely working Maarten
2020-02-04 14:40 ` Maarten [this message]
2021-05-05 15:21 ` [Bug 1861875] " Thomas Huth
2021-07-05 4:17 ` Launchpad Bug Tracker
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=158082723344.8247.14571828801571348763.launchpad@chaenomeles.canonical.com \
--to=1861875@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.