Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
However, after I am closing qemu tap0 interface goes down with its ip address removed from ip table, so instead of calling script above one time, I have to pass it as argument.
I wonder why so? How can I create persistent (at least till next reboot) tap interface for qemu? Qemu even doesn't have rights to change OS network settings, so it seems that OS itself switches off tap device.
My current OS is Debian Jessie.
Because, for persistent changes you must edit /etc/network/interfaces. And probably disable network-manager. Explained here: https://wiki.debian.org/QEMU.
This device is not managed by network manager I guess
Code:
sudo nmcli dev status
eth0 ethernet connected Wired connection 2
eth1 ethernet disconnected --
wlan0 wifi disconnected --
lo loopback unmanaged --
tap0 tap unmanaged --
I also added lines below to /etc/network/interfaces and this didn't help, maybe I forgot to add something
Code:
allow-hotplug tap0
iface tap0 inet manual
pre-up ip tuntap add tap0 mode tap user root
pre-up ip addr add 192.168.1.1/24 dev tap0
up ip link set dev tap0 up
How about following that wiki article step by step? Did you install bridge-utils package? And then change your configuration to match that on the wiki.
Maybe I am missing something from the wiki but I do not need and even do not want bridge or VDE, and can't see how repeating steps with bridge will help. And letting qemu to my company's network will be super bad and unwanted step, I need local network between qemu and host.
Without bridging, you can not do it like that, or at least I do not know how. Perhaps if you add some settings into the /etc/qemu-ifup, but not sure about it. You could do it with bridging, but without connecting your network device ( eth0 for example ) to the bridge. That should allow connection within host and guests connected to the bridge, but guests will not be able to see outside of that "localized" network.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.