Intshayelelo evela kumguquleli: Ngokuchasene nemvelaphi yokungenwa okukhulu kweentlobo ezahlukeneyo zemigqomo kubomi bethu, kunokuba nomdla kwaye kube luncedo ukufumanisa ukuba zeziphi iitekhnoloji eziqale kanye ngexesha. Ezinye zazo zinokusetyenziswa ngokufanelekileyo ukuza kuthi ga namhlanje, kodwa akuyena wonke umntu okhumbula iindlela ezinjalo (okanye uyazi, ukuba abazange babanjwe ngexesha lokuphuhliswa kwabo ngokukhawuleza). Enye itekhnoloji enjalo yiMode yoMsebenzisi yeLinux. Umbhali weyokuqala wenze isixa esifanelekileyo sokumba, ecinga ukuba yeyiphi kuphuhliso oludala olusasebenza kwaye olungasasebenziyo, kwaye wadibanisa into efana nemiyalelo yenyathelo nenyathelo malunga nendlela yokuzenzela i-UML ekhule ekhaya. 2k19. Kwaye ewe, simeme umbhali weposi yokuqala kuHabr , ngoko ke ukuba unemibuzo, cela ngesiNgesi kwizimvo.
Imowudi yomsebenzisi kwiLinux, enyanisweni, lizibuko leLinux kernel kuyo ngokwayo. Le ndlela ikuvumela ukuba usebenzise i-Linux kernel epheleleyo njengenkqubo yomsebenzisi kwaye iqhele ukusetyenziswa ngabaphuhlisi ukuvavanya abaqhubi. Kodwa le modi ikwaluncedo njengesixhobo sokuzihlukanisa ngokubanzi, umgaqo ofana nokusebenza koomatshini benyani. Le mowudi ibonelela ngokuzimela okukhulu kune-Docker, kodwa ngaphantsi komatshini ogcweleyo ogcweleyo onjenge-KVM okanye iBhokisi yeVirtual.
Lilonke, iMowudi yoMsebenzisi inokubonakala ngathi sisixhobo esingaqhelekanga nesinzima sokusisebenzisa, kodwa inokusebenzisa kwayo. Emva kwayo yonke loo nto, le yiLinux kernel epheleleyo esebenza njengomsebenzisi ongenalungelo. Eli nqaku livumela ikhowudi enokubakho engathembekanga ukuba iqhube ngaphandle kwesoyikiso kumatshini wokusingatha. Kwaye ekubeni le kernel epheleleyo, iinkqubo zayo zihlukanisiwe kumatshini wokusingatha, oko kukuthi iinkqubo ezisebenza ngaphakathi kweNdlela yoMsebenzisi aziyi kubonakala kumamkeli. Oku akufani nesitya se-Docker yendabuko, apho umatshini wokusingatha uhlala ebona iinkqubo ngaphakathi kwendawo yokugcina. Jonga esi siqwenga se pstree kwenye yeeseva zam:
containerd─┬─containerd-shim─┬─tini─┬─dnsd───19*[{dnsd}]
│ │ └─s6-svscan───s6-supervise
│ └─10*[{containerd-shim}]
├─containerd-shim─┬─tini─┬─aerial───21*[{aerial}]
│ │ └─s6-svscan───s6-supervise
│ └─10*[{containerd-shim}]
├─containerd-shim─┬─tini─┬─s6-svscan───s6-supervise
│ │ └─surl
│ └─9*[{containerd-shim}]
├─containerd-shim─┬─tini─┬─h───13*[{h}]
│ │ └─s6-svscan───s6-supervise
│ └─10*[{containerd-shim}]
├─containerd-shim─┬─goproxy───14*[{goproxy}]
│ └─9*[{containerd-shim}]
└─32*[{containerd}]Kwaye uthelekise oku kwi-psree ye-Linux kernel kwiNdlela yoMsebenzisi:
linux─┬─5*[linux]
└─slirpXa usebenza nezikhongozeli zeDocker, ndiyabona kummkeli amagama eenkqubo ezisebenza kundwendwe. Oku akunakwenzeka ngeModi yoMsebenzisi weLinux. Ingaba ithetha ntoni? Oku kuthetha ukuba izixhobo zokubeka iliso ezisebenza ngenkqubo ephantsi yophicotho ye-Linux andiboni iinkqubo ezisebenza kwinkqubo yeendwendwe. Kodwa kwezinye iimeko olu phawu lunokuba yikrele elintlangothi-mbini.
Ngokubanzi, yonke isithuba esingezantsi yingqokelela yophando kunye nemizamo enzima yokufezekisa umphumo oyifunayo. Ukwenza oku, kuye kwafuneka ndisebenzise izixhobo zakudala ezahlukeneyo, ndifunde imithombo ye-kernel, ndibandakanyeke kwi-debugging enzulu yekhowudi ebhalwe xa ndandisesesikolweni samabanga aphantsi, kwaye ndikhe ndajongana noHeroku wakha usebenzisa i-binary ekhethekileyo ukukhangela izixhobo endizifunayo. Wonke lo msebenzi ukhokelele ekubeni abafana abakwi-IRC yam bandibize ngomlingo. Ndiyathemba ukuba esi sithuba siya kusebenza njengamaxwebhu athembekileyo ukuba umntu enze into efanayo, kodwa ngeenkozo ezintsha kunye neenguqulelo ze-OS.
Yenza ngokwezifiso
Ukuseta iNdlela yoMsebenzisi weLinux kubandakanya amanyathelo amaninzi:
- ukufaka ukuxhomekeka kumamkeli;
- ikhuphela i Linux kernel;
- ukuseta i-kernel yokwakha;
- indibano ye-kernel;
- ukufaka i-binary;
- ukuseta inkqubo yefayile yeendwendwe;
- ukhetho lweeparamitha zokuqaliswa kwe-kernel;
- ukuseta inethiwekhi yeendwendwe;
- ukusungula i-kernel yeendwendwe.
Ndicinga ukuba ukuba uthatha isigqibo sokwenza konke oku ngokwakho, ngokuqinisekileyo uya kwenza yonke into echazwe kwi-Ubuntu okanye inkqubo efana ne-Debian. Ndizamile ukuphumeza konke oku kungentla kunikezelo lwam endiluthandayo-iAlpine, kodwa akukho nto isebenzayo, ngokucacileyo kuba i-Linux kernel ibotshelelwe ngokuqinileyo kwi-glibc-isms yabaqhubi kwiModi yoMsebenzisi. Ndicwangcisa ukuxela oku ukuya phezulu emva kokuba ndiyifumene ingxaki.
Ukuhlohla ukuxhomekeka kumamkeli
Ubuntu bufuna ubuncinci ezi phakheji zilandelayo ukwakha i-Linux kernel (ucinga ukufakela okucocekileyo):
- 'build-essential'
- 'flex'
- 'bison'
- 'xz-utils'
- 'wget'
- 'ca-certificates'
- 'bc'
- 'linux-headers'
Ungazifaka ngalo myalelo ulandelayo (njengengcambu okanye nge-sudo):
apt-get -y install build-essential flex bison xz-utils wget ca-certificates bc
linux-headers-$(uname -r)
Nceda qaphela ukuba ukuqhuba inkqubo yokwenza imenyu ye Linux kernel kuya kufuna ufakelo libncurses-dev. Nceda qinisekisa ukuba ifakwe usebenzisa lo myalelo ulandelayo (njengengcambu okanye usebenzisa i-sudo):
apt-get -y install libncurses-devIkhuphela ikernel
Qinisekisa ukuba ungakhuphela phi kwaye emva koko wakhe i-kernel. Kuya kufuneka unikeze malunga ne-1,3 GB yendawo ye-hard drive kulo msebenzi, ke qiniseka ukuba unayo.
Emva koko yiya ku kwaye ufumane i-URL yokukhuphela inguqulelo yamva nje ezinzileyo yekernel. Ngexesha lokubhalwa kwesi sithuba:
Khuphela le fayile usebenzisa 'wget':
wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.1.16.tar.xz
Kwaye uyikhuphe nge 'tar':
tar xJf linux-5.1.16.tar.xzNgoku singenisa uvimba weefayili owenziweyo xa ukhulula itarball:
cd linux-5.1.16Ukuseta i-kernel build
Inkqubo yokwakha i-kernel iseti с ezininzi izixhobo zesiko kunye nezikripthi ukwenza inkqubo izenzekele. Ukuqalisa, vula inkqubo yokuseta kwi-intanethi:
make ARCH=um menuconfig
Iza kugqiba ngokuyinxenye indibano kwaye ibonise ibhokisi yencoko yababini yakho. Xa ukukhanya kuvela ezantsi kwefestile[Select]', ungaqwalasela izicwangciso usebenzisa iSpacebar okanye Ngena izitshixo. Ukukhangela ujikeleze ifestile njengesiqhelo usebenzisa utolo lwebhodi yezitshixo “phezulu” kunye “ezantsi”, kwaye ukukhetha izinto “kusekhohlo” okanye “ekunene”.
Isalathisi sokujonga -> sithetha ukuba ukwimenyu engaphantsi, enokufikelelwa ngokusebenzisa iqhosha le-Enter. Indlela yokuphuma ngokucacileyo idlula '[Exit]'.
Quka olu khetho lulandelayo kwi '[Select]' kwaye qinisekisa ukuba kukho '[*]' isimboli ecaleni kwabo:
UML-specific Options:
- Host filesystem
Networking support (enable this to get the submenu to show up):
- Networking options:
- TCP/IP Networking
UML Network devices:
- Virtual network device
- SLiRP transport
Yiyo leyo, ungaphuma kule festile ngokukhetha ngokulandelelanayo '[Exit]'. Qinisekisa nje ukuba ekugqibeleni uyacelwa ukuba ugcine uqwalaselo kwaye ukhethe '[Yes]'.
Ndincoma ukuba udlale malunga neenketho zokwakha i-kernel emva kokufunda le post. Kolu vavanyo unokufunda okuninzi malunga nendlela i-kernel mechanics esebenza ngayo kunye nendlela iiflegi ezahlukeneyo ezichaphazela ngayo indlela ikernel eyakhiwe ngayo.
Ukwakha i-kernel
I-Linux kernel yinkqubo enkulu eyenza izinto ezininzi. Nokuba inobumbeko luncinci kwihardware endala, ukudibanisa kunokuthatha ixesha elithile. Yakha ke i-kernel usebenzisa lo myalelo ulandelayo:
make ARCH=um -j$(nproc)
Yantoni? Lo myalelo uya kuxelela umakhi wethu ukuba asebenzise zonke ii-CPU cores ezikhoyo kunye neentambo ngexesha lenkqubo yokwakha. Iqela $(nproc) ekupheleni Yakha ifaka imveliso yomyalelo nproc, eyinxalenye coreutils kuBukhi obuqhelekileyo.
Emva kwexesha elithile, i-kernel yethu iya kuhlanganiswa ibe yifayile ephunyeziweyo ./linux.
Ukuhlohla ibini
Kuba iNdlela yoMsebenzisi kwiLinux yenza ibhinari eqhelekileyo, ungayifaka njengayo nayiphi na enye into eluncedo. Nantsi indlela endenze ngayo:
mkdir -p ~/bin
cp linux ~/bin/linux
Kukwafanelekile ukuba uqinisekise ukuba ~/bin ikuwe $PATH:
export PATH=$PATH:$HOME/binUkuqwalasela iNkqubo yeFayile yoNdwendwe
Yenza uvimba weefayili wenkqubo yefayile yeendwendwe:
mkdir -p $HOME/prefix/uml-demo
cd $HOME/prefix
Vula alpinelinux.org kwaye ungene fumana ikhonkco lokukhuphela langoku MINI ROOT FILESYSTEM. Ngexesha lokubhala oku kwaba:
http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gzKhuphela le tarball usebenzisa i-wget:
wget -O alpine-rootfs.tgz http://dl-cdn.alpinelinux.org/alpine/v3.10/releases/x86_64/alpine-minirootfs-3.10.0-x86_64.tar.gzNgoku ngenisa ulawulo lwefayile yeendwendwe kwaye ukhuphe indawo yokugcina:
cd uml-demo
tar xf ../alpine-rootfs.tgzAmanyathelo achaziweyo aya kudala itemplate yefayile encinci. Ngenxa yendlela esebenza ngayo inkqubo, ukufaka iipakethe ngomphathi we-apk we-Alpine kuya kuba nzima kakhulu. Kodwa le FS iya kwanela ukuvavanya umbono jikelele.
Sikwafuna isixhobo ukumisa ukusetyenziswa kwememori ikernel yethu yeendwendwe.
wget -O tini https://github.com/krallin/tini/releases/download/v0.18.0/tini-static
chmod +x tiniUkwenza iKernel Command Line
I-Linux kernel, njengezinye iinkqubo ezininzi, ineengxoxo zelayini yomyalelo ezinokufikelelwa ngokukhankanya isitshixo --help.
Yena ngokwakhe—uncedo
linux --help
User Mode Linux v5.1.16
available at http://user-mode-linux.sourceforge.net/
--showconfig
Prints the config file that this UML binary was generated from.
iomem=<name>,<file>
Configure <file> as an IO memory region named <name>.
mem=<Amount of desired ram>
This controls how much "physical" memory the kernel allocates
for the system. The size is specified as a number followed by
one of 'k', 'K', 'm', 'M', which have the obvious meanings.
This is not related to the amount of memory in the host. It can
be more, and the excess, if it's ever used, will just be swapped out.
Example: mem=64M
--help
Prints this message.
debug
this flag is not needed to run gdb on UML in skas mode
root=<file containing the root fs>
This is actually used by the generic kernel in exactly the same
way as in any other kernel. If you configure a number of block
devices and want to boot off something other than ubd0, you
would use something like:
root=/dev/ubd5
--version
Prints the version number of the kernel.
umid=<name>
This is used to assign a unique identity to this UML machine and
is used for naming the pid file and management console socket.
con[0-9]*=<channel description>
Attach a console or serial line to a host channel. See
http://user-mode-linux.sourceforge.net/old/input.html for a complete
description of this switch.
eth[0-9]+=<transport>,<options>
Configure a network device.
aio=2.4
This is used to force UML to use 2.4-style AIO even when 2.6 AIO is
available. 2.4 AIO is a single thread that handles one request at a
time, synchronously. 2.6 AIO is a thread which uses the 2.6 AIO
interface to handle an arbitrary number of pending requests. 2.6 AIO
is not available in tt mode, on 2.4 hosts, or when UML is built with
/usr/include/linux/aio_abi.h not available. Many distributions don't
include aio_abi.h, so you will need to copy it from a kernel tree to
your /usr/include/linux in order to build an AIO-capable UML
nosysemu
Turns off syscall emulation patch for ptrace (SYSEMU).
SYSEMU is a performance-patch introduced by Laurent Vivier. It changes
behaviour of ptrace() and helps reduce host context switch rates.
To make it work, you need a kernel patch for your host, too.
See http://perso.wanadoo.fr/laurent.vivier/UML/ for further
information.
uml_dir=<directory>
The location to place the pid and umid files.
quiet
Turns off information messages during boot.
hostfs=<root dir>,<flags>,...
This is used to set hostfs parameters. The root directory argument
is used to confine all hostfs mounts to within the specified directory
tree on the host. If this isn't specified, then a user inside UML can
mount anything on the host that's accessible to the user that's running
it.
The only flag currently supported is 'append', which specifies that all
files opened by hostfs will be opened in append mode.Eli qela lolawulo liqaqambisa eyona parameters yokuqalisa. Masiqhube i-kernel ngobuncinci obufunekayo iseti yokhetho:
linux
root=/dev/root
rootfstype=hostfs
rootflags=$HOME/prefix/uml-demo
rw
mem=64M
init=/bin/shImigca engentla ixelela i-kernel yethu oku kulandelayo:
- Makhe sicinge ukuba inkqubo yefayile yengcambu sisixhobo sobuzenzisi
/dev/root. - Khetha njengomqhubi wenkqubo yefayile yengcambu.
- Nyusa indlela yefayile yeendwendwe esiyenzileyo kwisixhobo esiyingcambu.
- Kwaye ewe, kwindlela yokufunda-bhala.
- Sebenzisa kuphela i-64 megabytes ye-RAM (ungasebenzisa kancinci ngokuxhomekeke kwinto oceba ukuyenza, kodwa i-64 MB ibonakala iyeyona mali ifanelekileyo).
- I-kernel iqala ngokuzenzekelayo
/bin/shnjaniinit-inkqubo.
Sebenzisa lo myalelo kwaye kuya kufuneka ufumane into efana nale ilandelayo:
Elinye iphepha
Core dump limits :
soft - 0
hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking environment variables for a tempdir...none found
Checking if /dev/shm is on tmpfs...OK
Checking PROT_EXEC mmap in /dev/shm...OK
Adding 32137216 bytes to physical memory to account for exec-shield gap
Linux version 5.1.16 (cadey@kahless) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #30 Sun Jul 7 18:57:19 UTC 2019
Built 1 zonelists, mobility grouping on. Total pages: 23898
Kernel command line: root=/dev/root rootflags=/home/cadey/dl/uml/alpine rootfstype=hostfs rw mem=64M init=/bin/sh
Dentry cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Memory: 59584K/96920K available (2692K kernel code, 708K rwdata, 588K rodata, 104K init, 244K bss, 37336K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS: 15
clocksource: timer: mask: 0xffffffffffffffff max_cycles: 0x1cd42e205, max_idle_ns: 881590404426 ns
Calibrating delay loop... 7479.29 BogoMIPS (lpj=37396480)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 512 (order: 0, 4096 bytes)
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
devtmpfs: initialized
random: get_random_bytes called from setup_net+0x48/0x1e0 with crng_init=0
Using 2.6 host AIO
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 0, 6144 bytes)
NET: Registered protocol family 16
clocksource: Switched to clocksource timer
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
console [stderr0] disabled
mconsole (version 2) initialized on /home/cadey/.uml/tEwIjm/mconsole
Checking host MADV_REMOVE support...OK
workingset: timestamp_bits=62 max_order=14 bucket_order=0
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered (default)
io scheduler bfq registered
loop: module loaded
NET: Registered protocol family 17
Initialized stdio console driver
Using a channel type which is configured out of UML
setup_one_line failed for device 1 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 2 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 3 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 4 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 5 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 6 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 7 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 8 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 9 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 10 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 11 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 12 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 13 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 14 : Configuration failed
Using a channel type which is configured out of UML
setup_one_line failed for device 15 : Configuration failed
Console initialized on /dev/tty0
console [tty0] enabled
console [mc-1] enabled
Failed to initialize ubd device 0 :Couldn't determine size of device's file
VFS: Mounted root (hostfs filesystem) on device 0:11.
devtmpfs: mounted
This architecture does not have kernel memory protection.
Run /bin/sh as init process
/bin/sh: can't access tty; job control turned off
random: fast init done
/ # Ezi migaqo zingentla ziya kusinika inkqubo yeendwendwe encinci, ngaphandle kwezinto ezifana /proc okanye igama lomamkeli elabelwe. Umzekelo, zama le miyalelo ilandelayo:
- uname -av
- cat /proc/self/pid
- hostname
Ukuphuma kwinkqubo yeendwendwe, ngena exit okanye cinezela control-d. Oku kuya kutshisa iqokobhe elilandelwa yi-kernel panic:
/ # exit
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
fish: “./linux root=/dev/root rootflag…” terminated by signal SIGABRT (Abort)
Sifumene le kernel panic kuba i-Linux kernel icinga ukuba inkqubo yokuqalisa ihlala isebenza. Ngaphandle kwayo, inkqubo ayinakuphinda isebenze kwaye ivale. Kodwa kuba le yinkqubo yendlela yomsebenzisi, isiphumo esisiphumo sizithumela kuyo SIGABRT, ekhokelela ekuphumeni.
Ukumisela inethiwekhi yeendwendwe
Kodwa kulapho izinto ziqala khona ukungahambi kakuhle kuthi. Uthungelwano kwiNdlela yoMsebenzisi iLinux kulapho yonke ingqikelelo "yemowudi yomsebenzisi" iqala ukuwohloka. Emva kwayo yonke loo nto, inethiwekhi idla ngokukhawulelwa kwinqanaba lenkqubo nelungelo iindlela zokubulawa ngenxa yezizathu ezicacileyo kuthi sonke.
Phawula ngokwe.: Unokufunda ngakumbi malunga neenketho ezahlukeneyo zokusebenza nomsebenzi womnatha kwi UML .
Uhambo lokutyibilika
Nangona kunjalo, kukho isixhobo sakudala kwaye esingaxhaswanga esibizwa ngokuba , apho iModi yoMsebenzisi iLinux inokunxibelelana nenethiwekhi. Isebenza ngokurhabaxa njengenqanaba lomsebenzisi TCP/IP istaki kwaye ayifuni naziphi na iimvume zesixokelelwano sokusebenza. Esi sixhobo sasinjalo yakhutshwa ngo-1995, kwaye uhlaziyo lokugqibela lubhalwe umhla 2006. USlirp mdala kakhulu. Ngexesha ngaphandle kwenkxaso kunye nohlaziyo, abaqulunqi baye bafika ngoku ukuba ngoku esi sixhobo sinokuchazwa kuphela njenge .
Ke, masikhuphele iSlirp kwindawo yokugcina Ubuntu kwaye sizame ukuyiqhuba:
sudo apt-get install slirp
/usr/bin/slirp
Slirp v1.0.17 (BETA)
Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.
IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)
Type five zeroes (0) to exit.
[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]
SLiRP Ready ...
fish: “/usr/bin/slirp” terminated by signal SIGSEGV (Address boundary error)Oh zinkosi zam. Masifake i-debugger ye-Slirp kwaye sibone ukuba singakwazi na ukufumanisa ukuba kuqhubeka ntoni apha:
sudo apt-get install gdb slirp-dbgsym
gdb /usr/bin/slirp
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/slirp...Reading symbols from /usr/lib/debug/.build-id/c6/2e75b69581a1ad85f72ac32c0d7af913d4861f.debug...done.
done.
(gdb) run
Starting program: /usr/bin/slirp
Slirp v1.0.17 (BETA)
Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.
IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)
Type five zeroes (0) to exit.
[autodetect SLIP/CSLIP, MTU 1500, MRU 1500, 115200 baud]
SLiRP Ready ...
Program received signal SIGSEGV, Segmentation fault.
ip_slowtimo () at ip_input.c:457
457 ip_input.c: No such file or directory.Impazamo iyasibetha . Makhe sijonge kwi-stacktrace, mhlawumbi kukho into eya kusinceda apho:
(gdb) bt full
#0 ip_slowtimo () at ip_input.c:457
fp = 0x55784a40
#1 0x000055555556a57c in main_loop () at ./main.c:980
so = <optimized out>
so_next = <optimized out>
timeout = {tv_sec = 0, tv_usec = 0}
ret = 0
nfds = 0
ttyp = <optimized out>
ttyp2 = <optimized out>
best_time = <optimized out>
tmp_time = <optimized out>
#2 0x000055555555b116 in main (argc=1, argv=0x7fffffffdc58) at ./main.c:95
No locals.Apha sibona ukuba ingozi yenzeke ngexesha lokuqaliswa kwe-loop engundoqo, xa i-slirp izama ukujonga ukuphelelwa kwexesha. Kwakulo mzuzu ke apho kwafuneka ndiyeke ukuzama ukulungisa ingxaki. Kodwa masibone ukuba i-Slirp, eyakhiwe ngeentlobo, isebenza. Ndiphinde ndakhuphela indawo yokugcina ngqo kwisiza , kuba ukutsala into ukusuka apho ngelayini yomyalelo yintlungu:
cd ~/dl
wget https://xena.greedo.xeserv.us/files/slirp-1.0.16.tar.gz
tar xf slirp-1.0.16.tar.gz
cd slirp-1.0.16/src
./configure --prefix=$HOME/prefix/slirp
make
Apha sibona izilumkiso malunga nemisebenzi eyakhelwe-ngaphakathi engachazwanga, oko kukuthi, malunga nokungenzeki kokudibanisa isiphumo sefayile yokubini. Kubonakala ngathi phakathi kuka-2006 kwaye ngoku i-gcc iyekile ukwenza iisimboli ezisetyenziswa kwimisebenzi eyakhiweyo ephakathi. Masizame ukutshintsha igama elingundoqo inline kwizimvo ezingenanto kwaye ujonge isiphumo:
vi slirp.h
:6
a
<enter>
#define inline /**/
<escape>
:wq
makeHayi. Oku akusebenzi kwakhona. Awukayifumani imiqondiso yale misebenzi.
Ngelixesha ndancama ndaqala ukukhangela kwi Github . Ithiyori yam yayikukuba iphakheji yokwakha ye-Heroku yayiza kuqulatha iibhinari endizifunayo. Ekugqibeleni, ukukhangela kwam kwandikhokelela . Ndakhuphela ndakhulula uml.tar.gz kwaye ndafumana oku kulandelayo:
total 6136
-rwxr-xr-x 1 cadey cadey 79744 Dec 10 2017 ifconfig*
-rwxr-xr-x 1 cadey cadey 373 Dec 13 2017 init*
-rwxr-xr-x 1 cadey cadey 149688 Dec 10 2017 insmod*
-rwxr-xr-x 1 cadey cadey 66600 Dec 10 2017 route*
-rwxr-xr-x 1 cadey cadey 181056 Jun 26 2015 slirp*
-rwxr-xr-x 1 cadey cadey 5786592 Dec 15 2017 uml*
-rwxr-xr-x 1 cadey cadey 211 Dec 13 2017 uml_run*Le yibhinari etyibilikayo! Ngaba iyasebenza?
./slirp
Slirp v1.0.17 (BETA) FULL_BOLT
Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.
IP address of Slirp host: 127.0.0.1
IP address of your DNS(s): 1.1.1.1, 10.77.0.7
Your address is 10.0.2.15
(or anything else you want)
Type five zeroes (0) to exit.
[autodetect SLIP/CSLIP, MTU 1500, MRU 1500]
SLiRP Ready ...
Ayiwi - ke kufuneka isebenze! Masiyityale le yokubini ~/bin/slirp:
cp slirp ~/bin/slirpKwimeko apho umenzi wephakheji uyayisusa, I .
Ukucwangciswa kwenethiwekhi
Ngoku makhe siqwalasele inethiwekhi kwindawo yethu yeendwendwe. :
linux
root=/dev/root
rootfstype=hostfs
rootflags=$HOME/prefix/uml-demo
rw
mem=64M
eth0=slirp,,$HOME/bin/slirp
init=/bin/shNgoku makhe sivule inethiwekhi:
mount -t proc proc proc/
mount -t sysfs sys sys/
ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2
Imiyalelo emibini yokuqala yoqwalaselo /proc и /sys iyimfuneko emsebenzini ifconfig, emisela ujongano lwenethiwekhi ukunxibelelana neSlirp. Iqela route icwangcisa i kernel yendlela yetafile ukunyanzela zonke itrafikhi zithunyelwe ngapha kwetonela ye Slirp. Masijonge oku ngombuzo weDNS:
nslookup google.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8 dns.google
Name: google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4006:81b::200e lga25s63-in-x0e.1e100.netРаботает!
Inqaku ngalinye: Kuyabonakala ukuba, isithuba sokuqala sabhalwa kwidesktop enekhadi lenethiwekhi enentambo, okanye olunye uqwalaselo olungadingi abaqhubi abongezelelweyo. Kwilaptop ene-WiFi 8265 evela kwi-Intel, kwenzeka impazamo xa kunyuswa inethiwekhi
/ # ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
slirp_tramp failed - errno = 2
ifconfig: ioctl 0x8914 failed: No such file or directory
/ #Kuyabonakala ukuba, i-kernel ayikwazi ukunxibelelana nomqhubi wenethiwekhi. Umzamo wokuqokelela i-firmware kwi-kernel, ngelishwa, ayizange ilungise imeko. Ngexesha lopapasho, akukabikho sisombululo sasinokufunyanwa kolu lungelelwaniso. Kwiinkqubo ezilula (umzekelo, kwi-Virtualbox), ujongano luphakanyiswa ngokuchanekileyo.
Masizenze ulungelelwaniso ngokutsha sisebenzisa iqokobhe elilandelayo elishicilelweyo:
#!/bin/sh
# init.sh
mount -t proc proc proc/
mount -t sysfs sys sys/
ifconfig eth0 10.0.2.14 netmask 255.255.255.240 broadcast 10.0.2.15
route add default gw 10.0.2.2
echo "networking set up"
exec /tini /bin/shKwaye yiphawule njengenokuphunyezwa:
chmod +x init.shKwaye ke masenze utshintsho kumgca womyalelo we-kernel:
linux
root=/dev/root
rootfstype=hostfs
rootflags=$HOME/prefix/uml-demo
rw
mem=64M
eth0=slirp,,$HOME/bin/slirp
init=/init.sh
Kwaye masiphinde:
SLiRP Ready ...
networking set up
/bin/sh: can't access tty; job control turned off
nslookup google.com 8.8.8.8
Server: 8.8.8.8
Address 1: 8.8.8.8 dns.google
Name: google.com
Address 1: 172.217.12.206 lga25s63-in-f14.1e100.net
Address 2: 2607:f8b0:4004:800::200e iad30s09-in-x0e.1e100.netInethiwekhi izinzile!
docker ifayile
Ukwenza kube lula kuwe ukujonga konke oku, ndiqokelele , eyenza ngokuzenzekelayo uninzi lwamanyathelo achaziweyo kwaye kufuneka ikunike uqwalaselo olusebenzayo. Nam ndiyenzile , equlethe yonke into echazwe kwisithuba. Kodwa kubalulekile ukuqonda ukuba apha ndichaze kuphela iisetingi ezincinci.
Ndiyathemba ukuba esi sithuba sikuncede ukuba uqonde indlela yokuvelisa i-kernel yeendwendwe. Kwaba luhlobo oluthile lwe-monster, kodwa upapasho lwenzelwe ukuba ibe sisikhokelo esibanzi malunga nesihloko sokudibanisa, ukufaka kunye nokuqwalasela iNdlela yoMsebenzisi kwi-Linux phantsi kweenguqulelo zanamhlanje zeenkqubo zokusebenza zolu sapho. Amanyathelo alandelayo kufuneka abandakanye ukufakela iinkonzo kunye nenye isoftware esele ingaphakathi kwisixokelelwano seendwendwe. Kuba imifanekiso yesikhongozeli seDocker inyusiwe nje iitarballs, kuya kufuneka ukwazi ukukhupha umfanekiso nge docker export, kwaye emva koko umisele umendo wokuyifakela kwingcambu yenkqubo yefayile ye kernel yondwendwe. Kulungile, emva koko sebenzisa iskripthi seqokobhe.
Umbulelo okhethekileyo ku-Rkeene ovela kwi-#lobster kwi-Freenode. Ngaphandle koncedo lwakhe ekulungiseni iSlirp, ngendingazange ndifikelele apha. Andazi ukuba inkqubo yakhe ye-Slackware isebenza njani ngokuchanekileyo kunye ne-slirp, kodwa iinkqubo zam ze-Ubuntu kunye ne-Alpine azizange zamkele ukutyibilika kwaye iRkeene yokubini indicebise. Kodwa kwanele kum ukuba noko kukho into endisebenzelayo.
umthombo: www.habr.com