Problem with sound and VB

[Ralf Mardorf]

On Mon, 23 Sep 2019 12:33:01 -0700, MR ZenWiz wrote:
>On Mon, Sep 23, 2019 at 11:29 AM Ralf Mardorf wrote:
>> Did you take a look at Logs/VBox.log*?
>>  
>The newest log has a last modified timestamp of 9/15/2018.  No
>indication of any crash.
>
>???

Maybe the location of the log files changed?

If you can't access a recent log file by command line, you also could
use the VirtualBox GUI.

https://support.oracle.com/knowledge/Sun%20Microsystems/1342727_1.html#aref_section22

Select a machine and push Ctrl+L.

Btw. "12.3.2. Windows Bluescreens After Changing VM Configuration

Changing certain virtual machine settings can cause Windows guests to
fail during start up with a bluescreen. This may happen if you change
VM settings after installing Windows, or if you copy a disk image with
an already installed Windows to a newly created VM which has settings
that differ from the original machine.

This applies in particular to the following settings:

    The ACPI and I/O APIC settings should never be changed after
    installing Windows. Depending on the presence of these hardware
    features, the Windows installation program chooses special kernel
    and device driver versions and will fail to startup should these
    hardware features be removed. Enabling them for a Windows VM which
    was installed without them does not cause any harm. However,
    Windows will not use these features in this case.

    Changing the storage controller hardware will cause bootup failures
    as well. This might also apply to you if you copy a disk image from
    an older version of Oracle VM VirtualBox to a virtual machine
    created with a newer Oracle VM VirtualBox version. The default
    subtype of IDE controller hardware was changed from PIIX3 to PIIX4
    with Oracle VM VirtualBox 2.2. Make sure these settings are
    identical." -
https://www.virtualbox.org/manual/ch12.html#ts_win-guest-bluescreen

I get recent log files:

$ head -2 /mnt/winos7/vmw7/Logs/VBox.log*; echo "##"; head -2
/mnt/winos10/winos10/Logs/VBox.log* ==> /mnt/winos7/vmw7/Logs/VBox.log
<== 00:00:00.681796 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3
2019 11:38:02) release log 00:00:00.681799 Log opened
2019-09-21T14:52:07.507174000Z

==> /mnt/winos7/vmw7/Logs/VBox.log.1 <==
00:00:00.644811 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.644814 Log opened
2019-09-20T13:34:58.078722000Z

==> /mnt/winos7/vmw7/Logs/VBox.log.2 <==
00:00:00.673470 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.673473 Log opened
2019-09-18T11:24:37.771700000Z

==> /mnt/winos7/vmw7/Logs/VBox.log.3 <==
00:00:00.612108 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.612110 Log opened
2019-09-16T22:02:17.550566000Z ##
==> /mnt/winos10/winos10/Logs/VBox.log <==
00:00:00.627082 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.627084 Log opened
2019-09-21T17:56:41.835158000Z

==> /mnt/winos10/winos10/Logs/VBox.log.1 <==
00:00:00.662773 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.662776 Log opened
2019-09-21T17:24:25.881412000Z

==> /mnt/winos10/winos10/Logs/VBox.log.2 <==
00:00:00.671723 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.671725 Log opened
2019-09-21T03:15:17.742808000Z

==> /mnt/winos10/winos10/Logs/VBox.log.3 <==
00:00:00.806573 VirtualBox VM 6.0.12 r133076 linux.amd64 (Sep  3 2019
11:38:02) release log 00:00:00.806575 Log opened
2019-09-20T18:04:14.888509000Z

-- 
“Awards are merely the badges of mediocrity.”

― Charles Ives