Article 5414K network corruption in qemu4.0 client

network corruption in qemu4.0 client

by
timsoft
from LinuxQuestions.org on (#5414K)
hi all, I have a slackware 14.2 64bit client running in qemu on a slackware 14.2 64bit host. Both client and host have a samba share mounted to /mnt/smb1 containing among other things my local copy of slackware 14.2 rsynced weekly with uk mirror.
I run the vm with the following.
Code:qemu-system-x86_64 -cpu qemu64 -smp 4 -m 8G -drive file=/data/images/slack14.2_64bit_base.qcow2,format=qcow2 -cdrom /mnt/smb1/slackware/iso/slackware64-14.2-install-dvd.iso -boot c -net nic,macaddr=02:00:00:11:11:15,model=i82551 -net bridge,br=br0 -enable-kvm -k en-gb -display vnc=:1 -monitor telnet:localhost:7100,server,nowait,nodelay -drive file=/data/images/nvmed1.qcow2,format=qcow2,if=none,id=nvdisk1 -device nvme,drive=nvdisk1,serial=foo -drive file=/data/images/nvmed2.qcow2,format=qcow2,if=none,id=nvdisk2 -device nvme,drive=nvdisk2,serial=foo -drive file=/data/images/nvmed3.qcow2,format=qcow2,if=none,id=nvdisk3 -device nvme,drive=nvdisk3,serial=fooso network is bridged.
running md5sums on thunderbird on the mounted cifs drive ie.
Code:md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txzworks reliably on the host, but on the client does not, I get the correct md5sum sometimes, but often it is wrong.
Code:root@devslack64:~# md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
96018db681c9be2d19e40fa1f5fafb56 /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
root@devslack64:~# md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
96018db681c9be2d19e40fa1f5fafb56 /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
root@devslack64:~# md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
87cbf258758e332be5b6dba328b49318 /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
root@devslack64:~# md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
7a90575e5b14f056e1114a747a4df202 /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
root@devslack64:~# md5sum /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txz
96018db681c9be2d19e40fa1f5fafb56 /mnt/smb1/slackware/14.2-64bit/patches/packages/mozilla-thunderbird-68.8.1-x86_64-1_slack14.2.txzI think this was the cause of my recent issue with firefox not running, and a previous one with upgradepkg not working for some packages.
Has anyone else had these sort of issues, and is there a work-around ? both the host and client are running 4.4.217 kernel.
At first I was suspecting hardware, but the host has no problems, which seems to point to software,ie qemu or its libs. as can be seen from the vm startup line, I'm using qcow2 format for the vm drive/s. It is a bit disconcerting as the vm is my slackbuilds machine which I use for testing and creating all the builds I use. any ideas would be appreciated.latest?d=yIl2AUoC8zA latest?i=v0oQ4HD1qxI:AXPhWWkZ-DI:F7zBnMy latest?i=v0oQ4HD1qxI:AXPhWWkZ-DI:V_sGLiP latest?d=qj6IDK7rITs latest?i=v0oQ4HD1qxI:AXPhWWkZ-DI:gIN9vFwv0oQ4HD1qxI
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments