qemu-raspbian-network icon indicating copy to clipboard operation
qemu-raspbian-network copied to clipboard

Message need tun module at startup what to do?

Open johncblacker opened this issue 4 years ago • 2 comments

I'm getting "need tun module" at startup of the vm...I've tried everything I can to get things to work but no way. I did an "ip address show" command and I see a tap0 "tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 02:4d:40:9a:79:99 brd ff:ff:ff:ff:ff:ff But I need some help getting this script to run. lsmod | grep tun shows nothing; but I can do modprobe tun without error. Maybe I need to reboot? I'll try that.

johncblacker avatar Sep 06 '21 16:09 johncblacker

Reboot helped, I think. Here's what I get after starting script. obla@jobla-VirtualBox:~/qemu-buster/qemu-raspbian-network$ sudo ./qemu-pi.sh 2021-05-07-raspios-buster-armhf-lite.img need tun module mount: tmpmnt: overlapping loop device exists for /home/jobla/qemu-buster/qemu-raspbian-network/2021-05-07-raspios-buster-armhf-lite.img. ./qemu-pi.sh: line 123: tmpmnt/etc/udev/rules.d/90-qemu.rules: No such file or directory umount: tmpmnt: not mounted. ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave alsa: Could not initialize DAC alsa: Failed to open default': alsa: Reason: Device or resource busy ALSA lib pcm_dmix.c:1089:(snd_pcm_dmix_open) unable to open slave alsa: Could not initialize DAC alsa: Failed to open default': alsa: Reason: Device or resource busy audio: Failed to create voice `lm4549.out' *************** end of output *************************** Nothing appears to be happening on the QEMU window.

johncblacker avatar Sep 06 '21 17:09 johncblacker

Well, update...I was trying to use a "buster" image along with it's kernel module and apparently it won't work; so I downloaded the "jessie 2017-01-11" image that you "tested" with and it comes up! Now, the network address in the pi system is 10.0.2.15 and I was successful pinging www.google.com. However, how can I get to the machine from outside the vm - I'm running a Ubuntu 20,04 host inside VBOX on windows 10 pro. I've configured my Ubuntu with a bridge adaptor and it's on the same network as my other devices in my home: 192.168.0.23/24 (e.g.) but I can't ping 10.0.2.15 from my Ubuntu VM...but I seem to recall somewhere I read that ping (ICMP) wouldn't work. So, maybe I could ssh to my qemu/pi guest??? Tried using putty/ssh to 10.0.2.15 and it just waits...and waits... Can you help?

johncblacker avatar Sep 06 '21 19:09 johncblacker