VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (361 - 363 of 16363)

Ticket Resolution Summary Owner Reporter
#20513 fixed Linux Mint "white screen of death" or initial black screen wellitisspeedy
Description

Runtime conditions:

  • Macbook Pro with Mojave latest updates as a host
  • Linux Mint latest as a guest
  • Graphics adapter chosen - default VMSVGA

Issue 1 - initial total black screen in X11 mode: Once the guest OS starts up in graphical environment with automatic login (I don't really need login screens for my VMs) and brings up Cinnamon, the whole desktop is black. Figured a workaround - switch between Full Screen mode and Windowed mode shows the desktop. Note: This used to happen in all 6.0 and 6.1 versions. https://altomaxtech.com/vboximages/TotalBlack.png

Issue 2 - "white screen of death": Once the workaround is applied, the desktop comes as completely white and the only visible area is the bottom panel. The while seems to be a top in the Z-order and all Windows are like under it. I can only stop the VM by issuing poweroff from CLI or with the graphical interface only by pressing Enter as per the default choice to power off. https://altomaxtech.com/vboximages/WhiteScreenOfDeath.png

Workaround for both is to select VBoxVGA or VBoxSVGA adapters, but then I get a warning about 3D acceleration not going to be working.

#20512 fixed Sporadic data corruption on a VHD virtual disk with ext4 => fixed in SVN/next maintenance Mikhail Kovalev
Description

We observed this problem on VirtualBox 6.1.18 - 6.1.26, Windows 10 host, Debian 9 or Debian 10 VM. We don't know if the other versions are affected or not. We could reproduce it with and without Hyper-V enabled. So far we only saw this problem on small VHDs (up to 10MB size) with the ext4 file system.

How to reproduce:

  1. Start the VM
  2. Attach a VHD (~10 MB size) to the (running) VM. We were creating a fresh VHD using the VirtualBox UI here.
  3. Format the disk from the VM. We used the following command:
    mkfs.ext4 -m 0 /dev/sdb
    
  4. Mount the disk inside the VM. We used the following mounting options:
    mount -t ext4 -o sync,nodelalloc /dev/sdb /test
    

Note: if we remove the "nodelalloc" setting, it's much harder to reproduce the data corruption (but we still could reproduce it a few times).

  1. Write some data to the disk. E.g.
    dd bs=1 count=60 if=/dev/random of=/test/test1
    
  2. Unmount the disk and mount it again:
    umount/mount
    mount -t ext4 -o sync,nodelalloc /dev/sdb /test
    
  3. The data on the disk might get corrupted now: the file content will be replaced with NULL bytes (either the whole file or starting from some offset). Screenshot attached. The corruption doesn't happen every time. But we can easily reproduce it in 2-3 tries at most.

I am also attaching VBox.log and the zipped corrupted .vhd.

#20511 invalid Nie Uruchamia Ani Jednej Maszyny Knopers2929
Description

Nie Uruchamia Ani Jednej Maszyny Mimo Że ISO Wgrane I Ustawienia Dobre

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy