vboxguset

VM Deploy Log

  • 설치환경

    • Host OS : Windows 11
    • Vgrant : 2.3.6
    • VirtualBox : 7.0.8
    • vbox : ubuntu/bionic64
  • 설치 로그

C:\Windows\System32>vagrant --version
Vagrant 2.3.6

C:\Windows\System32>d:

D:\>cd certified-kubernetes-administrator-course

D:\certified-kubernetes-administrator-course>vagrant up
Bringing machine 'kubemaster' up with 'virtualbox' provider...
Bringing machine 'kubenode01' up with 'virtualbox' provider...
Bringing machine 'kubenode02' up with 'virtualbox' provider...
==> kubemaster: Box 'ubuntu/bionic64' could not be found. Attempting to find and install...
    kubemaster: Box Provider: virtualbox
    kubemaster: Box Version: >= 0
==> kubemaster: Loading metadata for box 'ubuntu/bionic64'
    kubemaster: URL: https://vagrantcloud.com/ubuntu/bionic64
==> kubemaster: Adding box 'ubuntu/bionic64' (v20230425.0.0) for provider: virtualbox
    kubemaster: Downloading: https://vagrantcloud.com/ubuntu/boxes/bionic64/versions/20230425.0.0/providers/virtualbox.box
Download redirected to host: cloud-images.ubuntu.com
    kubemaster:
==> kubemaster: Successfully added box 'ubuntu/bionic64' (v20230425.0.0) for 'virtualbox'!
==> kubemaster: Importing base box 'ubuntu/bionic64'...
==> kubemaster: Matching MAC address for NAT networking...
==> kubemaster: Setting the name of the VM: kubemaster
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> kubemaster: Clearing any previously set network interfaces...
==> kubemaster: Preparing network interfaces based on configuration...
    kubemaster: Adapter 1: nat
    kubemaster: Adapter 2: hostonly
==> kubemaster: Forwarding ports...
    kubemaster: 22 (guest) => 2711 (host) (adapter 1)
    kubemaster: 22 (guest) => 2222 (host) (adapter 1)
==> kubemaster: Running 'pre-boot' VM customizations...
==> kubemaster: Booting VM...
==> kubemaster: Waiting for machine to boot. This may take a few minutes...
    kubemaster: SSH address: 127.0.0.1:2222
    kubemaster: SSH username: vagrant
    kubemaster: SSH auth method: private key
    kubemaster: Warning: Connection reset. Retrying...
    kubemaster:
    kubemaster: Vagrant insecure key detected. Vagrant will automatically replace
    kubemaster: this with a newly generated keypair for better security.
    kubemaster:
    kubemaster: Inserting generated public key within guest...
    kubemaster: Removing insecure key from the guest if it's present...
    kubemaster: Key inserted! Disconnecting and reconnecting using new SSH key...
==> kubemaster: Machine booted and ready!
==> kubemaster: Checking for guest additions in VM...
    kubemaster: The guest additions on this VM do not match the installed version of
    kubemaster: VirtualBox! In most cases this is fine, but in rare cases it can
    kubemaster: prevent things such as shared folders from working properly. If you see
    kubemaster: shared folder errors, please make sure the guest additions within the
    kubemaster: virtual machine match the version of VirtualBox you have installed on
    kubemaster: your host and reload your VM.
    kubemaster:
    kubemaster: Guest Additions Version: 5.2.42
    kubemaster: VirtualBox Version: 7.0
==> kubemaster: Setting hostname...
==> kubemaster: Configuring and enabling network interfaces...
==> kubemaster: Mounting shared folders...
    kubemaster: /vagrant => D:/certified-kubernetes-administrator-course
==> kubemaster: Running provisioner: setup-hosts (shell)...
    kubemaster: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-b9tws9.sh
==> kubemaster: Running provisioner: setup-dns (shell)...
    kubemaster: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-klh8ae.sh
==> kubenode01: Box 'ubuntu/bionic64' could not be found. Attempting to find and install...
    kubenode01: Box Provider: virtualbox
    kubenode01: Box Version: >= 0
==> kubenode01: Loading metadata for box 'ubuntu/bionic64'
    kubenode01: URL: https://vagrantcloud.com/ubuntu/bionic64
