problem solved! :-)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
Invalid
Bug description:
hi there
the network bridge does not
problem solved! :-)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1404278
Title:
tap connections not working on windows host
Status in QEMU:
Fix Released
Bug description:
using latest qemu 2.
static ip does also not work, can't reach other machines in my own
subnet:
qemu-system-arm.exe -M versatilepb -cpu arm1176 -hda
2018-09-03_stretch_inkl_phalcon.img -kernel kernel-qemu-4.4.34-jessie -m
512 -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw
ip=192.168.80.252::192.168.80.1:255.255.25
when i install tap driver from https://openvpn.net/index.php/open-
source/downloads.html im able to start with tap01 (when i rename the tap
interface to "tap01"..)
but on start i get an apipa address with that config:
qemu-system-arm.exe -M versatilepb -cpu arm1176 -hda
2018-09-03_stretch_inkl_ph
"it works with qemu-w64-setup-20180519.exe"
not really:
J:\Tools\qemu>.\run.bat
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 512 -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw
init=/bin/bash" -no
https://bugs.launchpad.net/qemu/+bug/1404278
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
Invalid
Bug description:
hi there
the
incompatible with windows, right? so i need a linux machine with ethx??
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
Invalid
Bug des
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= must be used here instead."
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
what do i need for netdev id? n1 as described in your links does not
work. messsage: "netdev 'n1' not found"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not wor
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..
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
when i only use "-net nic", i get an apipa address
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
Invalid
Bug description:
hi there
"-nic tap,model=e1000"
-> "Device 'tap' colud not be found
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
Invalid
Bug description:
"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??
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
but google is pingable, so i have internet.
must be nat, right??
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
New
Bug description:
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
follo
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 spe
10.0.2.15 is neither a ip in our dhcp range nor an apipa address -
strange
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791680
Title:
network bridge does not work
Status in QEMU:
New
Bug desc
Public bug reported:
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
18 matches
Mail list logo
