Atualização para Criadores do Windows 10 Fall e Virtual Box / Homestead congela o PC

Question

Alguma dica de onde mais também parece pls? Eu estou procurando por isso ainda, mas não encontrei nada que tenha ajudado. Obrigado

Acabei de atualizar a atualização do Win 10 to Fall Creator. Meu ambiente do VirtualBox parou de funcionar e exigiria que o PC fosse inicializado a frio.

Acabei de atualizar o pacote de extensão do Virtualbox + e o Homestead / Vagrant para as versões mais recentes para tentar corrigir esse problema, mas o resultado é o mesmo. Tudo tem funcionado até este ponto por cerca de 2 anos.

Minhas configurações de rede são:

Adapter 1: NAT
Adapter 2: Bridged Adapter
           Killer Ethernet Controller
           PCnet-FAST III (Am79C973)
           Allow All
           Cable Connected -> yes

Se eu iniciar minha caixa homestead-7 do Virtualbox de uma janela bash, o resultado será o mesmo. O PC congela e requer uma inicialização a frio.

Meu arquivo VBoxSVC.log contém:

VirtualBox COM Server 5.2.0 r118431 win.amd64 (Oct 18 2017 06:24:56) release log
00:00:00.000000 main     Log opened 2017-11-21T06:44:33.784520500Z
00:00:00.000000 main     Build Type: release
00:00:00.000000 main     OS Product: Windows 10
00:00:00.000000 main     OS Release: 10.0.16299
00:00:00.000000 main     OS Service Pack: 
00:00:00.015627 main     DMI Product Name: Default string
00:00:00.015627 main     DMI Product Version: Default string
00:00:00.015627 main     Host RAM: 16221MB (15.8GB) total, 11734MB (11.4GB) available
00:00:00.015627 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.015627 main     Process ID: 6164
00:00:00.015627 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.015627          VirtualBox: object creation starts
00:00:00.015627          Home directory: 'C:\Users\PAPA\.VirtualBox'
00:00:00.015627          Installed Drivers:
00:00:00.015627            C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.2.0.18431)
00:00:00.015627            C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.2.0.18431)
00:00:00.015627            C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.2.0.18431)
00:00:00.015627            C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys (Version: 5.2.0.18431)
00:00:00.015627          Loading settings file "C:\Users\PAPA\.VirtualBox\VirtualBox.xml" with version "1.14-windows"
00:00:00.184485          netIfIsWireless: CreateFile on '\.\{21AD0D25-56F5-4F8A-8CB4-C922101B864A}' failed with rcWin=2 (0x2) - ignoring
00:00:00.184485          HostDnsMonitor: old information
00:00:00.184485            no server entries
00:00:00.184485            no domain set
00:00:00.184485            no search string entries
00:00:00.184485          HostDnsMonitor: new information
00:00:00.184485            server 1: 10.0.0.1
00:00:00.184485            domain: NHOME
00:00:00.184485            no search string entries
00:00:00.184485          HostDnsMonitorProxy::notify
00:00:00.231360          VD: VDInit finished with VINF_SUCCESS
00:00:00.231360          Loading settings file "F:\!! - VB VMs\Ansible Wordpress\Ansible Wordpress.vbox" with version "1.15-windows"
00:00:00.231360          Loading settings file "F:\!! - VB VMs\Ansible Wordpress Backup\Ansible Wordpress Backup.vbox" with version "1.15-windows"
00:00:00.231360          Loading settings file "F:\!! - VB VMs\Ansible Wordpress Target Test - MAIN\Ansible Wordpress Target Test - MAIN.vbox" with version "1.15-windows"
00:00:00.246985          Loading settings file "F:\!! - VB VMs\Ansible Wordpress Target Test - MAIN Clone\Ansible Wordpress Target Test - MAIN Clone.vbox" with version "1.15-windows"
00:00:00.247220          Loading settings file "F:\!! - VB VMs\FreePBX\FreePBX.vbox" with version "1.15-windows"
00:00:00.247729          Loading settings file "F:\!! - VB VMs\homestead-7\homestead-7.vbox" with version "1.15-windows"
00:00:00.257721          VirtualBox: object created

Quando fecho o Virtualbox, isso é adicionado ao log:

00:00:00.391990          netIfIsWireless: CreateFile on '\.\{21AD0D25-56F5-4F8A-8CB4-C922101B864A}' failed with rcWin=2 (0x2) - ignoring
00:00:03.161576          Saving settings file "C:\Users\PAPA\.VirtualBox\VirtualBox.xml" with version "1.14-windows"
00:00:03.177207          Saving settings file "C:\Users\PAPA\.VirtualBox\VirtualBox.xml" with version "1.14-windows"
00:00:08.700473 main     VirtualBox: object deletion starts
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\Ansible Wordpress\Ansible Wordpress.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\Ansible Wordpress Backup\Ansible Wordpress Backup.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\Ansible Wordpress Target Test - MAIN\Ansible Wordpress Target Test Clone.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\Ansible Wordpress Target Test - MAIN Clone\Ansible Wordpress Target Test - MAIN Clone-disk1.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\FreePBX\FreePBX-disk1_1.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\!! - VB VMs\homestead-7\box-disk1.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:00:08.700473 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:00:08.700473 main     VirtualBox: object deleted

Eu não entendo quais são os erros VBOX_E_OBJECT_IN_USE , pois o log mostrado acima é gerado simplesmente abrindo e fechando o Virtualbox (sem iniciar uma caixa).

Qualquer ideia / ajuda é muito apreciada.

    

Answer 1

OK, então alguns dias depois e mais queda de cabelo, aqui está o que eu encontrei:

O problema de congelamento foi HYPER-V em Windows 10 . Eu suponho que isso aconteceu devido à Atualização do Criador de Outono.

Abra o menu Iniciar e digite:

windows features

Em seguida, desmarque HYPER-V . Isso exigirá uma reinicialização. Isso parou o congelamento do PC e exigiu uma inicialização a frio.

No meu caso, eu atualizei o Virtualbox , Vagrant , então meu próximo problema foi:

ssh auth method private key timeout

durante a inicialização da VM. Para resolver isso eu fiz:

vagrant destroy
vagrant up

Você precisará executar novamente migrações e sementes para restaurar seus dados.