[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] qemu with vde not working

From: Tim Tassonis
Subject: [Qemu-devel] qemu with vde not working
Date: Thu, 12 Mar 2015 20:13:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0

Hi all

I have tried now for two days to get qemu 2.2.0 or 2.2.1 working with vde and just seem to get absolutely nowhere. On my old server (Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-77-generic x86_64)) it is working flawlessly, having a self compiled 2.2.0 version with the distros vde packages:

- libvde0               2.2.3-3build2
- libvdeplug2           2.2.3-3build2
- libvdeplug2-dev       2.2.3-3build2
- vde2                  2.2.3-3build2

The machine I'm testing on now is:
- Linux 3.19.1 OR Linux 3.2.0-76-generic copied from the old server
- vde2 2.3.2 OR svn 587 OR 2.2.3 copied from the old server
- gcc 4.9.1
- binutils 2.24
- qemu 2.2.0 or 2.2.1, compiled with:

./configure --prefix=/usr --enable-virtfs --sysconfdir=/etc \
            --disable-sdl  --disable-gtk --enable-vnc \
            --audio-drv-list=oss  --disable-vnc-sasl \
            --enable-kvm  --disable-smartcard-nss  --enable-vde \

I have setup the tap/vde network the usual, documented way, like on the old, working server:

# DHCP_RANGE=",,,,8h"
# modprobe kvm-intel
# modprobe tun
# vde_switch -tap tap0 -mod 660 -group kvm -s /var/run/qemu-vde.ctl \
             --pidfile /var/run/qemu-vde.pid -daemon
# ifconfig tap34 \
           inet \
           broadcast \
           netmask up
# sysctl -w net.ipv4.ip_forward=1
# iptables -t nat -A POSTROUTING -s -j MASQUERADE
# dnsmasq --log-queries \
          --user=dnsmasq \
          --dhcp-leasefile=/var/lib/misc/qemu-dhcpd.leases \
          --dhcp-range="$DHCP_RANGE" \
          --interface=tap34 \
          --domain=laconian-linux.org \

The tap interface is running fine, I can ping and also do an nslookup on it.

My virtual machine has a e1000 network card configured, it is running perfectly fine, the card is recognized and set up, but no networking. On the old server, the exact same qemu disk with the same startup parameters runs fine.

I started the virtual machine both with the old and the new options:


qemu-system-x86_64 -enable-kvm -m 1024 -boot c -hda sda \
     -netdev vde,sock=$VDE_SOCKET,group=kvm,mode=0660,id=vde0 \
     -device e1000,netdev=vde0,mac=52:54:00:12:34:84 \
     -vnc -k de-ch -vga std


qemu-system-x86_64 -enable-kvm -m 1024 -boot c -hda sda \
      -net nic,vlan=0,macaddr=52:54:00:12:34:84 \
      -net vde,sock=$VDE_SOCKET,group=kvm,mode=0660 \
      -vnc -k de-ch -vga std

When the virtual machine goes up and does the dhcp request, I even get those in the log:

dnsmasq-dhcp: DHCPDISCOVER(tap34) 52:54:00:12:34:84
dnsmasq-dhcp: DHCPOFFER(tap34) 52:54:00:12:34:84
dnsmasq-dhcp: DHCPDISCOVER(tap34) 52:54:00:12:34:84
dnsmasq-dhcp: DHCPOFFER(tap34) 52:54:00:12:34:84

Whe I look in the socket dir, there seems to be something strange:

# ls -la /var/run/qemu-vde.ctl/
total 0
drwxrws---  2 root   kvm  100 Mar 12 20:06 .
drwxrwxrwt 12 root   root 520 Mar 12 19:46 ..
srw-rw----  1 timtas kvm    0 Mar 12 20:06 002
srw-rw----  1 timtas kvm    0 Mar 12 20:06 .03869-00000
srw-rw----  1 root   kvm    0 Mar 12 19:46 ctl

On the working production machine, I get only one file, 002, but here I also always get this .03869-00000.

Can anybody point me to what I possibly do wrong, or to a patch that fixes that?

Kind regards

Below are the results of qemu ./configure, if that's of any interest.

python            python -B
smbd              /usr/sbin/smbd
module support    no
host CPU          x86_64
host big endian   no
target list       x86_64-softmmu i386-softmmu arm-softmmu
tcg debug enabled no
gprof enabled     no
sparse enabled    no
strip binaries    yes
profiler          no
static build      no
pixman            system
SDL support       no
GTK support       no
VTE support       no
curses support    yes
curl support      yes
mingw32 support   no
Audio drivers     oss
Block whitelist (rw)
Block whitelist (ro)
VirtFS support    yes
VNC support       yes
VNC TLS support   yes
VNC SASL support  no
VNC JPEG support  yes
VNC PNG support   yes
VNC WS support    yes
xen support       no
brlapi support    no
bluez  support    no
Documentation     yes
GUEST_BASE        yes
PIE               yes
vde support       yes
netmap support    no
Linux AIO support no
ATTR/XATTR support yes
Install blobs     yes
KVM support       yes
RDMA support      no
TCG interpreter   no
fdt support       yes
preadv support    yes
fdatasync         yes
madvise           yes
posix_madvise     yes
sigev_thread_id   yes
uuid support      yes
libcap-ng support no
vhost-net support yes
vhost-scsi support yes
Trace backends    nop
spice support     no
rbd support       no
xfsctl support    no
nss used          no
libusb            yes
usb net redir     no
GLX support       yes
libiscsi support  no
libnfs support    no
build guest agent yes
QGA VSS support   no
seccomp support   no
coroutine backend ucontext
coroutine pool    yes
GlusterFS support no
Archipelago support no
gcov              gcov
gcov enabled      no
TPM support       yes
libssh2 support   no
TPM passthrough   yes
QOM debugging     yes
vhdx              yes
Quorum            yes
lzo support       no
snappy support    no
NUMA host support no

reply via email to

[Prev in Thread] Current Thread [Next in Thread]