thanks for the suggestion. I tried using netcat (nc) to transfer a large file
from host to guest, and also from fileserver to guest with the problematic
i82551 emulated network adapter on the host and the files transfered reliably.
(correct md5sum 3 out of 3 attempts)
I also tried md5sum of the
this would be really useful for testing resilliance and auto fall-over
systems in a vm, to be able to quickly virtually "unplug" a network
connection.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/165
Public bug reported:
qemu 4.0 compiled fom source.
vm called by
qemu-system-x86_64 -cpu qemu64 -smp 4 -m 4G -drive
file=/data/images/slack14.2_64bit_test.qcow2,format=qcow2 -cdrom
/mnt/smb1/slackware/iso/slackware64-14.2-install-dvd.iso -boot c -net
nic,macaddr=02:00:00:11:11:17,model=i82551 -n
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
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
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
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
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
Public bug reported:
using latest qemu 2.2.0 64bit for windows host (installed from
qemu-w64-setup-20141210.exe obtained from http://qemu.weilnetz.de/w64/
),OpenVPN 2.6.3-I601 64bit tap adapter named tap01 and calling qemu
using the following.
qemu-system-x86_64.exe -m 512 -net nic -net tap,ifnam
13 matches
Mail list logo
