Win 10 guest on Ubuntu host stops working (black screen) after running a while

Discussions about using Windows guests in VirtualBox.
Post Reply
Igfoo
Posts: 4
Joined: 16. Mar 2021, 14:44

Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by Igfoo »

Hi folks,

On my x86_64 Ubuntu host, "VBoxManage --version" says 6.1.16_Ubuntur140961. I have a Windows 10 64bit guest, and in "Machine/Session Information/Runtime Information" it says "Guest Additions 6.1.16 r140961". The host has 32GB RAM, and the guest has been given 16GB.

If I start the VM then everything appears to be fine. However, if I then start a large "git clone" command running in a shared folder, then after a while the VM stops working: The screen is black and it appears to not respond to anything. When I notice this has happened, the last line in the log is "00:34:10.277761 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago"

Searching the forums, I only found people with this black screen problem at startup. However, I nevertheless tried the advice there: I increased the video RAM to maximum (128M), and when the screen had gone black I tried resizing the window. Neither seems to have helped.

According to "Machine/Session Information/Performance Monitor", the guest load is 96% (VM load approx 3%) and "VM Exits" is around 17k; I've attached a screenshot in case it is helpful.

Does anyone have any idea what the problem is please?

And please let me know if more information would be useful.


Thanks
Ian
Attachments
vbox.png
vbox.png (79 KiB) Viewed 2905 times
VBox_log.zip
(33.25 KiB) Downloaded 16 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by scottgus1 »

I don't see anything egregiously wrong with the setup or the running of the VM up to the 'heartbeat flatline' log entry. The VM environment continues running.

Check inside the VM's OS to see if it has any messages in the Event Viewer.
Igfoo
Posts: 4
Joined: 16. Mar 2021, 14:44

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by Igfoo »

OK, I've done a little experimentation, and it looks like shared folders may be key to the problem.

I did (in msys)

Code: Select all

cd /c/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
(i.e. in c:\ian, on the virtual disk) and it ran without problem for an hour.

I then did

Code: Select all

cd /s/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
(i.e. in s:\ian, on the shared drive). This had random errors as it ran, e.g.

Code: Select all

19 Mar 2021 23:11:54
19 Mar 2021 23:11:54
19 Mar 2021 23:11:55
rm: cannot remove 'vs_enterprise__1421815813.1615828398.exe': Permission denied
19 Mar 2021 23:11:55
rm: cannot remove 'msys2-x86_64-20210228.exe': Permission denied
19 Mar 2021 23:11:55
19 Mar 2021 23:11:55
and after approx 10 mins the VM rebooted, with "19 Mar 2021 23:19:59" being the last date printed. This corresponded to this error and vmmDevHeartbeatFlatlinedTimer in the log (full log also attached as VBox_log2.zip):

Code: Select all

