diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 19:39:53 +0200 |
| commit | dee4dcba78baf712cab403d47d9db319ab7f95d6 (patch) | |
| tree | 418478faf06786701a56268672f73d6b0b4eb239 /results/classifier/111/network/1791680 | |
| parent | 4d9e26c0333abd39bdbd039dcdb30ed429c475ba (diff) | |
| download | emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.tar.gz emulator-bug-study-dee4dcba78baf712cab403d47d9db319ab7f95d6.zip | |
restructure results
Diffstat (limited to 'results/classifier/111/network/1791680')
| -rw-r--r-- | results/classifier/111/network/1791680 | 104 |
1 files changed, 0 insertions, 104 deletions
diff --git a/results/classifier/111/network/1791680 b/results/classifier/111/network/1791680 deleted file mode 100644 index 56a069ea5..00000000 --- a/results/classifier/111/network/1791680 +++ /dev/null @@ -1,104 +0,0 @@ -network: 0.104 -semantic: 0.103 -permissions: 0.093 -debug: 0.088 -other: 0.084 -PID: 0.083 -device: 0.075 -files: 0.069 -boot: 0.058 -performance: 0.054 -graphic: 0.052 -socket: 0.052 -vnc: 0.051 -KVM: 0.034 -network: 0.799 -debug: 0.056 -PID: 0.023 -boot: 0.021 -device: 0.019 -files: 0.016 -socket: 0.016 -other: 0.015 -semantic: 0.008 -graphic: 0.007 -performance: 0.006 -KVM: 0.006 -permissions: 0.004 -vnc: 0.004 - -network bridge does not work - -hi there - -the network bridge does not seem to work described as here: https://en.wikibooks.org/wiki/QEMU/Networking - -When i add that parameters in a 192.168.80.x subnet, my emulated raspbian ARM gets the IP 10.0.2.15.... While all other computers get 192.168.80.x - -The command i use is: - - -qemu-system-arm.exe -M versatilepb -cpu arm1176 -hda 2018-09-03_stretch_inkl_phalcon.img -kernel kernel-qemu-4.4.34-jessie -m 192 -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" -no-reboot -net nic -net user -device e1000,mac=52:54:00:12:34:56 & - - -Does not build up a network bridge to 192.168.80.x... - -The host system i use is win10 x64 v1803 - -Best regards, -Jan - -J:\Tools\qemu>qemu-system-arm.exe -M versatilepb -cpu arm1176 -hda 2018-09-03_stretch_inkl_phalcon.img -kernel kernel-qe -mu-4.4.34-jessie -m 192 -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" -no-reboot -net nic -net user -device e1000, -mac=52:54:00:12:34:56 -WARNING: Image format was not specified for '2018-09-03_stretch_inkl_phalcon.img' and probing guessed raw. - Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted. - - Specify the 'raw' format explicitly to remove the restrictions. -dsound: Could not initialize DirectSoundCapture -dsound: Reason: No sound driver is available for use, or the given GUID is not a valid DirectSound device ID -qemu-system-arm.exe: warning: nic e1000.0 has no peer - - -10.0.2.15 is neither a ip in our dhcp range nor an apipa address - strange - -but google is pingable, so i have internet. - -must be nat, right?? - -Yes, looks like nat - 10.10.2.15 is not pingable from 192.168.80.x but vice versa... - -but wqhat they write here is not nat: "If no network options are specified, QEMU will default to emulating a single Intel e1000 PCI card with a user-mode network stack that bridges to the host's network. The following three command lines are equivalent:" - -And i think my params are right? - -... -net nic -net user -device e1000,mac=52:54:00:12:34:56 & - -That comment about e1000 is only true for qemu-system-i386. For ARM machines, there are other default NICs. You should also not mix "-net" and "-device", see https://www.qemu.org/2018/05/31/nic-parameter/ for some details. And concerning NAT, yes the "user" backend is using NAT, see https://wiki.qemu.org/Documentation/Networking#User_Networking_.28SLIRP.29 for details about that. - -OK thx. - -"The -device option can only be used for pluggable NICs. Boards (e.g. embedded boards) which feature an on-board NIC cannot be configured with -device yet, so -net nic,netdev=<id> must be used here instead." - -when i only use "-net nic", i get an apipa address - -what do i need for netdev id? n1 as described in your links does not work. messsage: "netdev 'n1' not found" - -currently, only one nic adapter is enabled on my win10 host: the ethernet controller. - -the other 2, 1x internal wlan and 1x usb wlan is disabled.. - -"That comment about e1000 is only true for qemu-system-i386. For ARM machines, there are other default NICs." - -but why im able to ping google with that config?? - -"-nic tap,model=e1000" - --> "Device 'tap' colud not be found - -incompatible with windows, right? so i need a linux machine with ethx?? - -https://bugs.launchpad.net/qemu/+bug/1404278 - -problem solved! :-) - |