==> kubenode01: Adding box 'ubuntu/bionic64' (v20230425.0.0) for provider: virtualbox
==> kubenode01: Importing base box 'ubuntu/bionic64'...
==> kubenode01: Matching MAC address for NAT networking...
==> kubenode01: Setting the name of the VM: kubenode01
==> kubenode01: Fixed port collision for 22 => 2222. Now on port 2200.
==> kubenode01: Clearing any previously set network interfaces...
==> kubenode01: Preparing network interfaces based on configuration...
    kubenode01: Adapter 1: nat
    kubenode01: Adapter 2: hostonly
==> kubenode01: Forwarding ports...
    kubenode01: 22 (guest) => 2721 (host) (adapter 1)
    kubenode01: 22 (guest) => 2200 (host) (adapter 1)
==> kubenode01: Running 'pre-boot' VM customizations...
==> kubenode01: Booting VM...
==> kubenode01: Waiting for machine to boot. This may take a few minutes...
    kubenode01: SSH address: 127.0.0.1:2200
    kubenode01: SSH username: vagrant
    kubenode01: SSH auth method: private key
    kubenode01: Warning: Connection reset. Retrying...
    kubenode01:
    kubenode01: Vagrant insecure key detected. Vagrant will automatically replace
    kubenode01: this with a newly generated keypair for better security.
    kubenode01:
    kubenode01: Inserting generated public key within guest...
    kubenode01: Removing insecure key from the guest if it's present...
    kubenode01: Key inserted! Disconnecting and reconnecting using new SSH key...
==> kubenode01: Machine booted and ready!
==> kubenode01: Checking for guest additions in VM...
    kubenode01: The guest additions on this VM do not match the installed version of
    kubenode01: VirtualBox! In most cases this is fine, but in rare cases it can
    kubenode01: prevent things such as shared folders from working properly. If you see
    kubenode01: shared folder errors, please make sure the guest additions within the
    kubenode01: virtual machine match the version of VirtualBox you have installed on
    kubenode01: your host and reload your VM.
    kubenode01:
    kubenode01: Guest Additions Version: 5.2.42
    kubenode01: VirtualBox Version: 7.0
==> kubenode01: Setting hostname...
==> kubenode01: Configuring and enabling network interfaces...
==> kubenode01: Mounting shared folders...
    kubenode01: /vagrant => D:/certified-kubernetes-administrator-course
==> kubenode01: Running provisioner: setup-hosts (shell)...
    kubenode01: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-5occf9.sh
==> kubenode01: Running provisioner: setup-dns (shell)...
    kubenode01: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-dpz2ps.sh
==> kubenode02: Box 'ubuntu/bionic64' could not be found. Attempting to find and install...
    kubenode02: Box Provider: virtualbox
    kubenode02: Box Version: >= 0
==> kubenode02: Loading metadata for box 'ubuntu/bionic64'
    kubenode02: URL: https://vagrantcloud.com/ubuntu/bionic64
==> kubenode02: Adding box 'ubuntu/bionic64' (v20230425.0.0) for provider: virtualbox
==> kubenode02: Importing base box 'ubuntu/bionic64'...
==> kubenode02: Matching MAC address for NAT networking...
==> kubenode02: Setting the name of the VM: kubenode02
==> kubenode02: Fixed port collision for 22 => 2222. Now on port 2201.
==> kubenode02: Clearing any previously set network interfaces...
==> kubenode02: Preparing network interfaces based on configuration...
    kubenode02: Adapter 1: nat
    kubenode02: Adapter 2: hostonly
==> kubenode02: Forwarding ports...
    kubenode02: 22 (guest) => 2722 (host) (adapter 1)
    kubenode02: 22 (guest) => 2201 (host) (adapter 1)
==> kubenode02: Running 'pre-boot' VM customizations...
==> kubenode02: Booting VM...
==> kubenode02: Waiting for machine to boot. This may take a few minutes...
    kubenode02: SSH address: 127.0.0.1:2201
    kubenode02: SSH username: vagrant
    kubenode02: SSH auth method: private key
    kubenode02: Warning: Connection reset. Retrying...
    kubenode02:
    kubenode02: Vagrant insecure key detected. Vagrant will automatically replace
    kubenode02: this with a newly generated keypair for better security.
    kubenode02:
    kubenode02: Inserting generated public key within guest...
    kubenode02: Removing insecure key from the guest if it's present...
    kubenode02: Key inserted! Disconnecting and reconnecting using new SSH key...
