From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: "Chan Kim" <ckim@etri.re.kr>
Cc: 'Richard' <richard_siegfried@systemli.org>,
kernelnewbies@kernelnewbies.org
Subject: Re: Can I debug busybox program running on a qemu virtual machine using gdb?
Date: Thu, 07 Jul 2022 21:29:35 -0400 [thread overview]
Message-ID: <304321.1657243775@turing-police> (raw)
In-Reply-To: <042001d89267$b5ec7910$21c56b30$@etri.re.kr>
[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]
On Fri, 08 Jul 2022 10:11:53 +0900, "Chan Kim" said:
> I get the message "tftp: sendto: Network is unreachable".
Unless you did something *really* drastic, like figure out how to build
the kernel without IPv4 support (is that even possible yet?), or leave out
support for whatever virtual network device qemu is providing to the
emulated kernel, you're probably just missing an 'ifconfig' and/or a 'route add'
to tell the kernel where the bits need to go.
Less likely, you did something silly like tell the kernel to enforce SELinux
or AppArmor or whatever, but you fed it a policy file that doesn't allow tftp
to have network access....
[-- Attachment #1.2: Type: application/pgp-signature, Size: 494 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2022-07-08 1:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 9:27 Can I debug busybox program running on a qemu virtual machine using gdb? Chan Kim
2022-07-07 23:45 ` Richard
2022-07-08 1:11 ` Chan Kim
2022-07-08 1:29 ` Valdis Klētnieks [this message]
2022-07-08 8:36 ` Tom Mitchell
2022-07-09 1:19 ` Richard
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=304321.1657243775@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=ckim@etri.re.kr \
--cc=kernelnewbies@kernelnewbies.org \
--cc=richard_siegfried@systemli.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