Varun Chitre: I'm not sure the fix was identified, but this one stood
out in the git log:
commit b73c1849148da1229a3c3b336311a8194970b35f
Author: Andrew Baumann
Date: Wed Nov 18 11:45:09 2015 -0800
tap-win32: disable broken async write path
--
You received this bug notification because y
What was the fix that took place in the mainstream qemu? I'm facing the
same issue on the latest Android Emulator (emulator: Android qemu
version 30.3.5.0 (build_id 7033400) (CL:N/A)) on Windows 10.
TAP network gets attached just fine and shows us as eth1 on guest in
ifconfig. But cannot ping the
Hi,
I want to run u-boot for x86_64 architecture in windows10 and I am using
qemu-5.0.0, the latest version of qemu. The TAP adapter for Linux (host)
worked successfully and I communicated between u-boot (guest) and Linux
(host), but the result for Windows (host) failed.
I installed the Tap Netwo
hi jan, would you care to elaberate for the benefit of everyone "out
there".
--
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
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
... ah, well, never mind, just saw that you already closed it :-)
--
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 Rel
ok, thanks for checking! So I'm closing this ticket now...
--
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
addition to previous comment. it works with qemu-w64-setup-20180519.exe
I haven't tested it with in between versions of qemu.
--
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 connec
it is working now. using the following config.
"c:\program files\qemu\qemu-system-i386.exe" -cpu qemu32 -m 3G -drive
file="c:\\data\\images\\slack14.2_32bit_base.qcow2",format=qcow2 -cdrom
"c:\\data\\images\\slackware-14.2-install-dvd.iso" -boot c -net
nic,macaddr=02:00:00:11:11:14,model=i82551
i'll check with a more recent version and report back
On 22/05/2018 14:33, Thomas Huth wrote:
> Looking through old bug tickets... can you still reproduce this issue
> with the latest version of QEMU? Or could we close this ticket nowadays?
>
> ** Changed in: qemu
> Status: New => Incomple
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
On Wed, Jan 07, 2015 at 04:09:55PM -, timsoft wrote:
> I have tried what you suggested (breaking the bridge on the host, and giving
> the host tap 192.168.5.1 and the guest eth0 192.168.5.2
> and tried pinging one from the other. I get 100% packet loss.
> This points to QEMU's tap networking a
I'm having the same problem here on Windows 7 x64 host trying to run
Raspbian.
--
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 QE
I also confirm the problem on Windows 7 host.
I tried the following over the past few nights:
Downloaded the OpenVPN tap 32 adapter. Installed it and gave it a different
network address (192.168.200.10) to my normal LAN (192.168.1.10). Bridged the 2
connections, which gets me a new IP via DHCP a
I can concur that I am having the same problem on a Windows host.
--
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:
New
Bu
I have tried what you suggested (breaking the bridge on the host, and giving
the host tap 192.168.5.1 and the guest eth0 192.168.5.2
and tried pinging one from the other. I get 100% packet loss.
This points to QEMU's tap networking as far as I can see.
I have tried uninstalling the 64 bit version
On Tue, Jan 06, 2015 at 09:12:53PM -, timsoft wrote:
> output as requested from the guest:
> ip addr
> 1: lo: mtu 65536 qdisc noqueue state UNKOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
On Tue, Jan 06, 2015 at 09:30:46PM -, timsoft wrote:
> I have also run the 64bit version of qemu with the slight modification
> of the batch/cmd line
>
> cd "c:\program files\qemu"
> qemu-system-x86_64w.exe -m 512 -net nic -net tap,ifname=tap01 -hda
> "c:\\data\\images\\test.img"
>
> and ge
I have also run the 64bit version of qemu with the slight modification
of the batch/cmd line
cd "c:\program files\qemu"
qemu-system-x86_64w.exe -m 512 -net nic -net tap,ifname=tap01 -hda
"c:\\data\\images\\test.img"
and get the same output both for the client(ip addr; ip route; ip
tables -L -n
output as requested from the guest:
ip addr
1: lo: mtu 65536 qdisc noqueue state UNKOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft f
On Mon, Jan 05, 2015 at 05:11:50PM -, timsoft wrote:
> have used wireshark on host and nothing is coming through when I try to ping
> the host from the client. (bare with me as I haven't used wireshark before).
> I'm just upgrading the client to slack64 14.1 so I can get wireshark
> running
have used wireshark on host and nothing is coming through when I try to ping
the host from the client. (bare with me as I haven't used wireshark before).
I'm just upgrading the client to slack64 14.1 so I can get wireshark running
on it. (process is a little slow, especially with no functioning
same behaviour observed with qemu 2.2.0 32bit version for windows host
--
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:
Ne
26 matches
Mail list logo
