From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zl0qb-0000nk-W8 for qemu-devel@nongnu.org; Sat, 10 Oct 2015 16:34:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zl0qY-000759-Om for qemu-devel@nongnu.org; Sat, 10 Oct 2015 16:34:29 -0400 Received: from mail-lb0-x22f.google.com ([2a00:1450:4010:c04::22f]:35200) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zl0qY-000752-Gi for qemu-devel@nongnu.org; Sat, 10 Oct 2015 16:34:26 -0400 Received: by lbwr8 with SMTP id r8so110343416lbw.2 for ; Sat, 10 Oct 2015 13:34:25 -0700 (PDT) From: "mar.krzeminski" Message-ID: <5619764F.3030304@gmail.com> Date: Sat, 10 Oct 2015 22:34:23 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------020400000900090500080704" Subject: [Qemu-devel] Arm virtual machine networking problem with build for 64bit host List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org Developers" Cc: Peter Maydell , Peter Crosthwaite This is a multi-part message in MIME format. --------------020400000900090500080704 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, I have my own virtual machine (already asked some questions about that here). I also have my own gmac model. I am building qemu (version 2.4.0.1) for 32 and 64 linux hosts. The problem is with 64 bit binary. If I run as guest under qemu linux, I could not even ping my machine. In 32 bit version it works fine. And if I run in this 64 bit host u-boot pingf from u-boot qorks fine. From debugging it seems that under linux (32 bit arm) started on 64 linux host can_receive function from my model, is called only once when virtual machine is booting, there is no furthers call so that is why I can not ping. I am running qemu in this way (based on yocto scripts): /qemu-system-arm -kernel zImage.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M macine-a9 -dtb zImage.dtb -serial null -serial null -serial null -serial mon:stdio -serial null -nographic -smp 2 -readconfig config -m 512 --append "ip=192.168.7.2::192.168.7.1:255.255.255.0 noinitrd console=ttyS3,19200 earlyprintk debug=31"/ As there is lack of documentation (or maybe there is but I haven't got it ), my question is where should I start debugging what is going wrong? As for now it seems that my model does not receive ping and it is not asked if can receive one. Situation is same when I ping from quest the host's tap, or from host guest machine. Regards, Marcin --------------020400000900090500080704 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Hello,

I have my own virtual machine (already asked some questions about that here).
I also have my own gmac model. I am building qemu (version 2.4.0.1) for 32 and 64 linux hosts.
The problem is with 64 bit binary. If I run as guest under qemu linux, I could not even ping my machine.
In 32 bit version it works fine. And if I run in this 64 bit host u-boot pingf from u-boot qorks fine.
From debugging it seems that under linux (32 bit arm) started on 64 linux host can_receive function from my model,
is called only once when virtual machine is booting, there is no furthers call so that is why I can not ping.
I am running qemu in this way (based on yocto scripts):

qemu-system-arm -kernel zImage.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M macine-a9 -dtb zImage.dtb -serial null -serial null -serial null -serial mon:stdio -serial null -nographic -smp 2 -readconfig config -m 512 --append "ip=192.168.7.2::192.168.7.1:255.255.255.0 noinitrd console=ttyS3,19200 earlyprintk debug=31"

As there is lack of documentation (or maybe there is but I haven't got it ), my question is where should I start debugging what is going wrong?
As for now it seems that my model does not receive ping and it is not asked if can receive one. Situation is same when I ping from quest the host's tap,
or from host guest machine.

Regards,
Marcin
--------------020400000900090500080704--