launchctl-load-vmware-utility 에러

Question

(base) ryanchoi@Byungsoos-MBP 2.4 % launchctl-load-vmware-utility   Load failed: 5: Input/output error Try running launchctl bootstrap as root for richer errors. 이런 에러가 발생해서, sudo 를 써봐도 해결이 안되는데, 혹시 어떻게 해결할 수 있을까요?   ***** 추가 (base) ryanchoi@Byungsoos-MBP k8s % vagrant up Bringing machine 'cp-k8s-1.30.0' up with 'vmware_desktop' provider... Bringing machine 'w1-k8s-1.30.0' up with 'vmware_desktop' provider... Bringing machine 'w2-k8s-1.30.0' up with 'vmware_desktop' provider... Bringing machine 'w3-k8s-1.30.0' up with 'vmware_desktop' provider... ==> cp-k8s-1.30.0: Box 'sysnet4admin/Ubuntu-k8s' could not be found. Attempting to find and install...     cp-k8s-1.30.0: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation     cp-k8s-1.30.0: Box Version: >= 0 ==> cp-k8s-1.30.0: Loading metadata for box 'sysnet4admin/Ubuntu-k8s'     cp-k8s-1.30.0: URL: https://vagrantcloud.com/api/v2/vagrant/sysnet4admin/Ubuntu-k8s ==> cp-k8s-1.30.0: Adding box 'sysnet4admin/Ubuntu-k8s' (v0.8.5) for provider: vmware_desktop (arm64)     cp-k8s-1.30.0: Downloading: https://vagrantcloud.com/sysnet4admin/boxes/Ubuntu-k8s/versions/0.8.5/providers/vmware_desktop/arm64/vagrant.box Progress: 93% (Rate: 13.2M/s, Estimated time remaining: 0:00:04)^R ==> cp-k8s-1.30.0: Successfully added box 'sysnet4admin/Ubuntu-k8s' (v0.8.5) for 'vmware_desktop (arm64)'! ==> cp-k8s-1.30.0: Cloning VMware VM: 'sysnet4admin/Ubuntu-k8s'. This can take some time... ==> cp-k8s-1.30.0: Checking if box 'sysnet4admin/Ubuntu-k8s' version '0.8.5' is up to date... ==> cp-k8s-1.30.0: Verifying vmnet devices are healthy... The VMware "vmnet" devices are failing to start. The most common reason for this is collisions with existing network services. For example, if a hostonly network space collides with another hostonly network (such as with VirtualBox), it will fail to start. Likewise, if forwarded ports collide with other listening ports, it will fail to start.   Vagrant does its best to fix these issues, but in some cases it cannot determine the root cause of these failures.   Please verify you have no other colliding network services running. As a last resort, restarting your computer often fixes this issue. 이런 에러가 뜨는 건 launchctl-load-vmware-utility 이 부분 명령어가 제대로 처리가 안되어서 그런거죠?

조훈(Hoon Jo) · Answer

안녕하세요 sudo는 이미 포함되어 있어서요... launchctl-reload-vmware-utility 명령을 쓰셔도 동일하신가요? 기존에 설정 또는 다른 설정이 있어서 그런거 같기도 해서요.   베이그런트 에러 로그만 가지고 어떤 문제가 원인이다는 정확하게 알기 어렵습니다. 호스트 설정과 진행했던 내용 그리고 그에 따른 실행 결과들을 다 살펴봐야 해서요.   우선 랩탑을 다시 시작한 이후에 위의 명령을 포함한 다른 명령을 순서대로 실행해 보고 알려주실 수 있을까요?