virtualbox 설치오류

Question

에러내용 이 버전의 macOS에서는 이 버전의 'VirtualBox.app' 응용 프로그램을 사용할 수 없습니다. 현재 버전은 'VirtualBox.app' 5.2.2입니다. 사양 macOS Mojave 10.14.6 조치 ctl.sh 안에 vm version을 6.0바꿔서 했는데도 문제가 되서, 기존에 설치된 vm제거하고 하니, 정상 설치되네요. 영상에서는 기존버전 있어도 문제 없다고 해서 실행 했거든요 ;;

Ralf Yang · Answer

https://www.inflearn.com/questions/12425 위 링크와 같이 답변을 등록 해 두었으니 참고 부탁 드립니다 :)

stallon · Answer

MacOS Catalina에서 실습 중인데, virtualbox 6.1.4, vagrant 2.2.7로 변경하여 진행하고 있습니다. 5.x 대는 Catalina와 궁합이 안맞는 것 같아요. 그런데, vbox + vagrant 설치는 문제가 없는데, ctl.sh에서 Start VM & login을 실행하면 아래와 같이 진행 중에 Guest Addition이 Host에 설치된 Virtualbox와 버전이 안 맞는다는 경고가 뜨고, VM 생성이 성공하기도 실패하기도 합니다. 저의 경우는 docker00.dev는 생성되어 로그인까지 되었고, docker01.dev부터는 virtualbox가 작업 도중에 크래시가 나서 종료됩니다. 아래는 에러 로그입니다. updated: 아 바로 옆 질문에 아래와 같이 버전 미스매치에 대한 오류 로그와 현상이 동일하게 여러분이 언급하고 계시네요. 그냥 참고하시면 되겠습니다. -------- =========================================================== What do you want ? =========================================================== [0] Install the Virtualbox & Vagrant [1] Start VM & login [2] Login to VM [3] Stop VM [4] Reload VM [5] Reboot VM [RM] Remove VM =========================================================== Please insert a key as you need = 1 =========================================================== Bringing machine 'docker01.dev' up with 'virtualbox' provider... ==> docker01.dev: Importing base box 'folimy/Ubuntu1604_with_docker'... ==> docker01.dev: Matching MAC address for NAT networking... ==> docker01.dev: Setting the name of the VM: vagrant_docker_cluster_docker01dev_1584279201875_79335 ==> docker01.dev: Fixed port collision for 22 => 2222. Now on port 2200. ==> docker01.dev: Clearing any previously set network interfaces... ==> docker01.dev: Preparing network interfaces based on configuration... docker01.dev: Adapter 1: nat docker01.dev: Adapter 2: hostonly docker01.dev: Adapter 3: hostonly docker01.dev: Adapter 4: hostonly docker01.dev: Adapter 5: hostonly docker01.dev: Adapter 6: hostonly docker01.dev: Adapter 7: hostonly docker01.dev: Adapter 8: hostonly docker01.dev: Adapter 9: hostonly docker01.dev: Adapter 10: hostonly docker01.dev: Adapter 11: hostonly ==> docker01.dev: Forwarding ports... docker01.dev: 22 (guest) => 2200 (host) (adapter 1) ==> docker01.dev: Running 'pre-boot' VM customizations... ==> docker01.dev: Booting VM... ==> docker01.dev: Waiting for machine to boot. This may take a few minutes... docker01.dev: SSH address: 127.0.0.1:2200 docker01.dev: SSH username: vagrant docker01.dev: SSH auth method: private key docker01.dev: docker01.dev: Vagrant insecure key detected. Vagrant will automatically replace docker01.dev: this with a newly generated keypair for better security. docker01.dev: docker01.dev: Inserting generated public key within guest... docker01.dev: Removing insecure key from the guest if it's present... docker01.dev: Key inserted! Disconnecting and reconnecting using new SSH key... ==> docker01.dev: Machine booted and ready! ==> docker01.dev: Checking for guest additions in VM... docker01.dev: The guest additions on this VM do not match the installed version of docker01.dev: VirtualBox! In most cases this is fine, but in rare cases it can docker01.dev: prevent things such as shared folders from working properly. If you see docker01.dev: shared folder errors, please make sure the guest additions within the docker01.dev: virtual machine match the version of VirtualBox you have installed on docker01.dev: your host and reload your VM. docker01.dev: docker01.dev: Guest Additions Version: 5.2.6 docker01.dev: VirtualBox Version: 6.1 ==> docker01.dev: Setting hostname... ==> docker01.dev: Configuring and enabling network interfaces... ==> docker01.dev: Forcing shutdown of VM... ==> docker01.dev: Destroying VM and associated drives... /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:126:in `[]': no implicit conversion from nil to integer (TypeError) from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:126:in `block in configure_nettools' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:125:in `each' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:125:in `configure_nettools' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/guests/debian/cap/configure_networks.rb:28:in `configure_networks' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/capability_host.rb:111:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/capability_host.rb:111:in `capability' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/guest.rb:43:in `capability' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/network.rb:134:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/warden.rb:57:in `call' from /opt/vagrant/embedded/gems/2.2.7/gems/vagrant-2.2.7/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/

Ralf Yang · Answer

> 조치 > ctl.sh 안에 vm version을 6.0바꿔서 했는데도 문제가 되서, 기존에 설치된 vm제거하고 하니, 정상 설치되네요. 아! 네 제가 확인이 늦었네요.. ㅠㅠ 최근 VirtualBox 에서 해당 문제가 자주 일어나네요... 조치 하신 상황처럼 재설치하는 방법이 가장 좋다고 합니다. 미리 말씀 주셔서 감사합니다! :)