[Top][All Lists]

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

[Qemu-discuss] QEMU in ovs-dpdk network interface renamed

From: Roman Mashak
Subject: [Qemu-discuss] QEMU in ovs-dpdk network interface renamed
Date: Sun, 2 Nov 2014 11:54:22 -0500


I'm using ovs-dpdk from https://github.com/01org/dpdk-ovs the package
also includes qemu-1.6.2. I'm observing the following behaviour, which
I would like to clarify.

Qemu is launched:
% qemu-system-x86_64 -cpu host -boot c -hda my_image.qcow2 -snapshot
-m 1024 --enable-kvm -name vm0 -nographic -display curses -pidfile
/var/run/vm0.pid -mem-path /dev/hugepages -mem-prealloc -monitor
unix:/var/run/vm0monitor,server,nowait -net none -netdev

No warnings or errors, and I can login the VM afterwards. However it
seems that udev has renamed single network interface form eth0 to
eth1, here is a rule file automatically created at boot:

% cat /etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x1af4:0x1000 (virtio-pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:00:00:00:00:0
1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

Why would virtio-pci driver choose eth1 for the single interface in the system?

This does not happen if I run qemu without mac=.. option, ie. the MAC
address is qemu predefined 52:54:xxx but I want to provide the macs
via command line.

Is it a known issue or I'm doing something wrong?

Roman Mashak

reply via email to

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