The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" within the next 60 days (otherwise it will get
closed as "Expired"). We will then eventually migrate the ticket auto-
matically to the new system (but you won't be the reporter of the bug
in the new system and thus won't get notified on changes anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1882241
Title:
file transfer over cifs to 64bit guest corrupts large files
Status in QEMU:
Incomplete
Bug description:
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 -net bridge,br=br0 -enable-kvm -k
en-gb -display vnc=:3 -monitor telnet:localhost:7103,server,nowait,nodelay
copying large files eg 2.4gb or reading them on a cifs mount in the guest
causes corruption every time. For smaller files 40-60mb corruption is more than
50% of the time. tested by md5sum on cifs server, or on host machine vs. on
guest vm.
corruption is seen only with 64bit guest using cifs with i82551 emulated
network device
ie. 32bit guest using cifs with i82551 emulated network device gives no
corruption.
changing the emulated device to vmxnet3 removes the data corruption
(see below)
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=vmxnet3 -net bridge,br=br0
-enable-kvm -k en-gb -display vnc=:3 -monitor
telnet:localhost:7103,server,nowait,nodelay
this corruption is repeatable. ie. I created new vm, call using top example,
installed 64bit linux, mounted cifs share and copied 2.4gb file to /tmp then
run md5sum "filecopied"
the md5sum is different every time. copy same file to the host, or to a 32bit
guest with the same virtual network device and bridge and md5sums are correct.
The host pysical network adapter is
lspci|grep Ether
1e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
physically connected via gigabit ethernet to cifs server (via gigabit
switch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1882241/+subscriptions
