Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp1393203imc; Mon, 11 Mar 2019 12:45:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqwCNu1LIhdtSAhPTduPIVGZL6UzLdhSzzJMsJfXsjFlrOjvEpxEdDid36wfLsSPtSw+JReC X-Received: by 2002:a63:2147:: with SMTP id s7mr30144154pgm.361.1552333554163; Mon, 11 Mar 2019 12:45:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552333554; cv=none; d=google.com; s=arc-20160816; b=A8XWmlo9vCS6kVp6C5AwGJzOjArNangfb/5u4f5khLUlHRguWMDdMV9WLkJGavkCBg jn0hPr12ZDGR2wZtmFW+pJGWr3DM4A0DUUeCQE9nVkb1Nz1IcNpQyrrCEEykuLsgHQEn Q9BIQ48vYFNdDeh9k/54CLFReK47TlDWGKefWsj4+Ac16O1ndDc1k8tuMzk75w1+qnbW 588TENNmMvltD2QiPX228QmazrDjMLDS1tN6t+y+cA5MQ4CAVPEe4m06irdKPV0LwCQN k1/Xxx6KYRw/FxKd0Zz67sd+PPZiY65P+S7tQD2A6/NdBg0QJ0BiKQq8/i+ufJKd9G1s DkPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=vLeVI4LB0FTnKSwGylLC2x3Sf+vUVzJ9R3zL2vhpXmU=; b=OaOsUGTg/Wg8wpIRDh37pDr/ENLR6N2djVY7JmV3QhXMaot7eXtNTcw5n/gD7w8xK3 GMKEkZibK4iEjT0Aa9SbKHHGrx6zNgH7sZ1U4GieXyYTrkbvfaJ/tdSaweT6tJo0hnYi X+l6pjuqSQwhiWiGcPEDPe+MqDcX0l3Yi6fpZgKmIVHHWfsrDv6zjETAeQeF5EFyxiR8 qW7vxqQlWNcv4QwlnTnsqXnZ8J7pA0LTsS/VPAYvJWQs3HdfXpC9cNM/SZndlW8DYEPj mScC4TzvK7uA4OB1Uv1DxCQcQoHxUykUMROcp+KWgp+zZLASWsTRG684oKNszIGlYvPe lW+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e16si5341412pgv.436.2019.03.11.12.45.38; Mon, 11 Mar 2019 12:45:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728171AbfCKTnt (ORCPT + 99 others); Mon, 11 Mar 2019 15:43:49 -0400 Received: from zero.eik.bme.hu ([152.66.115.2]:59611 "EHLO zero.eik.bme.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727008AbfCKTns (ORCPT ); Mon, 11 Mar 2019 15:43:48 -0400 X-Greylist: delayed 606 seconds by postgrey-1.27 at vger.kernel.org; Mon, 11 Mar 2019 15:43:46 EDT Received: from zero.eik.bme.hu (blah.eik.bme.hu [152.66.115.182]) by localhost (Postfix) with SMTP id 94CB27456B3; Mon, 11 Mar 2019 20:33:39 +0100 (CET) Received: by zero.eik.bme.hu (Postfix, from userid 432) id 73F847456B2; Mon, 11 Mar 2019 20:33:39 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zero.eik.bme.hu (Postfix) with ESMTP id 734E17456A0; Mon, 11 Mar 2019 20:33:39 +0100 (CET) Date: Mon, 11 Mar 2019 20:33:39 +0100 (CET) From: BALATON Zoltan To: Pintu Agarwal cc: open list , kernelnewbies@kernelnewbies.org, linux-arm-kernel@lists.infradead.org, linux-riscv@lists.infradead.org, qemu-devel@nongnu.org, =?EUC-KR?B?wPzB+L+1?= Subject: Re: [Qemu-devel] ssh session with qemu-arm using busybox In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Spam-Checker-Version: Sophos PMX: 6.4.6.2792898, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.3.11.192716, AntiVirus-Engine: 5.58.0, AntiVirus-Data: 2019.3.11.5580001, https://viki.eik.bme.hu/doku.php?id=spam_filter X-Spam-Flag: NO X-Spam-Probability: 8% X-Spam-Level: X-Spam-Status: No, score=8% required=50% tests= MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1800_1899 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, IN_REP_TO 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, MULTIPLE_REAL_RCPTS 0, REFERENCES 0, SINGLE_URI_IN_BODY 0, URI_WITH_PATH_ONLY 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CC_NAME 0, __CC_NAME_DIFF_FROM_ACC 0, __CC_REAL_NAMES 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __DQ_NEG_HEUR 0, __DQ_NEG_IP 0, __FORWARDED_MSG 0, __HAS_CC_HDR 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __NO_HTML_TAG_RAW 0, __REFERENCES 0, __SANE_MSGID 0, __SINGLE_URI_TEXT 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __SUBJ_REPLY 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __URI_IN_BODY 0, __URI_NOT_IMG 0, __URI_NO_MAILTO 0, __URI_NO_WWW 0, __URI_NS , __URI_WITH_PATH 0, __USER_AGENT 0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 11 Mar 2019, Pintu Agarwal wrote: > I am sure, many of you people would have explored already "how to use > ssh over qemu" and found a easy method. > So, if anybody have easy setup please share with me. > > I could see that after adding "ip=dhcp" I get the eth0 interface like this: > / # ifconfig > eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56 > inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:1180 (1.1 KiB) TX bytes:1180 (1.1 KiB) > Interrupt:22 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:65536 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > But I could not ping it from ubuntu PC. This should already be documented here: https://wiki.qemu.org/Documentation/Networking The default QEMU network is -net user slirp based networking that provides outbound connectivity from the virtual machine but no ping or inbound connections. I.e. you can ssh from your guest to your host (so you could use scp in your guest to copy files from your host) or use some other networking (such as tap) that allows the host to connect to guest (but then you'll need to arrange routing and dhcp if you want that on your host otherwise your guest will only see your host). Hope this helps. Regards, BALATON Zoltan