==> kubenode02: Machine booted and ready!
==> kubenode02: Checking for guest additions in VM...
    kubenode02: The guest additions on this VM do not match the installed version of
    kubenode02: VirtualBox! In most cases this is fine, but in rare cases it can
    kubenode02: prevent things such as shared folders from working properly. If you see
    kubenode02: shared folder errors, please make sure the guest additions within the
    kubenode02: virtual machine match the version of VirtualBox you have installed on
    kubenode02: your host and reload your VM.
    kubenode02:
    kubenode02: Guest Additions Version: 5.2.42
    kubenode02: VirtualBox Version: 7.0
==> kubenode02: Setting hostname...
==> kubenode02: Configuring and enabling network interfaces...
==> kubenode02: Mounting shared folders...
    kubenode02: /vagrant => D:/certified-kubernetes-administrator-course
==> kubenode02: Running provisioner: setup-hosts (shell)...
    kubenode02: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-3yoha0.sh
==> kubenode02: Running provisioner: setup-dns (shell)...
    kubenode02: Running: C:/Users/igoto/AppData/Local/Temp/vagrant-shell20230525-11144-iuod3b.sh

Guest Additions 관련 로그

kubemaster: The guest additions on this VM do not match the installed version of
    kubemaster: VirtualBox! In most cases this is fine, but in rare cases it can
    kubemaster: prevent things such as shared folders from working properly. If you see
    kubemaster: shared folder errors, please make sure the guest additions within the
    kubemaster: virtual machine match the version of VirtualBox you have installed on
    kubemaster: your host and reload your VM.
    kubemaster:
    kubemaster: Guest Additions Version: 5.2.42
    kubemaster: VirtualBox Version: 7.0

VM Setting

kubemaseter

vagrant@kubemaster:~$ ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::3e:6fff:feb6:28d7  prefixlen 64  scopeid 0x20<link>
        ether 02:3e:6f:b6:28:d7  txqueuelen 1000  (Ethernet)
        RX packets 1487  bytes 196227 (196.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1036  bytes 182475 (182.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.56.2  netmask 255.255.255.0  broadcast 192.168.56.255
        inet6 fe80::a00:27ff:fe7d:8cd9  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:7d:8c:d9  txqueuelen 1000  (Ethernet)
        RX packets 1  bytes 243 (243.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 936 (936.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 16  bytes 1532 (1.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16  bytes 1532 (1.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vagrant@kubemaster:~$ hostname
kubemaster
vagrant@kubemaster:~$ lsmod | grep vboxguest
vboxguest             294912  2 vboxsf
vagrant@kubemaster:~$ /sbin/modinfo vboxguest
filename:       /lib/modules/4.15.0-210-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
version:        5.2.8_KernelUbuntu r120774
license:        GPL
description:    Oracle VM VirtualBox Guest Additions for Linux Module
author:         Oracle Corporation
srcversion:     F2E5886E3B0544500D404A1
alias:          pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i*
depends:
retpoline:      Y
intree:         Y
name:           vboxguest
vermagic:       4.15.0-210-generic SMP mod_unload modversions
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4

kubenode01

vagrant@kubenode01:~$ hostname
kubenode01
vagrant@kubenode01:~$ ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
        inet6 fe80::3e:6fff:feb6:28d7  prefixlen 64  scopeid 0x20<link>
        ether 02:3e:6f:b6:28:d7  txqueuelen 1000  (Ethernet)
        RX packets 1428  bytes 193049 (193.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1058  bytes 186276 (186.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.56.3  netmask 255.255.255.0  broadcast 192.168.56.255
        inet6 fe80::a00:27ff:fe40:fef4  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:40:fe:f4  txqueuelen 1000  (Ethernet)
        RX packets 1  bytes 243 (243.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 13  bytes 1006 (1.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 16  bytes 1532 (1.5 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16  bytes 1532 (1.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vagrant@kubenode01:~$ lsmod | grep vboxguest
vboxguest             294912  2 vboxsf
vagrant@kubenode01:~$ /sbin/modinfo vboxguest
filename:       /lib/modules/4.15.0-210-generic/kernel/ubuntu/vbox/vboxguest/vboxguest.ko
version:        5.2.8_KernelUbuntu r120774
license:        GPL
description:    Oracle VM VirtualBox Guest Additions for Linux Module
author:         Oracle Corporation
srcversion:     F2E5886E3B0544500D404A1
alias:          pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i*
depends:
retpoline:      Y
intree:         Y
name:           vboxguest
vermagic:       4.15.0-210-generic SMP mod_unload modversions
signat:         PKCS#7
signer:
sig_key:
sig_hashalgo:   md4

kubenode03


igotoo

igotoo