01:03:04.964042 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:03:06.019860 VMMDev: Guest Log: VBOXNP: DLL loaded.
01:03:06.104235 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:05:37.831856 VMMDev: Guest Additions capability report: (0x5 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
01:05:37.832050 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
01:05:37.832076 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
01:05:37.832092 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
01:05:37.832095 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
01:05:37.940386 VMMDev: Guest Additions capability report: (0x0 -> 0x1) seamless: yes, hostWindowMapping: no, graphics: no
01:05:37.940571 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
01:05:37.940584 VMMDev: Guest Additions capability report: (0x1 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
01:05:37.940595 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
01:05:37.940634 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
01:05:37.940637 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
01:05:37.940656 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners
01:05:37.940673 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary
01:05:37.940677 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners
01:05:37.940679 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
01:08:12.227993 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f467c000000 w=1269 h=768 bpp=32 cbLine=0x13D4 flags=0x1 origin=0,0
01:09:09.050964 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f467c000000 w=1269 h=768 bpp=32 cbLine=0x13D4 flags=0xD origin=0,0
01:09:09.051198 GUI: UIFrameBufferPrivate::performResize: Size=1269x768, Using fallback buffer since no source bitmap is provided
01:10:41.742030 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f467c000000 w=1269 h=768 bpp=32 cbLine=0x13D4 flags=0x1 origin=0,0
01:11:39.474489 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f467c000000 w=1269 h=768 bpp=32 cbLine=0x13D4 flags=0xD origin=0,0
01:11:39.474568 GUI: UIFrameBufferPrivate::performResize: Size=1269x768, Using fallback buffer since no source bitmap is provided
01:18:17.642115 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8022aed9020 P3=0x0 P4=0xffffffffffffffff
01:18:17.642194 GIMHv: BugCheck 1e {ffffffffc0000005, fffff8022aed9020, 0, ffffffffffffffff}
01:18:17.642195 KMODE_EXCEPTION_NOT_HANDLED
01:18:17.642195 P1: ffffffffc0000005 - exception code - STATUS_ACCESS_VIOLATION
01:18:17.642195 P2: fffff8022aed9020 - EIP/RIP
01:18:17.642195 P3: 0000000000000000 - Xcpt param #0
01:18:17.642195 P4: ffffffffffffffff - Xcpt param #1
01:18:20.515191 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
01:18:21.244762 AHCI#0: Reset the HBA
01:18:21.244775 VD#0: Cancelling all active requests
01:18:21.245069 AHCI#0: Port 0 reset
01:18:21.246113 VD#0: Cancelling all active requests
01:18:31.654788 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e P1=0xffffffffc0000005 P2=0xfffff8022aed9020 P3=0x0 P4=0xffffffffffffffff
01:18:31.654944 GIM: HyperV: Reset initiated through MSR
01:18:31.654962 Changing the VM state from 'RUNNING' to 'RESETTING'
01:18:31.657991 GIM: HyperV: Resetting MMIO2 regions and MSRs
01:18:31.658051 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
01:18:31.658162 Shared Clipboard: Stopping X11 event thread ...
01:18:31.658191 Shared Clipboard: X11 event thread terminated successfully
01:18:31.658554 VMMDevNotifyGuest: fAddEvents=0x1 ignored because enmVMState=8
01:18:31.658696 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007f467c000000 w=640 h=480 bpp=0 cbLine=0x140 flags=0x0 origin=0,0
I'm not familiar with the event viewer, but there didn't seem to be any obvious errors in there. Using this view:

Code: Select all

<ViewerConfig><QueryConfig><QueryParams><Simple><RelativeTimeInfo>6</RelativeTimeInfo><BySource>False</BySource><Channel>Application,Security,Setup,System,ForwardedEvents</Channel><FromDate>637517922000000000</FromDate><ToDate>637517970009990000</ToDate><Level>1,2,3,4,0,5</Level></Simple></QueryParams><QueryNode><Name>Ian view</Name><QueryList><Query Id="0" Path="Application"><Select Path="Application">*[System[(Level=1  or Level=2 or Level=3 or Level=4 or Level=0 or Level=5) and TimeCreated[@SystemTime>='2021-03-19T23:10:00.000Z' and @SystemTime<='2021-03-20T00:30:00.999Z']]]</Select><Select Path="Security">*[System[(Level=1  or Level=2 or Level=3 or Level=4 or Level=0 or Level=5) and TimeCreated[@SystemTime>='2021-03-19T23:10:00.000Z' and @SystemTime<='2021-03-20T00:30:00.999Z']]]</Select><Select Path="Setup">*[System[(Level=1  or Level=2 or Level=3 or Level=4 or Level=0 or Level=5) and TimeCreated[@SystemTime>='2021-03-19T23:10:00.000Z' and @SystemTime<='2021-03-20T00:30:00.999Z']]]</Select><Select Path="System">*[System[(Level=1  or Level=2 or Level=3 or Level=4 or Level=0 or Level=5) and TimeCreated[@SystemTime>='2021-03-19T23:10:00.000Z' and @SystemTime<='2021-03-20T00:30:00.999Z']]]</Select><Select Path="ForwardedEvents">*[System[(Level=1  or Level=2 or Level=3 or Level=4 or Level=0 or Level=5) and TimeCreated[@SystemTime>='2021-03-19T23:10:00.000Z' and @SystemTime<='2021-03-20T00:30:00.999Z']]]</Select></Query></QueryList></QueryNode></QueryConfig><ResultsConfig><Columns><Column Name="Level" Type="System.String" Path="Event/System/Level" Visible="">163</Column><Column Name="Keywords" Type="System.String" Path="Event/System/Keywords">70</Column><Column Name="Date and Time" Type="System.DateTime" Path="Event/System/TimeCreated/@SystemTime" Visible="">213</Column><Column Name="Source" Type="System.String" Path="Event/System/Provider/@Name" Visible="">123</Column><Column Name="Event ID" Type="System.UInt32" Path="Event/System/EventID" Visible="">123</Column><Column Name="Task Category" Type="System.String" Path="Event/System/Task" Visible="">123</Column><Column Name="User" Type="System.String" Path="Event/System/Security/@UserID">50</Column><Column Name="Operational Code" Type="System.String" Path="Event/System/Opcode">110</Column><Column Name="Log" Type="System.String" Path="Event/System/Channel">80</Column><Column Name="Computer" Type="System.String" Path="Event/System/Computer">170</Column><Column Name="Process ID" Type="System.UInt32" Path="Event/System/Execution/@ProcessID">70</Column><Column Name="Thread ID" Type="System.UInt32" Path="Event/System/Execution/@ThreadID">70</Column><Column Name="Processor ID" Type="System.UInt32" Path="Event/System/Execution/@ProcessorID">90</Column><Column Name="Session ID" Type="System.UInt32" Path="Event/System/Execution/@SessionID">70</Column><Column Name="Kernel Time" Type="System.UInt32" Path="Event/System/Execution/@KernelTime">80</Column><Column Name="User Time" Type="System.UInt32" Path="Event/System/Execution/@UserTime">70</Column><Column Name="Processor Time" Type="System.UInt32" Path="Event/System/Execution/@ProcessorTime">100</Column><Column Name="Correlation Id" Type="System.Guid" Path="Event/System/Correlation/@ActivityID">85</Column><Column Name="Relative Correlation Id" Type="System.Guid" Path="Event/System/Correlation/@RelatedActivityID">140</Column><Column Name="Event Source Name" Type="System.String" Path="Event/System/Provider/@EventSourceName">140</Column></Columns></ResultsConfig></ViewerConfig>
around the time of the reboot the logs were:

Code: Select all

Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,32,(58),The bootmgr spent 0 ms waiting for user input.
Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,18,(57),There are 0x1 boot options on this system.
Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,27,(33),The boot type was 0x0.
Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,25,(32),The boot menu policy was 0x1.
Error,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,124,(80),The virtualization-based security enablement policy check at phase 0 failed with status: The request is not supported.
Error,19/03/2021 23:20:22,Microsoft-Windows-Hyper-V-Hypervisor,41,None,Hypervisor launch failed; Either VMX not present or not enabled in BIOS.
Information,19/03/2021 23:20:32,EventLog,6013,None,The system uptime is 10 seconds.
Information,19/03/2021 23:20:32,EventLog,6005,None,The Event log service was started.
Information,19/03/2021 23:20:32,EventLog,6009,None,Microsoft (R) Windows (R) 10.00. 19042  Multiprocessor Free.
Error,19/03/2021 23:20:32,EventLog,6008,None,The previous system shutdown at 22:42:07 on 19/03/2021 was unexpected.
Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,20,(31),The last shutdown's success status was false. The last boot's success status was true.
Warning,19/03/2021 23:20:22,Microsoft-Windows-Kernel-Boot,156,None,"Virtualization-based security (policies: VBS Enabled,VSM Required,Boot Chain Signer Soft Enforced) is disabled due to VBS initialization failure with status: The request is not supported."
Information,19/03/2021 23:20:22,Microsoft-Windows-Kernel-General,12,(1),The operating system started at system time 2021-03-19T23:20:22.500000000Z.
Information,19/03/2021 23:19:01,Microsoft-Windows-Security-Auditing,4670,Authorization Policy Change,"Permissions on an object were changed.

Subject:
    Security ID:        SYSTEM
    Account Name:       DESKTOP-TNKF00T$
    Account Domain:     WORKGROUP
    Logon ID:       0x3E7

Object:
    Object Server:  Security
    Object Type:    Token
    Object Name:    -
    Handle ID:  0x2124

Process:
    Process ID: 0xa50
    Process Name:   C:\Windows\System32\svchost.exe

Permissions Change:
    Original Security Descriptor:   D:(A;;GA;;;SY)(A;;GA;;;NS)
    New Security Descriptor:    D:(A;;GA;;;SY)(A;;RC;;;OW)(A;;GA;;;S-1-5-86-615999462-62705297-2911207457-59056572-3668589837)"
Information,19/03/2021 23:18:54,Microsoft-Windows-Security-Auditing,4946,MPSSVC Rule-Level Policy Change,"A change was made to the Windows Firewall exception list. A rule was added.

Profile Changed:    All

Added Rule:
    Rule ID:    {A0E7A8EA-72B3-44E1-B482-6FF6C6969AFA}
    Rule Name:  LpacSenseNdr"
Information,19/03/2021 23:18:54,Microsoft-Windows-Security-Auditing,4946,MPSSVC Rule-Level Policy Change,"A change was made to the Windows Firewall exception list. A rule was added.

Profile Changed:    All

Added Rule:
    Rule ID:    {2A1BE447-38D8-45F9-BEE5-6E52836F96D2}
    Rule Name:  LpacSenseNdr"
Information,19/03/2021 23:18:54,Microsoft-Windows-Security-Auditing,4948,MPSSVC Rule-Level Policy Change,"A change was made to the Windows Firewall exception list. A rule was deleted.

Profile Changed:    All

Deleted Rule:
    Rule ID:    {06638BE4-229C-4199-ADD8-A427AEFBE56C}
    Rule Name:  LpacSenseNdr"
Information,19/03/2021 23:18:54,Microsoft-Windows-Security-Auditing,4948,MPSSVC Rule-Level Policy Change,"A change was made to the Windows Firewall exception list. A rule was deleted.

Profile Changed:    All

Deleted Rule:
    Rule ID:    {A6DE822A-7B27-4770-AE4E-BDED0A7C4ED9}
    Rule Name:  LpacSenseNdr"
Information,19/03/2021 23:18:46,Microsoft-Windows-Security-Auditing,4957,MPSSVC Rule-Level Policy Change,"Windows Firewall did not apply the following rule:

Rule Information:
    ID: PlayTo-QWave-In-TCP-PlayToScope
    Name:   Cast to Device functionality (qWave-TCP-In)

Error Information:
    Reason: Remote Addresses resolved to an empty set."
and a little later:

Code: Select all

Error,19/03/2021 23:20:46,Microsoft-Windows-WER-SystemErrorReporting,1001,None,"The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8022aed9020, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: aaa5247c-2470-4b0f-b43e-1d8499992fb5."
After it rebooted, I reran

Code: Select all

cd /s/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
getting the same random permissions errors, and then the VM stopped responding as in my original post. The log (part of the same attached log) corresponding to this is

Code: Select all

01:56:58.470287 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:56:59.406491 VMMDev: Guest Log: VBOXNP: DLL loaded.
01:56:59.494596 VMMDev: Guest Log: VBOXNP: DLL unloaded.
01:59:07.085812 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
02:57:33.663244 Console: Machine state changed to 'Stopping'
02:57:33.663570 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)
02:57:33.664410 Changing the VM state from 'RUNNING' to 'POWERING_OFF'
and the last events are

Code: Select all

Level,Date and Time,Source,Event ID,Task Category
Information,19/03/2021 23:58:53,Microsoft-Windows-Security-Auditing,4670,Authorization Policy Change,"Permissions on an object were changed.

Subject:
    Security ID:        SYSTEM
    Account Name:       DESKTOP-TNKF00T$
    Account Domain:     WORKGROUP
    Logon ID:       0x3E7

Object:
    Object Server:  Security
    Object Type:    Token
    Object Name:    -
    Handle ID:  0x7f8

Process:
    Process ID: 0xa90
    Process Name:   C:\Windows\System32\svchost.exe

Permissions Change:
    Original Security Descriptor:   D:(A;;GA;;;SY)(A;;GA;;;NS)
    New Security Descriptor:    D:(A;;GA;;;SY)(A;;RC;;;OW)(A;;GA;;;S-1-5-86-615999462-62705297-2911207457-59056572-3668589837)"
Information,19/03/2021 23:58:23,Microsoft-Windows-Security-SPP,16384,None,Successfully scheduled Software Protection service for re-start at 2021-03-20T23:57:23Z. Reason: RulesEngine.
Information,19/03/2021 23:58:23,Microsoft-Windows-Security-Auditing,4702,Other Object Access Events,"A scheduled task was updated.

Subject:
    Security ID:        NETWORK SERVICE
    Account Name:       DESKTOP-TNKF00T$
    Account Domain:     WORKGROUP
    Logon ID:       0x3E4

Task Information:
    Task Name:      \Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
    Task New Content:       <?xml version=""1.0"" encoding=""UTF-16""?>
<Task version=""1.6"" xmlns=""http://schemas.microsoft.com/windows/2004/02/mit/task"">
  <RegistrationInfo>
    <Source>$(@%systemroot%\system32\sppc.dll,-200)</Source>
    <Author>$(@%systemroot%\system32\sppc.dll,-200)</Author>
    <Version>1.0</Version>
    <Description>$(@%systemroot%\system32\sppc.dll,-201)</Description>
    <URI>\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask</URI>
    <SecurityDescriptor>D:P(A;;FA;;;SY)(A;;FA;;;BA)(A;;FA;;;S-1-5-80-123231216-2592883651-3715271367-3753151631-4175906628)(A;;FR;;;S-1-5-87-2912274048-3994893941-1669128114-1310430903-1263774323)</SecurityDescriptor>
  </RegistrationInfo>
  <Triggers>
    <CalendarTrigger>
      <StartBoundary>2021-03-20T23:57:23Z</StartBoundary>
      <Enabled>true</Enabled>
      <ScheduleByDay>
        <DaysInterval>1</DaysInterval>
      </ScheduleByDay>
    </CalendarTrigger>
  </Triggers>
  <Principals>
    <Principal id=""NetworkService"">
      <UserId>S-1-5-20</UserId>
      <RunLevel>LeastPrivilege</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>false</StopIfGoingOnBatteries>
    <AllowHardTerminate>false</AllowHardTerminate>
    <StartWhenAvailable>true</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <IdleSettings>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>true</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>
    <UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
    <Priority>7</Priority>
    <RestartOnFailure>
      <Interval>PT1M</Interval>
      <Count>3</Count>
    </RestartOnFailure>
  </Settings>
  <Actions Context=""NetworkService"">
    <ComHandler>
      <ClassId>{B1AEBB5D-EAD9-4476-B375-9C3ED9F32AFC}</ClassId>
      <Data><![CDATA[timer]]></Data>
    </ComHandler>
  </Actions>
</Task>

Other Information:
    ProcessCreationTime:        9570149208162972
    ClientProcessId:            6808
    ParentProcessId:            720
    FQDN:       0
    "
Does that help shed any light?


Thanks
Ian
Attachments
VBox_log2.zip
(35.53 KiB) Downloaded 12 times
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by scottgus1 »

Igfoo wrote:if I then start a large "git clone" command running in a shared folder
Is this command the 'git clone'?
Igfoo wrote:cd /c/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
The host is Linux, the VM is Windows. Sounds like the shared folder is shared from within the Windows OS over the VM network to the host OS.
Igfoo wrote:c:\ian, on the virtual disk ... s:\ian, on the shared drive
The info here is unusual, while possibly still OK. Please explain your arrangement. Also are you sharing the root of the C drive in the VM OS? And how does the S drive relate? Is it a separate drive in the VM or is it a shared folder from another OS?
Igfoo
Posts: 4
Joined: 16. Mar 2021, 14:44

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by Igfoo »

scottgus1 wrote:
Igfoo wrote:if I then start a large "git clone" command running in a shared folder
Is this command the 'git clone'?
Igfoo wrote:cd /c/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
When I sent the original message, the command I was running was "git clone <something>", but that's a complex command, and uses network, disk, etc. The above is a simpler command which also triggers the problem, but using "cp", so it seems unlikely that the network is relevant. Also, as it happens when I do it on the shared folder but not the virtual drive, I think it is likely to be a bug in shared folders.
scottgus1 wrote: The host is Linux, the VM is Windows. Sounds like the shared folder is shared from within the Windows OS over the VM network to the host OS.
Igfoo wrote:c:\ian, on the virtual disk ... s:\ian, on the shared drive
The info here is unusual, while possibly still OK. Please explain your arrangement. Also are you sharing the root of the C drive in the VM OS? And how does the S drive relate? Is it a separate drive in the VM or is it a shared folder from another OS?
The host is Linux, and the VM is Windows, correct.

The C drive is a normal virtual disk, created with "VBoxManage storageattach WindowsTest --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium /home/ian/vms/WindowsTest/disk.vdi".

The S drive is a shared folder, created with "VBoxManage sharedfolder add WindowsTest --name shared_wintest --hostpath=/home/ian/shared/wintest --automount --auto-mount-point=s:".

Apologies if my terminology is wrong.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by scottgus1 »

Igfoo wrote:The S drive is a shared folder, created with "VBoxManage sharedfolder
Thanks. This is a Virtualbox Shared Folder, which requires Guest Additions in the VM. This 'shared folder' is not a real shared folder, rather a Guest-Additions-established alternate channel that is technically only for manual mouse-driven drag-n-drop file/folder copy from the chosen host folder into the VM's OS and back. It isn't designed for anything else.

Further, this command:
Igfoo wrote:cd /s/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
Is referencing the shared folder inside the Windows VM, but with Linux commands running from the host. Did you also re-share the S drive in Windows so the Linux OS can see the contents of the S drive over a network?
Igfoo
Posts: 4
Joined: 16. Mar 2021, 14:44

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by Igfoo »

scottgus1 wrote:
Igfoo wrote:The S drive is a shared folder, created with "VBoxManage sharedfolder
Thanks. This is a Virtualbox Shared Folder, which requires Guest Additions in the VM. This 'shared folder' is not a real shared folder, rather a Guest-Additions-established alternate channel that is technically only for manual mouse-driven drag-n-drop file/folder copy from the chosen host folder into the VM's OS and back. It isn't designed for anything else.
Ah, I hadn't realised that. I assumed that this would be the most efficient way to do what I wanted. Is something else recommended for a directory that is shared, and used from both (Linux) host and (Windows) guest?
scottgus1 wrote: Further, this command:
Igfoo wrote:cd /s/ian
while :; do date; cp /c/Users/ialynagh/Downloads/*.exe .; rm *; done
Is referencing the shared folder inside the Windows VM, but with Linux commands running from the host. Did you also re-share the S drive in Windows so the Linux OS can see the contents of the S drive over a network?
I am running these command in an MSYS shell.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Win 10 guest on Ubuntu host stops working (black screen) after running a while

Post by scottgus1 »

Igfoo wrote:an MSYS shell.
Had to web-search this, and got to MSYS2, which apparently is some kind of run-Linux-commands-in-Windows a la Cygwin. That makes the setup more clear. Thought you'd somehow re-shared the Virtualbox Shared Folder back out over the network to the Linux host again.... :shock:

Anyhooo, If you're doing anything beyond moving a mouse to drag a file, use a real shared folder provided by the host or VM OS over a Virtualbox Bridged or Host-Only network. Since the commands appear to be running in the VM, web-search how to share a folder in Linux to a networked Windows PC.
Post Reply