From: BALATON Zoltan <balaton@eik.bme.hu>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: kernelnewbies@kernelnewbies.org, qemu-devel@nongnu.org,
"open list" <linux-kernel@vger.kernel.org>,
전진영 <jy0.jeon@gmail.com>,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Qemu-devel] ssh session with qemu-arm using busybox
Date: Mon, 11 Mar 2019 20:33:39 +0100 (CET) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1903112027050.69539@zero.eik.bme.hu> (raw)
In-Reply-To: <CAOuPNLgobR4ejPs_ZUuXpRwkURH0sfb1LD27TKhGg=wrwhUvZg@mail.gmail.com>
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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-03-13 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 14:34 ssh session with qemu-arm using busybox Pintu Agarwal
2019-03-11 18:28 ` Nick Kossifidis
2019-03-12 14:02 ` Pintu Agarwal
2019-03-12 14:11 ` Suzuki K Poulose
2019-03-12 17:08 ` Pintu Agarwal
2019-03-12 23:12 ` [Qemu-devel] " Dongli Zhang
2019-03-11 19:33 ` BALATON Zoltan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.BSF.2.21.9999.1903112027050.69539@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=jy0.jeon@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=pintu.ping@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).