[opensuse] qemu guest network bridged
Is there a simple way to get a bridged network for the qemu guest? From what I have read this should work: qemu-system-x86_64 -machine pc VirtualBox\ VMs/debian/debian.vdi -boot c -enable-kvm -m 1024 -nic tap qemu-system-x86_64: could not configure /dev/net/tun: Operation not permitted Other things I have tried allow me to start the machine but there is no networking. I have tried both wired and wireless on the host (and in fact at the moment I have both, I am not sure how that works). I normally use virtual box but it doesn't seem to work with kernel 5, which I am using to get around a problem with suspend on kernel 4. :/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Is there a simple way to get a bridged network for the qemu guest? From what I have read this should work:
qemu-system-x86_64 -machine pc VirtualBox\ VMs/debian/debian.vdi -boot c -enable-kvm -m 1024 -nic tap qemu-system-x86_64: could not configure /dev/net/tun: Operation not permitted
Other things I have tried allow me to start the machine but there is no networking.
I have tried both wired and wireless on the host (and in fact at the moment I have both, I am not sure how that works).
I normally use virtual box but it doesn't seem to work with kernel 5, which I am using to get around a problem with suspend on kernel 4. :/
I am running VirtualBox on a 5.3.0 kernel in Ubuntu19.10. Works no problem (vb6.1.2 downloaded from virtualbox.org site).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Is there a simple way to get a bridged network for the qemu guest? From what I have read this should work:
qemu-system-x86_64 -machine pc VirtualBox\ VMs/debian/debian.vdi -boot c -enable-kvm -m 1024 -nic tap qemu-system-x86_64: could not configure /dev/net/tun: Operation not permitted
Other things I have tried allow me to start the machine but there is no networking.
I have tried both wired and wireless on the host (and in fact at the moment I have both, I am not sure how that works).
I normally use virtual box but it doesn't seem to work with kernel 5, which I am using to get around a problem with suspend on kernel 4. :/ I am running VirtualBox on a 5.3.0 kernel in Ubuntu19.10. Works no problem (vb6.1.2 downloaded from virtualbox.org site). I think there are some complications here, as I have obtained kernel 5 from Tumbleweed, though I am on Leap, in order to check whether it fixes
ldb@braha.nl wrote: the suspend problem. But I would like to find out how to get qemu working.
Hi richmond, Am 28.01.20 um 15:21 schrieb Richmond:
Is there a simple way to get a bridged network for the qemu guest? From what I have read this should work:
qemu-system-x86_64 -machine pc VirtualBox\ VMs/debian/debian.vdi -boot c -enable-kvm -m 1024 -nic tap qemu-system-x86_64: could not configure /dev/net/tun: Operation not permitted
Other things I have tried allow me to start the machine but there is no networking.
I have tried both wired and wireless on the host (and in fact at the moment I have both, I am not sure how that works).
I normally use virtual box but it doesn't seem to work with kernel 5, which I am using to get around a problem with suspend on kernel 4. :/
i have had a year in past same problem, with the direct commandline. (on much older versions of qemu i used always commandline successfully) but on tumbleweed i never managed it. most easy way is to use virt-manager 1) make a bridge device in yast network and put your hardware network card to the bridge 2) install and run virt-manager 3) inside the graphical tool, you could now select your image. and use the bridge. thats it. 4) if network its not going through, for testpurpose switch off firewall, it will block your connections. i know a dirty work around for this problem. (better tell me your solution :-)) or ask again. and by the way, if you loose connection from the whole machine when going over the bridge, another not good solution is for this to edit /usr/lib/systemd/network/99-default.link MACAddressPolicy=none (needed if your network is filtered by known mac adresses.) (you will loose it every systemupdate) here one of my, from virt manager generated commandline (i think its complex :-(((((((( : ) 4717 ? Sl 36:17 /usr/bin/qemu-system-x86_64 -name guest=suse1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-suse1/master-key.aes -machine pc-i440fx-2.12,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu EPYC-IBPB,x2apic=on,tsc-deadline=on,hypervisor=on,tsc-adjust=on,arch-capabilities=on,cmp-legacy=on,perfctr-core=on,virt-ssbd=on,skip-l1dfl-vmentry=on,monitor=off -m 1024 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid bbbf5cf7-58ae-45ab-b8f2-faef9b62bfee -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=33,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -blockdev {"driver":"file","filename":"/home/simon/kvm/images/suse.img","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null} -device ide-hd,bus=ide.0,unit=0,drive=libvirt-1-format,id=ide0-0-0,bootindex=1 -netdev tap,fd=35,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:12:35:57,bus=pci.0,addr=0x3 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input2,bus=usb.0,port=1 -spice port=5901,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -object rng-random,id=objrng0,filename=/dev/urandom -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x9 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on if you find a easy way for a commandline, you are welcome to tell me :-)) simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
28.01.2020 17:21, Richmond пишет:
Is there a simple way to get a bridged network for the qemu guest? From what I have read this should work:
qemu-system-x86_64 -machine pc VirtualBox\ VMs/debian/debian.vdi -boot c -enable-kvm -m 1024 -nic tap qemu-system-x86_64: could not configure /dev/net/tun: Operation not permitted
If you are running as unprivileged user, you need to use bridge helper to setup interfaces for you.
Other things I have tried allow me to start the machine but there is no networking.
I have tried both wired and wireless on the host (and in fact at the moment I have both, I am not sure how that works).
I normally use virtual box but it doesn't seem to work with kernel 5, which I am using to get around a problem with suspend on kernel 4. :/
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Andrei Borzenkov
-
ldb@braha.nl
-
Richmond
-
Simon Becherer