﻿ticket,summary,version,created,modified,_changetime,_description,_reporter
17461,writethrough affected by snapshots,VirtualBox 5.2.4,2018-01-16T18:53:26Z,2019-01-26T03:29:12Z,2019-01-26T03:29:12Z,"I made this critical because not everyone will check for correct functionality. Restoring a snapshot will cause an unexpected data loss on a drive of type writethrough.

I've got a VM with a main drive and an attached writethrough drive. I see twice as many .vdi files than .sav files in the snapshot directory. And yes a restore changes the writethrough drive.


C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi[[BR]]
UUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx[[BR]]
Parent UUID: base [[BR]]
State: created [[BR]]
Type: writethrough [[BR]]
Location: E:\DataW10.vdi [[BR]]
Storage format: VDI Format [[BR]]
variant: fixed default [[BR]]
Capacity: 4096 MBytes [[BR]]
Size on disk: 4098 MBytes [[BR]]
Encryption: disabled [[BR]]
In use by VMs: Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)",Loafer
13718,Write same error when using SAS controller with Arch Linux guest,VirtualBox 4.3.20,2014-12-27T01:23:00Z,2014-12-27T01:23:00Z,2014-12-27T01:23:00Z,"I'm installing an Arch Linux guest using the 2014.12.01 ISO image. I've taken the defaults for VM provisioning except for changing the default storage controller to SAS. The ISO is able to boot and the /dev/sda disk is able to be successfully partitioned using cgdisk. Creating an ext4 file system is also successful. However, when the new sda1 is mounted, errors begin appearing on the console:
sda1: WRITE SAME failed. Manually zeroing.

I've changed the controller to SATA, and the problem is gone.

I'm not sure if this is a problem with the drivers in Arch, or with the SAS device in VirtualBox. I'm opening a bug with Arch as well, in case its not a vbox problem.",rj45
15590,"Windows guest hangs with AHCI port resets, cannot close VirtualBox instance",VirtualBox 5.0.20,2016-07-10T14:52:46Z,2016-07-10T14:52:46Z,2016-07-10T14:52:46Z,"Hello,

Recently I encountered a Windows guest that hung itself and would not allow me to stop it when right-clicking the VM->Close->Power off. I am running it in headless mode and I saw the vBoxHeadless.exe process on the host was reporting a constant CPU usage value but was not changing, indicating the process was hung.

There are 6 other guests running on this host, all of which did not hang and continued operating properly.

The guest had been booted at 6/30/16 01:31 and some logging software of mine stopped receiving a ping from the guest around 7/9/16 13:30 (232:57 in logfile). I did not attempt to intervene until 20 hours later (252:29 in logfile). It looks like when the guest host process hung the AHCI controller experienced an issue with port resets.

The host is running Windows Server 2008 R2, the guest is running the same.

The VBox.log file is attached.",lbgaus
16601,Windows 10 on Surface Book virtualbox install,VirtualBox 5.1.18,2017-03-24T01:13:41Z,2017-03-24T01:13:41Z,2017-03-24T01:13:41Z,"I have a brand new Microsoft surface pro book with windows 10.  I have the latest update.  I even uninstalled
the software, removed the files off the hard, removed from windows registery
then reinstalled virtualbox.  I downloaded the latest version of Kali Linux
and I get the same problem.  Windows crashes on me and restarts itself
saying it is writing the report.  I even reinstalled windows 10 and then
did a update, downloaded a fresh virtualbox, fresh kali Linux and the system
bombed out again.  Is there anyway we can fix this problem?",henrygh101
20202,"Win10 6.1.18 host hanging during guest startup / pausing / shutdown, excessive disk read seen",VirtualBox 6.1.18,2021-02-18T13:56:03Z,2022-06-16T01:16:21Z,2022-06-16T01:16:21Z,"When I upgrade from 6.1.16 on win10 to 6.1.18, 6.1.19-142777, or 6.1.97-142300 then my Linux and Win10 guests stop responding for a while during startup, shutdown and every time the VM is Paused.

During the entirity of the time the VM is not responding, Task Manager on the host shows Disk reads for the VirtualBox process jump to 600MBytes/sec. Writes stay at close to zero.   The duration of the non-responsiveness when Pausing both tested VMs corresponds with the size of the VM.  

IE every time I Pause the Ubuntu Linux guest, it take 15 seconds of reading @ 600MB/sec to Puase, while the VM size is ~=9GB.   Likewise it takes ~50 seconds to Pause my ~30GB Win10 VM.

From observing the Disk status on Task Manager, whatever triggers the hang/reads seems to happen 2-3 times during VM start up and 1-2 times during shutdown.

vbox.log on 6.1.18 (see attached) shows entries like:

- AsyncCompletion: Task 0x0000000762df00 completed after 16 seconds

- VD#0: Aborted read (0 bytes left) returned rc=VERR_PDM_MEDIAEX_IOREQ_CANCELED

However, during pausing of the VM no errors are seen in the log file - just that PDMR3Suspend took 15 seconds instead of 50 milliseconds.

The Ubuntu guest sometimes has a console message about disk that I couldn't capture.  One boot it came up with / readonly due to needing fs check.

I don't see the same issue occur using 6.1.18 on Win8.1.  It pauses (in well under 1 second), boots and shuts down swiftly as expected with minimum disk reads.
",Grrrrrrr
17685,Weird acting of vboxmanage.exe's --compact flag,VirtualBox 5.2.8,2018-04-14T17:29:01Z,2018-04-18T15:01:10Z,2018-04-18T15:01:10Z,"When using the 
{{{
vboxmanage modifymedium <virtual VDI disk> --compact
}}}
command on a dynamic type VDI disk (previously nulled the free spaces, with [https://technet.microsoft.com/en-us/library/2009.08.utilityspotlight.aspx Sdelete] on Windows), it seems to be successful, though, the resulted image's content cannot be viewed with [https://www.7-zip.org/ 7zip] anymore, even though, VDI is a supported format of it and before running the command, it was working too. At this point, the image is mountable and the system on it is bootable, like it should.
But, after all of these, when i try to clone the image with
{{{
vboxmanage clonemedium <input file> <output file>
}}}
even though, the operation is finishes, without any problems, the system on the cloned disk, isn't bootable anymore, because the whole VM crashes, right in the middle of the boot process. Suprisingly, it can be opened with 7zip again. Cloning again and again doesn't change anything, while ''chkdsk'' cannot find any problems.
Additionally, this isn't the first case, when i have to face with this issue, so i guess, i can label it, as reproducible.",T800
8760,VMDK: VERR_SHARING_VIOLATION,VirtualBox 4.0.6,2011-04-21T21:06:37Z,2019-03-03T04:57:10Z,2019-03-03T04:57:10Z,"When running in an administrator command line and attempting to create virtual drives from raw disks under a windows 7 host, vboxmanage fails with this error message.  I was previously able to use these commands to mount my ubuntu partition under virtualbox on a windows XP host.  

Regards,
Alaric

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands listpartition
s -rawdisk \.\PhysicalDrive0
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
5       0x83  0   /2  /1   29  /254/63           235          126
6       0x82  30  /1  /1   333 /254/63          2384       482013
7       0x83  334 /1  /1   1023/254/63         18119      5365773
8       0x83  1023/254/63  1023/254/63         17406     42475520
2       0x07  1023/254/63  1023/254/63        114470     78124095

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe internalcommands createrawvmdk
 -filename ""c:\Users\alaric\mydrive.vmdk"" -rawdisk \.\PhysicalDrive0 -partition
s 5,6,7,8
VBoxManage.exe: error: VMDK: could not open raw partition file '\.\PhysicalDriv
e0'
VBoxManage.exe: error: Error code VERR_SHARING_VIOLATION at D:\tinderbox\win-4.0
\src\VBox\Storage\VMDK.cpp(3762) in function vmdkCreateRawImage
VBoxManage.exe: error: Cannot create the raw disk VMDK: VERR_SHARING_VIOLATION
VBoxManage.exe: error: The raw disk vmdk file was not created
",Alaric
19197,vmdk not visible after shutdown,VirtualBox 5.2.34,2020-01-04T10:15:11Z,2020-01-04T14:29:46Z,2020-01-04T14:29:46Z,"Hi,

I have come acros a problem.
I downloaded mininet-vm from [1].
I opened virtualbox
I selected file
I selected import appliance
The vm booted
I shut down the vm
I closed virtualbox
I opened virtualbox again
I clicked on the ""Mininet-VM"" virtual machine
the prompt with initramfs appeared.
I closed the virtual machine by pressing x from the window
I right clicked the virtual machine
I selected properties
I went to storage
I reselected the vmdk for the VM which came with the mininet-vm from mininet download folder
it worked.

Thanks",cric
17081,VM virtual hard disk deleted,VirtualBox 5.1.26,2017-09-14T23:26:57Z,2017-09-15T08:19:06Z,2017-09-15T08:19:06Z,"Hi,

I installed the latest Windows update (Windows 7 is my guest OS) and an update of the VirtualBox expansion pack this morning. After restart, the majority of my VMs were shown as inaccessible. When I checked, the hard disk files were not present. I looked at the VirtualBox logs and I can see VirtualBox doing the deletion in the logs. I never requested this deletion. Fortunately I have backups. Log files will be attached.
Thanks!
Jean",Zed
16450,VM locks up when setting --discard and --nonrotational and using fstrim,VirtualBox 5.1.14,2017-02-04T02:32:50Z,2020-03-21T16:49:41Z,2020-03-21T16:49:41Z,"I changed the settings of my Xubuntu VM to emulate an SSD:

{{{
VBoxManage storageattach Xubuntu --storagectl SATA --port 0 --discard on --nonrotational on
}}}

After that started the VM. Everything runs fine until running fstrim in the VM. First the VDI file is shrinked a bit, then VirtualBox starts continuously reading from host filesystem (I guess from the VDI file). After some time the VM guest OS reports storage problems (timeouts) in dmesg output. No access to emulated storage is possible after that, but VM continues to run (e.g. scrolling in windows, moving mouse, ...). See attached VM screenshots and VBox.log for details.

I already observed the same behavior with a Windows 10 VM which locked up in the same way, but then I did not record any logs or error information.

Problem seems to be similar to ticket #15509.

Host info: Kubuntu 16.10 64 Bit, VirtualBox 5.1.6 (installed from Kubuntu repository)

Guest info: Xubuntu 16.10 64 Bit, 1 SATA controller, 1 VDA file with dynamic size

Please tell if any more information is needed.",Motlib
17604,"VM becomes ""inaccessible"" on re-launching GUI, Sharable VDI removed from media registry",VirtualBox 5.2.8,2018-03-07T16:51:29Z,2021-02-03T13:47:07Z,2021-02-03T13:47:07Z,"Hello all,

Running into a ''very'' annoying problem, where my shareable vdi disk gets removed from the the VM (.vbox) xml on shutting down the VirtualBox Manager GUI -- resulting in my guest becoming ""inaccessible"" -- this has been happening for the past few versions (at least as far back as 5.2.6).
I can make the VM ""accessible"" again by manually specifying the shared disk in the .vbox file (or temporarily attaching the shared disk to another guest, to have it show up in the media registry).
As soon as I close/re-open the VirtualBox Manager GUI, my VM becomes ""inaccessible"" again.

Anyhow, here is the message I get:

{{{
A differencing image of snapshot {5912e4a6-b6c8-4ba7-ae4c-51b15512b9f5} could not be found. Could not find an open hard disk with UUID {662e4d2d-9085-4ecb-819e-f1f9875367e2}.
Result Code: 
E_FAIL (0x80004005)
Component: 
SnapshotMachine
Interface: 
IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
}}}

When manually editing the .vbox file, this is what I have been adding... but it get's overwritten when cycling the VirtualBox Manager GUI:

{{{
<VirtualBox ...>
  <Machine ...>
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{662e4d2d-9085-4ecb-819e-f1f9875367e2}"" location=""C:\Users\{me}\VirtualBox VMs\Shared\ActivationsDisk.vdi"" format=""VDI"" type=""Shareable""/>
      </HardDisks>
      <.../>
    </MediaRegistry>
    <.../>
  </Machine>
</VirtualBox>
}}}

Any help/fixes would be greatly appreciated.

Thanks!
",pbouill
1461,Virtualizing physical partition with createrawvmdk fails on Mac OS X Leopard,VirtualBox 3.0.4,2008-05-03T20:22:21Z,2014-01-15T14:58:50Z,2014-01-15T14:58:50Z,"On Mac OS X 10.5.2 (Intel iMac Core Duo) with VirtualBox 1.6.0, trying to create a VMDK for disk0s3, running the command

{{{sudo VBoxManage internalcommands createrawvmdk -filename test.vmdk -rawdisk /dev/disk0 -partitions 3 -register}}}

returns:

{{{Error while creating the raw disk VMDK: VERR_INVALID_PARAMETER}}}",jtbandes
8435,VirtualBox only works with floppy disk images which have a certain filename extension,VirtualBox 4.0.4,2011-02-25T15:38:34Z,2016-10-10T15:42:12Z,2016-10-10T15:42:12Z,"VirtualBox 4.0.4 seems to refuse to work with floppy disk images unless the image filename has a certain extension. For example, on selecting ""myfloppy.bin"" in the GUI, VirtualBox says:
  Failed to open the floppy image /home/user/myfloppy.bin.
  Could not get the storage format of the medium '/home/user/myfloppy.bin' (VERR_NOT_SUPPORTED).

  Result Code: 
  VBOX_E_IPRT_ERROR (0x80BB0005)
  Component: 
  Medium
  Interface: 
  IMedium {9edda847-1279-4b0a-9af7-9d66251ccc18}
  Callee: 
  IVirtualBox {d2de270c-1d4b-4c9e-843f-bbb9b47269ff}

However, if I rename the file to myfloppy.dsk, there is no problem. I suggest that the filename limitation be removed. (If the selected file is exactly 1474560 bytes long, it will be a raw floppy disk image.)

",Donuts
20478,Virtualbox locks up badly with fstrim on CentOS 8,VirtualBox 6.1.24,2021-07-28T16:57:33Z,2021-07-28T16:57:33Z,2021-07-28T16:57:33Z,"I tried using fstrim, with a VM presenting a virtio-scsi ""disk"", and it worked for a while (defined as ""the VDI file backing the FS shrinking on disk""), then eventually most IO hung indefinitely.

Most excitingly, SysRq-B resulted in the VM being stuck with its ""display"" showing a mix of black and occasional green boxes and not rebooting, then if I attempted to do anything to the VM (e.g. ""Reset"", ""Poweroff""), the window became unresponsive, and I had to force-close it, and VB reported ""Aborted"" for the VM status.

When I tried reproducing it just now for this ticket, it instead just blocked indefinitely in the OS - no errors reported, but fstrim wouldn't respond to ^C or kill -9, and trying to close the VM window hung and then reported Aborted.",rincebrain
15547,Virtualbox destroy encrypted discs when delete online snapshots,VirtualBox 5.0.22,2016-06-26T15:20:55Z,2016-07-14T17:25:07Z,2016-07-14T17:25:07Z,"I tested this on several servers, and the results are 100% reproducible.

I found 3 ways to destroy the encrypted discs:

First:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Remove the snapshot with VM turned on.
 4. Restart the VM
=> The discs are destroyed and the S.O can't start.

Second:
 1. Encrypt the discs of an VM 
 2. Take a offline snapshot
 3. Start the VM
 4. Remove the snapshot with VM turned on.
 5. Restart the VM
=> The discs are destroyed and the S.O can't start.

Third:
 1. Encrypt the discs of an VM and start the S.O 
 2. Take a online snapshot
 3. Pause the VM
 4. Remove the snapshot with VM paused.
 5. Resume the VM
 6. Restart VM
=> The discs are destroyed and the S.O can't start.

I was tried to find a way to make a automatic backup of an encrypted VM, without need the save the key on the backup script to start vm again, and hard crash the discs off the VM.

The log of the VM on the first case as attached, and a screenshot of it after the restart.

It was tested with the last 5.0.22 VirtualBox Release and I dont found other tickts about this defect.

Thanks for you guys that develop this great program.  ",Law
20306,VirtualBox crashes on IO in FreeBSD 13,VirtualBox 6.1.18,2021-04-20T09:42:24Z,2021-04-20T10:01:34Z,2021-04-20T10:01:34Z,"I started up a FreeBSD 13 VM that I've had for a little bit on VB 6.1.16, started installing some packages, and suddenly the VM crashed and displayed ""Aborted"" on the management interface.

I upgraded VB to 6.1.18, booted the VM, started installing the same packages again, and lo and behold, it died again.

I've attached the log from the VM dying on 6.1.18.",rincebrain
6102,VirtualBox cannot load split VHD files.,VirtualBox 3.1.2,2010-01-31T18:46:03Z,2013-05-20T09:34:35Z,2013-05-20T09:34:35Z,"When I try to open a split VHD file in the VirtualBox Media Manager, I get the following error:
{{{
Failed to open the hard disk D:\Fedora 7 Hard Disk.vhd.
Could not get the storage format of the medium 'D:\Fedora 7 Hard Disk.vhd' (VERR_NOT_SUPPORTED).
}}}
The VHD file is split because Microsoft Virtual PC automatically splits VHD files on disks that have the FAT32 filesystem.
",theflash
19748,VirtualBox 6.1.12 allows to create a fixed disk bigger than free space,,2020-07-22T12:35:44Z,2020-07-22T12:35:44Z,2020-07-22T12:35:44Z,"Good afternoon,

Creating a virtual machine allows you to also add a new disk. In my opinion, if you choose fixed size, the program shouldn't allow to create disks bigger than the free space.

You can see it in [https://streamable.com/fr8dyj this video].

Regards.",Antonio López Fernández
14165,Virtual machine loses hard drive when settings are changed.,VirtualBox 4.3.28,2015-06-02T14:21:26Z,2015-06-02T15:35:30Z,2015-06-02T15:35:30Z,"This problem is described at length in the forum at this link:
http://forums.virtualbox.org/viewtopic.php?f=6&t=68147&p=323314&e=323314

After shutting down the guest OS and changing its settings using VirtualBox Manager the virtual machine loses its DVD and/or HDD configuration.
The message: FATAL: Could not read from the boot medium! System halted.

is displayed and it not possible to recover the disk. (Things tried restoring the original .vbox and .vbox-prev files, running VBoxManage internalcommands sethduuid etc. )

This problem is not present in VirtualBox 4.3.20.",eqh
17731,virtual drive,VirtualBox 5.2.10,2018-05-04T13:24:06Z,2018-05-04T14:30:07Z,2018-05-04T14:30:07Z,"the problem enhances, wen I am testing a new OS X86 / internet data mikeOS
the drive get un link’t , after 1 after a month of use


",NadirVT
20294,Virtual disk automatic resize/growth failing.,VirtualBox 6.1.18,2021-04-08T18:40:30Z,2021-05-19T16:55:55Z,2021-05-19T16:55:55Z,"Hi,

When the vitual hdd is defined during VM creation, I selected a dynamically allocated VDI. As far as I can tell, the size selected will be the maximum size of the hdd on the host and that less space will be allocated initially and extended as needed during guest operation. Correct?

My situation is a VM with a dynamically allocated hdd of 384GB. Right now it's at 45GB or so but is trying to extend the size. The guest is reporting disk problems and out of space problems and has now changed one partition to read only. What I think is happening is that the guest has a code path which Virtual Box intercepts, does some magic to add space, restart the operation. This is apparently NOT happening. The path through Virtual Box may or may not be trying to handle this situation but then appears to let the error(s) continue through the guest OS (5.12.0-0.rc5.180.fc35.x86_64).

Here's what the host thinks of the partition where the VDI is located:

{{{
Filesystem                         1K-blocks        Used   Available  Really_Available Use% Mount_Point
/dev/sda8                         1735405656   485065980  1250569508        1250339676  28% /export/home
}}}

The guest thinks it's VDI is:

{{{
Filesystem     1K-blocks     Used Available Use% Mounted on
/dev/sda2        1992552   164592   1706720   9% /
/dev/sda7       65478188 14001584  48104780  23% /usr
/dev/sda1        1992552   149816   1721496   9% /boot
/dev/sda8      184666464 19495796 155717356  12% /export/home
/dev/sda5       65478188   751092  61355272   2% /var
/dev/sda6       65478188   936844  61169520   2% /opt
}}}

Which is considerably less than 384GB.

Additionally, the guest is throwing numerous messages like these:

{{{
[   23.180382] 06:32:17.603879 main     VBoxService 6.1.18_Fedora r142142 (verbosity: 0) linux.amd64 (Mar  2 2021 00:00:00
) release log
               06:32:
[   23.184678] 06:32:17.610514 main     OS Product: Linux
[   23.189518] 06:32:17.614980 main     OS Release: 5.12.0-0.rc5.180.fc35.x86_64
[   23.192546] 06:32:17.617869 main     OS Version: #1 SMP Mon Mar 29 15:30:36 UTC 2021
[   23.197236] 06:32:17.620938 main     Executable: /usr/sbin/VBoxService
               06:32:17.620942 main     Process ID: 591
               06:32:17.620944 main     Pa
[   23.202542] 06:32:17.628117 main     6.1.18_Fedora r142142 started. Verbose level = 0
[   23.208141] 06:32:17.633605 main     vbglR3GuestCtrlDetectPeekGetCancelSupport: Supported (#1)
[   40.487920] e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   40.488885] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
[ 7841.824091] systemd[1]: systemd v248-1.fc35 running in system mode. (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOM
P +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQU
ALITY +P11KIT +QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 7841.825374] systemd[1]: Detected virtualization oracle.
[ 7841.825631] systemd[1]: Detected architecture x86-64.
[ 7872.660143] ata1.00: exception Emask 0x0 SAct 0x1ffff800 SErr 0x0 action 0x6 frozen
[ 7872.661528] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.662445] ata1.00: cmd 61/00:58:c8:89:2b/0a:00:12:00:00/40 tag 11 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.664910] ata1.00: status: { DRDY }
[ 7872.665671] ata1.00: failed command: WRITE FPDMA QUEUED
[ 7872.666963] ata1.00: cmd 61/00:60:c8:93:2b/0a:00:12:00:00/40 tag 12 ncq dma 1310720 ou
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}


and:

{{{
[ 7872.721207] ata1.00: status: { DRDY }
[ 7872.721577] ata1.00: failed command: READ FPDMA QUEUED
[ 7872.722023] ata1.00: cmd 60/08:e0:10:7a:0d/00:00:17:00:00/40 tag 28 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 7872.723230] ata1.00: status: { DRDY }
[ 7872.723607] ata1: hard resetting link
[ 7873.036871] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7873.038028] ata1.00: configured for UDMA/133
[ 7873.038418] ata1.00: device reported invalid CHS sector 0
[ 7873.038850] ata1.00: device reported invalid CHS sector 0
[ 7873.039295] ata1.00: device reported invalid CHS sector 0
[ 7873.039725] ata1.00: device reported invalid CHS sector 0
[ 7873.040250] ata1.00: device reported invalid CHS sector 0
[ 7873.040691] ata1.00: device reported invalid CHS sector 0
[ 7873.041133] ata1.00: device reported invalid CHS sector 0
[ 7873.041646] ata1.00: device reported invalid CHS sector 0
}}}


and:

{{{
[49175.522760] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621957, error -30)
[49175.526567] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621958, error -30)
[49175.530010] EXT4-fs (sda8): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2621961, error -30)
}}}

Of course there are more of all of these messages available in a file. I'm not sure how I would attach a file to this mailing list though.

Can someone take a look at all this and render some assistance please?

Best regards,

George...



VirtualBox Graphical User Interface

Version 6.1.19 r143581 (Qt5.6.1)",George R. Goffe
18060,virtual computer disk removes,VirtualBox 5.2.20,2018-10-18T11:47:33Z,2018-10-18T11:52:52Z,2018-10-18T11:52:52Z,"after a wile de virtual computer disk removes it self from the settings.
And need to reinitialize from the disk section menu. 
Like the data setting are removed.
",Nadvt
17024,"VHD Disks created on Disk Manager cannot be moved tho another folder after attaching and desattaching on VM, fail on reattaching without registration deletion",VirtualBox 5.1.26,2017-08-20T00:45:09Z,2018-03-14T17:19:07Z,2018-03-14T17:19:07Z,"Recipe to bug/enhacement : 

 1. Create a .VHD (not VHDx not tested) disk on Windows Disk Manager with dinamic size.
 2. Desattach disk from system using the same Disk manager
 3. Create a Virtual Machine and choose the Existing Disk created
 4. Run the virtual machine, after error boot, stop.
 5. Remove the VHD hardDisk from VM using the Virtual Disk configuration UI
 6. On windows explorer, MOVE the created VHD Disk to another folder
 7. Try to attach the disk ON VM ou other VM using Virtual Box UI

you got the error/failure.
{{{
Cannot register the hard disk 'C:\Users\username\Desktop\FolderToMove\VirtualDisk1.vhd' {fa3d7a1c-xxxx-49ae-xxxx-63a83b45916e} because a hard disk 'C:\Users\username\Desktop\VirtualDisk1.vhd' with UUID {fa3d7a1c-xxxx-49ae-xxxx-63a83b45916e} already exists.


Código de Resultado: 
E_INVALIDARG (0x80070057)
Componente: 
VirtualBoxWrap
Interface: 
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
RC do Chamador: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}
Ok, on Virtual Box UI, you have to click on File - Virtual Media manager and remove the registred VHD disk from the list. but enhancing Virtual Box can be check the old file location not exist anymore and update to the new file location on disk without error, or ask to the user if he want to update.
",Armored
6023,VHD Delete Snapshot results in corrupt virtual hard disk or double snapshot revert,VirtualBox 3.1.2,2010-01-19T02:50:05Z,2018-01-25T20:38:49Z,2018-01-25T20:38:49Z,"1) VHD double snapshot - Restore:

Restore Snapshot (snap2) immediately followed by Delete Snapshot (snap2) has the same effect as Delete Snapshot (snap2) followed by Restore Snapshot to the parent Snapshot (snap1).  Any changes made between snap1 and snap2 are lost.

Repro steps:
 * Start with a VM having a VHD file attached that has no snapshots. (I used the Windows XP Mode VHD extracted from the 32-bit Windows XP Mode download: MD5sum= 5189623a8e5c6ff518cdd4759037f109, newly attached to a new VM and not yet booted.)
 * Take a snapshot 'Snapshot 1'
 * Boot the VM and make a change (perhaps create a file).
 * Shutdown VM
 * Take a snapshot 'Snapshot 2'
 * Select 'Snapshot 2' and 'Restore Snapshot' immediately followed by 'Delete Snapshot'
 * Boot VM and note that your change has gone: The VM has been restored back to 'Snapshot 1'

2) Virtual hard disk corruption causes BSOD and/or registry repair messages at boot.

Repro steps:
 * Start with a VM having a VHD file attached that has no snapshots. (I used the Windows XP Mode VHD extracted from the 32-bit Windows XP Mode download: MD5sum= 5189623a8e5c6ff518cdd4759037f109, newly attached to a new VM and not yet booted.)
 * Take a snapshot 'Snapshot 1'
 * Boot the VM and make a change (perhaps create a file).
 * Shutdown VM
 * Take a snapshot 'Snapshot 2'
 * Boot the VM then shutdown.
 * Select 'Snapshot 2' and 'Delete Snapshot'
 * Boot VM and note that it BSOD's or has other corruption problems.",Mark Cranness
18219,VERR_NOT_SUPPORTED for a valid ISO image,VirtualBox 6.0.0,2018-12-21T15:17:07Z,2022-10-21T12:47:37Z,2022-10-21T12:47:37Z,"Both VirtualBox 6.0 and 5.2.22 don't accept this ISO image:

http://mirror.ppa.trinitydesktop.org/trinity/cdimages/ubuntu/tde-ubuntu-14.04-desktop-latest-amd64.iso

The error is:

Failed to open the disk image file /tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso.

Could not get the storage format of the medium '/tmp/tde-ubuntu-14.04-desktop-latest-amd64.iso' (VERR_NOT_SUPPORTED).


{{{
Result Code: VBOX_E_IPRT_ERROR (0x80BB0005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}


",Artem S. Tashkinov
16454,VERR_ACCESS_DENIED when using raw disk on Windows 10 host,VirtualBox 5.1.14,2017-02-04T18:51:58Z,2018-06-19T09:32:03Z,2018-06-19T09:32:03Z,"I created an Ubuntu 16.10 x86_64 VM and attach added raw disk to it which is an internal SATA hard drive (not the system one). I followed the procedure described in the manual for Windows hosts and successfully created a raw disk with VBoxManage.

However, during installation of the gust Ubuntu system as soon as it attempted to modify the disk the VM was paused with the following error:

The I/O cache encountered an error while updating data in medium ""ahci-0-0"" (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.


Error ID: 
BLKCACHE_IOERR
Severity: 
Non-Fatal Error

despite that I was running VirtualBox as admin.
",szx
19242,vdi file destroyed,VirtualBox 6.0.14,2020-01-19T09:55:22Z,2020-01-20T15:47:06Z,2020-01-20T15:47:06Z,"
So my .vdi has become empty - 0B size, checked with hex viewer. There is E_ACCESSDENIED entry at the very end of log from last proper run of my machine (previous log does not have this). Also modification date on the vdi file matches that of said log.

I understand that this error may be not reproducible but seems to me like a possible very major flaw. I have never tampered with disk file in any way and didn't notice any similar incidents on my hardware. 

I'm on windows 8.1, client was Linux Manjaro.

Thank you
",pk6610
18721,vdi disk got filled up and now VirtualBox refuses to revert to an earlier snapshot,VirtualBox 5.2.18,2019-06-22T14:31:49Z,2019-06-22T21:39:05Z,2019-06-22T21:39:05Z,"Hello,

I am running VritualBox 5.2.18, host OS being Ubuntu 18.04 and guest being Mint 19. 

In Mint I have a riscv/rocket-chip environment setup in order to simulate behavior of a processor and observe its output waveforms, given the input in the form of c/assembly programs. Once I had installed the Mint OS I created a snapshot, and then again, once I had setup the environment, I created another snapshot and only then moved on to run different simulations.

The output waveform files do tend to get big, so my VDI is 110 GB fixed-size. Nevertheless, yesterday the simulation went on and on, and the output waveform file simply filled the whole VDI, completely. 

That I conclude from this is the message I get when I try turning the VM in its current state:


{{{
An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_DISK_FULL). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}


So, ok - it makes sense: the file got to big, filled up the disk, the VM can't boot. Ok, no problem there. However, once I tried bringing back the snapshot (either one of them), I get:


{{{
Failed to restore the snapshot intenuser of the virtual machine rockettest.

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
}}}


And this, definitely, is not ok - it brings me into a terrible position, as it completely destroys the work on setting up everything.

I tried increasing size of the VDI, but for some reason - I am not allowed to type in the new size (image attached - 1).

VirtualBox does allow me to enter the new size for a snapshot (image attached - 2), but once I click Apply, that leads to a new error:


{{{
Failed to resize the storage unit of the hard disk /media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi from 100.00 GB to 120.00 GB.

Could not resize medium '/media/aleksandar/Elements/VirtualMachines/rockettest/Snapshots/{814f10d6-c461-4860-be1c-4da0540701b3}.vdi' (VERR_DISK_FULL).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}


Please help.",dndrdm
18741,VBoxManage see fixed size disk as dynamic,VirtualBox 6.0.4,2019-07-03T05:27:11Z,2019-07-03T05:48:08Z,2019-07-03T05:48:08Z,"I have faced with the following problem during the attaching vdi disk to the virtual machine. 
The disk is fixed size:
{{{
VBoxManage showmediuminfo /opt/asm1.vdi
UUID:           8f62813f-0329-426a-8c65-def93934337a
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /opt/asm1.vdi
Storage format: VDI
Format variant: fixed default
Capacity:       20480 MBytes
Size on disk:   20482 MBytes
Encryption:     disabled
}}}
but when I try to attach it:

{{{
VBoxManage storageattach node1_rac --storagectl ""SATA"" --port 1 --device 0 --type hdd --medium asm1.vdi --mtype=shareable
VBoxManage: error: Cannot change type for medium '/opt/asm1.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 708 of file VBoxManageStorageController.cpp
VBoxManage: error: Failed to set the medium type

}}}

Could you explain the reason?


",SAlex
17637,VBoxManage encryptmedium - cipher validation and documentation,VirtualBox 5.2.6,2018-03-25T11:48:45Z,2018-03-25T11:48:45Z,2018-03-25T11:48:45Z,"Hi, 
As reported in https://forums.virtualbox.org/viewtopic.php?f=6&t=87254, i had some issues encrypting a disk.

Long story short, the encryptmedium command '''requires''' a cipher parameter, but a) does not validate it is present and b) does not present clear usage instructions (in my humble opinion).

Can I suggest that a check is done in handleEncryptMedium (VBoxManageDisk.cpp, line 1756) that if a user has provided a new password and password id, but no old password, that either the method picks a cipher by default if none is provided or reports the issue to the user. At the moment the error reported is pretty misleading.

For example:


{{{
VBoxManage encryptmedium 2f6ab46f-8db4-44d9-af1e-152c35178724 --newpasswordid test --newpassword -
Enter new password:
0%...
Progress state: VBOX_E_INVALID_OBJECT_STATE
VBoxManage.exe: error: Failed to encrypt hard disk
VBoxManage.exe: error: The password and password identifier must be empty if the output should be unencrypted
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleEncryptMedium(struct HandlerArg *)"" at line 1890 of file VBoxManageDisk.cpp

}}}


Supplying the cipher:


{{{
VBoxManage encryptmedium 2f6ab46f-8db4-44d9-af1e-152c35178724 --newpasswordid test --newpassword - --cipher AES-XTS128-PLAIN64
Enter new password:
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%


}}}
",andy-g
12866,VBoxManage clonehd should fail early if not enough disk space,VirtualBox 4.3.8,2014-03-25T14:37:38Z,2014-03-26T15:00:03Z,2014-03-26T15:00:03Z,"Given a 40GB .vmdk file, trying to clone the disk

  VBoxManage clonehd in.vmdk out.vdi --format vdi

will churn happily until it runs out of disk space many minutes later.

The command should first verify that there is sufficient space
for the output file (which will be roughly the same size),
and fail early if there is insufficient space. 

Care should be be taken for the case that the output file
is in a symlinked diretory; you need to check the canonical
location.

A --force option could bypass that check (for example, if there is
some other job running concurrently that will free up space
for the new file).

Same should be true for modifyhd or other operations that create virtual disk or other large files.",David Biesack
11358,VBoxManage cannot resize fixed size disks,VirtualBox 4.2.6,2013-01-04T02:42:52Z,2013-01-04T03:40:15Z,2013-01-04T03:40:15Z,"It shows an error instead:

VBoxManage.exe: error: Resize hard disk operation for this format is not implemented yet!

Another (easier and safer) solution would be to add a --resize option to the clonehd command of VBoxManage",Csq
20097,VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) error,VirtualBox 6.1.16,2020-12-19T05:39:16Z,2020-12-19T06:18:13Z,2020-12-19T06:18:13Z,"The VM-B works properly in Windows 10,
The VM-B is a link-clone VM of another VM-A.
I moved my working space '''from Windows to Linux''' in recently.
[[Image(https://i.loli.net/2020/12/19/UrqvuKlEnOZQbRT.png)]]

I installed newest VirtualBox on my Linux Desktop.
And the '''VM-A is working properly,''' (import from *.vbox file)
But the VM-B give an error message VBOX_E_OBJECT_NOT_FOUND.
[[Image(https://i.loli.net/2020/12/19/vIt5o8ZPUHVFubW.png)]]

And I tried register the seprated disk image for VM-B,
then VM-B works fine!
But the error VBOX_E_OBJECT_NOT_FOUND showns again when I restart VirtualBox.
I need register the seprated disk again to let it works.
[[Image(https://i.loli.net/2020/12/19/ijwGykchT7L4npN.png)]]


Linux OS: UOS V20 [Deepin V20 Commerical Version]
VirtalBox: 6.1.16 r140961 (Qt5.11.3)


i tried:
* remove old vbox file for VM-B and recreate it.
* import vbox file for VM-B again.
but no use.

Regards,
Pekaikon Norckon",dfc643
20553,VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension,VirtualBox 6.1.26,2021-09-17T01:25:08Z,2021-09-22T04:23:30Z,2021-09-22T04:23:30Z,"hi Team,

While importing the OVA file into Virtual box, an error in being popped up with ""VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension""
I already verified, of having the disk with its proper extensions in .ovf file.
But still having the issues whereas when I import the same ova file in VMware, it did worked at its pace and can start the VM.
Please help on this asap ?",Sanchit Gupta
20233,Unwanted conversion dynamic to fixed disk,VirtualBox 6.1.18,2021-03-04T10:07:46Z,2021-03-08T12:40:05Z,2021-03-08T12:40:05Z,"Hello!

I'm unsure about this is a bug or a feature, but I'm very confused about it:

I have a VM with a fixed VDI. This is explicitly what I want to have for some performance issues on Linux host. When I clone this VM via Ctrl-O, I wondering that the clone has an dynamic VDI, I didnt like that behavior. 

But really really bad is: The source VM is also converted to a dynamic VDI. Therefore I must go to the vboxmanage modifyvm twice (for source and target VM) and convert it back to fixed. These steps consumes unneccessarily space on my SSD.

Please make an selection in the GUI which target disk type is wanted. And much more important: Please leave the source VM unchanged!

Thanks and Greets!",Codehunter
8929,undoc'd Windows XP  trick does not work in virtualbox (active partitons),VirtualBox 3.1.2,2011-05-20T03:58:43Z,2011-05-21T02:43:10Z,2011-05-21T02:43:10Z,"do this on a real computer:
run UBCD and mark the sole partition of your computer active using MMC. reboot without disk, and you should receive error: NTLDR missing. Press Ctrl+Alt+Del to reboot.

then i copy contents of windows drive to the disk and it runs because NTLDR is copied.


do the same in virtualbox and i get FATAL: No bootable medium found! system halted.
obviously a virtualbox error, not seeing the active partition on the virtual drive.

This virtual drive was created using version 1.62 as i was using a win2k host at the time, but the copying was done using the 3.1.2 (and failed to boot), and tried running it on 4.0.8 and not going.

UBCD mmc still reports there is a single partition on the drive, and is active. 160GB drive, 48GB partition.

currently vista host 4.0.8
and not yet a XP sp1 guest.

cb.",Charlie
15213,Unable to remove device with attached diff images,VirtualBox 5.0.16,2016-03-07T15:12:29Z,2016-11-16T13:00:51Z,2016-11-16T13:00:51Z,"Receive message box - one or more disk image files are not currently accessible......

Select ""check""

VDI device is not attached to any machine.  Also, rechecked all machines and non are using this vdi in this location.  Attempt to remove it but it says it has 1 child media and object in use.

a) cryptic message as it should really say in plain english what object name its associated with.

b) there are no machines that I currently have using this particular vdi.

c) have similar named vdi located in another directory but not attached to this one here.  Nothing is attached to it.
",ArtZ
16534,Unable to detach media from past snapshot that causes warnings,VirtualBox 5.1.14,2017-03-06T18:20:13Z,2017-03-06T19:31:24Z,2017-03-06T19:31:24Z,"Hello world :-)

In VirtualBox 5.1.14 macOS I have noticed that after removing a local ISO file I get this warning on unavailable media. But I am unable to remove this media from the list as it is attached to a past snapshot in one of my machines. So I had to revert the machine state in order to detach the missing image. This caused loss of work progress that I had on the machine I had to revert..

I think it should be possible to detach (missing) media images even from past snapshots..

Best regards,
Tomek",CeDeROM
17612,Unable to create RAWDISK vmdk which includes extended partition,VirtualBox 5.2.8,2018-03-10T13:09:40Z,2020-03-04T10:10:45Z,2020-03-04T10:10:45Z,"System is dual boot between Windows 7 Professional and Debian 9. 
The bare-metal Windows 7 system is installed on a 256GB SSD which has the 
system reserved partition, Windows system partition and two data partitions, one of which is a logical partition. 

Debian has VirtualBox 5.2.8 installed and a separate instance of Windows 7 is installed within a virtual machine which requires RAW DISK access to the two data partitions mentioned above. 

Issuing parted from Debian shows the following (correct) partition structure for the drive,


{{{
Disk /dev/sdb: 256GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  106MB   105MB   primary   ntfs         boot
 2      107MB   41.3GB  41.2GB  primary   ntfs
 3      41.3GB  68.1GB  26.8GB  primary   ntfs
 4      68.1GB  256GB   188GB   extended               lba
 5      68.2GB  256GB   188GB   logical   ntfs 
}}}
 

Issuing the VBoxManage listpartitons -rawdisk command does not give the same results, as shown below.


{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/sdb
Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x07  0   /32 /33  12  /223/19           100         2048
2       0x07  13  /0  /52  1022/254/63         39290       208896
3       0x07  1022/254/63  1022/254/63         25600     80674816 

}}}

It does not appear to have recognised the extended/logical partition 
structure and has also calculated partition 3 as the size of the whole drive.

Attempts to create a RAW DISK vmdk just referencing relative partitions 3 and 5 give the following warning message :


{{{
VBoxManage internalcommands createrawvmdk -filename ""/disk/VM System/Raw Disks/Windows Data.vmdk"" -rawdisk ""/dev/sdb"" -partitions 3,5 -relative
VBoxManage: warning: It is not possible (and necessary) to explicitly give access to the extended partition 5. If required, enable access to all logical partitions inside this extended partition.
RAW host disk access VMDK file /disk/VM System/Raw Disks/Windows Data.vmdk created successfully. 

}}}

Whilst the VMDK is created it does not map the logical partition correctly. When seen from within the Windows 7 guest, the 175GB logical partition shows up as free space.",Feline
16423,Unable to boot after converting .vmdk to .vdi,VirtualBox 5.1.12,2017-01-24T19:17:48Z,2017-01-26T23:06:27Z,2017-01-26T23:06:27Z,"Host: Arch Linux x86_64 with 4.8.13-1-ARCH

After converting a 50GB vmdk file to vdi using the command below, I wasn't able to boot the virtual machine with the newly created vdi file because of a ""fatal error: no bootable medium found"" 

{{{
VBoxManage clonemedium --format VDI actual.vmdk new.vdi
}}}

The conversion went well though. You will find my ''actual.vmdk'' file attached to this post, alongside 2MB of my ''actual-flat.vmdk'', as requested by an IRC user on #vbox.",closingin
17458,"type/mtype can't be set to ""shareable""",VirtualBox 5.2.4,2018-01-16T13:19:19Z,2018-01-17T07:13:22Z,2018-01-17T07:13:22Z,"The virtual drive is erroneously recognized as dynamic. See cmd-responses:

C:\Program Files\VirtualBox>VBoxManage storageattach Win10 --storagectl SATA --port 2 --medium E:\DataW10.vdi --mtype shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 708 of file VBoxManageStorageController.cpp
VBoxManage.exe: error: Failed to set the medium type

C:\Program Files\VirtualBox>VBoxManage modifymedium  disk e:\dataw10.vdi --type shareable
VBoxManage.exe: error: Cannot change type for medium 'E:\DataW10.vdi' to 'Shareable' since it is a dynamic medium storage unit
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: ""COMSETTER(Type)(enmMediumType)"" at line 705 of file VBoxManageDisk.cpp

C:\Program Files\VirtualBox>VBoxManage showmediuminfo disk e:\dataw10.vdi
UUID:           xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Parent UUID:    base
State:          created
Type:           writethrough
Location:       E:\DataW10.vdi
Storage format: VDI
Format variant: fixed default
Capacity:       4096 MBytes
Size on disk:   4098 MBytes
Encryption:     disabled
In use by VMs:  Win10 (UUID: xxxxxxxxxxxxxxxxxxxxx)
",Loafer
14594,Trying to create Windows 10 VB from Parallels 10 Win.hdd,VirtualBox 5.0.4,2015-09-15T20:05:34Z,2016-08-10T17:44:31Z,2016-08-10T17:44:31Z,"I just installed latest version of VB on my mac (5.0.4) and did try to import existing hdd file from parallels 10
When I select :Use existing virtual disk file"" And select Win10 copied from Parallels 10 HDD package I get following error. My Host is 10.11 El Capitan GM (15A282a)

The medium '/Users/rob/Documents/Win10.hdd' can't be used as the requested device type.


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee: 
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Callee RC: 
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
",oxoocoffee
17012,Support Split2G variant for VDI format,VirtualBox 5.1.26,2017-08-14T19:24:24Z,2017-08-14T19:24:24Z,2017-08-14T19:24:24Z,"I would like to have the Split2G variant for VDI just like for VMDK.
I know I could use VMDK, but Virtualbox cannot compact VMDK files.",opensourcer
11486,Support passthrought of TRIM commands to raw partitions,VirtualBox 4.2.6,2013-02-13T13:27:11Z,2017-04-29T14:31:38Z,2017-04-29T14:31:38Z,"Since VirtualBox 4.2 it appears that the AHCI virtual controller supports the ATA TRIM command.

However, only the VDI image file backend actually implements it, where it is used to detect unused blocks so that the image file size can be reduced (if using a dynamic image). The rest of backends do not seem to use it for anything.

My request is for the RAW block device backend to send TRIM/DISCARD commands to the backing block device upon receiving a TRIM command from the guest. 

This would enable e.g. Windows guests on raw partitions (via VMDK's partitionedDevice) sending TRIM commands to a backing SSD device, thereby increasing performance and SSD longevity. 

Unlike discard support for VDI images, this should not involve any extra bookkeeping (""discard"" commands can be sent to the raw block device mostly ""as is"", no need to cluster them).",javispedro
4754,Suggest a new function to install the VDI file to a real physical hardrive,VirtualBox 3.0.0,2009-08-12T00:49:45Z,2010-08-19T20:00:45Z,2010-08-19T20:00:45Z,"Hi, all VBox developers,
I am a 1-year VBox user, fanny about this application.
Thank you all for the masterpiece.

Currently, I have been running Ubuntu(a kind of Linux, as guest OS here) on VBox on Windows(as host OS here) for 1 year and love the Ubuntu OS very much. 
However, how could I put the Ubuntu to a physical hardisk?
That means, how could I write the VDI file to a real phycial hardisk, in which way Ubuntu is on a real and physical machine? 
Is there such a functionality in VBox of next version?

Thanks and waiting. ",jack
16781,Strange handling of encryption keys in case of encrypted media vs. encrypted VM.,VirtualBox 5.1.22,2017-05-24T14:48:07Z,2017-05-24T18:11:11Z,2017-05-24T18:11:11Z,"I have created a new medium and encrypted it according the docs[1] WITHOUT attaching it to a VM first. This succeeded and made me wonder where the encryption keys got saved? According to some blog posts and because of tests I made before with encryption on VM level, those should be saved in the XML config of a VM, but in my case I didn't have a VM the media was attached to. I had a look in the global configuration file of the user running the VBoxManage command as well and didn't find any keys.

So where should the keys be saved if only a new medium was created and encrypted, e.g. using VBoxManage, WITHOUT attaching that medium to a VM before encryption?

Afterwards I attached the newly created, encrypted media to some test VM and at some point recognized keys in the XML config of the test VM. Did some testing and stuff and removed the medium from the test VM again to attach it to another VM. But looking at the config of the first test VM, the keys of the re-attached medium is still present there, not in the VM where the medium is currently attached to. Additionally, it is really ONLY attached to the new VM, not the former test VM anymore.

Shouldn't the keys now be part of the one and only VM the medium is attached to? I'm supposed to backup the keys for all media, but how should I do that reliably if I can't be sure where the keys are actually stored? In my case the first VM was for test purposes, the second for production. What happens if I delete the test VM now, still containing the keys of my encrypted medium, even if it's not attached anymore?

I couldn't find any more detailed documentation about where VirtualBox stores the keys when and if/how/when those parts of the config are moved in case of attaching and removing encrypted media from VMs. Looking at how important those keys are, I strongly suggest adding some paragraphs to the docs how to deal with those and what VirtualBox does automatically. Or not at all, because in my case it doesn't seem to move case around as expected...

[1]: https://www.virtualbox.org/manual/ch09.html#diskencryption-encryption",Thorsten Schöning
17487,Strange behaviour of linked clones.,VirtualBox 5.2.6,2018-01-20T10:18:12Z,2018-08-01T05:31:41Z,2018-08-01T05:31:41Z,"This one was reported by a user in the forums here: https://forums.virtualbox.org/viewtopic.php?f=6&t=86354&start=15.

I have reproduced the behaviour he reports and must admit that I find it hard to explain.

The behaviour is that, if you create a linked clone then the difference image for the clone is registered in the media register of the base VM, not in the .vbox file of the clone. Surely the media should be registered with the VM which owns the media?

This is not a problem as long as both VMs remain registered. However, if you unregister the clone VM then the media is deleted from the parent VM register. When you try to re-register the clone VM (e.g. you wanted to move it to another drive) you get a media not found error.

It's possible there is some reason for this that escapes me, but frankly it seems like a bug. Of course it would normally escape attention as long as the two VMs remain registered.",mpack
18964,storageattach --hotpluggable while running makes disk unremovable,VirtualBox 5.2.32,2019-09-25T17:36:26Z,2020-01-24T03:41:58Z,2020-01-24T03:41:58Z,"Machine `w10` is running. I do:
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi --hotpluggable on
VBoxManage: error: The machine is not mutable (state is Running)
VBoxManage: error: Details: code VBOX_E_INVALID_VM_STATE (0x80bb0002), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: ""SetHotPluggableForDevice(Bstr(pszCtl).raw(), port, device, TRUE)"" at line 901 of file VBoxManageStorageController.cpp
}}}

I expect it to complete successfully as I explicitly enable hot-plugging when actually hot-plugging. But it's not all.

The biggest problem is that the disk get irreversibly associated with the VM! Neither attaching the disk again to this or another VM, nor `closemedium`, nor Release/Remove in Virtual Media Manager after unregistering the VM help.

{{{
gsovetov@gsovetov:~$ VBoxManage storageattach w10 --storagectl SATA --port 4 --type hdd --medium po.vdi 
VBoxManage: error: Cannot attach medium '/home/gsovetov/po.vdi' {47bb8284-7df3-42db-8132-c7d1248ee59d}: medium is already associated with the current state of machine uuid {490c11af-e66f-45fa-9e7d-f9f8ed156169}!
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""AttachDevice(Bstr(pszCtl).raw(), port, device, DeviceType_HardDisk, pMedium2Mount)"" at line 776 of file VBoxManageStorageController.cpp
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showvminfo w10 --machinereadable | grep -iE 'storage|sata'
storagecontrollername0=""SATA""
storagecontrollertype0=""IntelAhci""
storagecontrollerinstance0=""0""
storagecontrollermaxportcount0=""30""
storagecontrollerportcount0=""8""
storagecontrollerbootable0=""on""
""SATA-0-0""=""/home/gsovetov/VirtualBox VMs/w10/Snapshots/{e27504b0-359a-4caf-bbaa-6770cc83fff1}.vdi""
""SATA-ImageUUID-0-0""=""e27504b0-359a-4caf-bbaa-6770cc83fff1""
""SATA-1-0""=""none""
""SATA-2-0""=""none""
""SATA-3-0""=""none""
""SATA-4-0""=""none""
""SATA-5-0""=""none""
""SATA-6-0""=""none""
""SATA-7-0""=""none""
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage list hdds | grep -C5 po

UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Capacity:       100 MBytes
Encryption:     disabled

}}}

{{{
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
In use by VMs:  w10 (UUID: 490c11af-e66f-45fa-9e7d-f9f8ed156169)
}}}

{{{
gsovetov@gsovetov:~$ VBoxManage unregistervm w10  
gsovetov@gsovetov:~$ VBoxManage showmediuminfo po.vdi 
UUID:           47bb8284-7df3-42db-8132-c7d1248ee59d
Parent UUID:    base
State:          created
Type:           normal (base)
Location:       /home/gsovetov/po.vdi
Storage format: VDI
Format variant: dynamic default
Capacity:       100 MBytes
Size on disk:   2 MBytes
Encryption:     disabled
VBoxManage: error: Could not find a registered machine with UUID {490c11af-e66f-45fa-9e7d-f9f8ed156169}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee nsISupports
VBoxManage: error: Context: ""FindMachine(machineIds[i], pMachine.asOutParam())"" at line 1375 of file VBoxManageDisk.cpp
gsovetov@gsovetov:~$ VBoxManage closemedium /home/gsovetov/po.vdi
VBoxManage: error: Medium '/home/gsovetov/po.vdi' cannot be closed because it is still attached to 1 virtual machines
VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""Close()"" at line 1648 of file VBoxManageDisk.cpp
}}}

The only way to detach it is to power off all VMs, wait for VBoxSVC to terminate, then manually remove the record from XML file, then run GUI and open Virtual Media Manager and remove the disk there.",georgesovetov
16989,Snapshots should store differencing disks alongside parent virtual disks,VirtualBox 5.1.26,2017-08-07T17:23:26Z,2017-08-15T17:01:59Z,2017-08-15T17:01:59Z,"With a VM with the VDI stored on volume J:\, after creating a snapshot, the differencing VDI is stored under C:\%USERNAME%\VirtualBox VMs\.

The VDI was stored on another volume due to space issues on C:, and the differencing disk ended up using up all space on C: when it should have been on J:",Jessica Hamilton
21057,Snapshots restore files on Writetrough Disk,VirtualBox 6.1.36,2022-08-09T18:50:57Z,2022-08-09T18:50:57Z,2022-08-09T18:50:57Z,"Hello dear support team. My snapshots restore files on Writetrough Disk.
Here my thread on forum https://forums.virtualbox.org/viewtopic.php?f=6&t=106742

I use two VDI on my VM. First VDI: Normal type. Created for system using (OS, applications, system configuration). I want to take snapshots only from Normal disk type.
Second VDI: Write-through type. Created for file storage. I don't want to take snapshot from Write-through disk.
But files are restored on Write-through disk... I do not understand anything.
Please check me step by step. I will try to be as detailed as possible.
1. I created new VM with new VDI (Normal type for system using). Capacity 30GB. Screenshot https://www.dropbox.com/s/gy764nib8kljrdc/Screenshot_8.png?dl=0
2. I created new VDI (Write-through type for file storage). Capacity 50GB. https://www.dropbox.com/s/2g2cfr621yuqo93/Screenshot_12.png?dl=0
3. Check attached to VM disks. https://www.dropbox.com/s/8ospntq1fx4w9l5/Screenshot_16.png?dl=0 second https://www.dropbox.com/s/8zr79tm9zp6a2ny/Screenshot_17.png?dl=0
4. Now I'm install Windows 10 on 30GB disk (Normal type) https://www.dropbox.com/s/g0uk8bkozy51scy/Screenshot_18.png?dl=0
5. Initialization wright-trough disk after Windows installation https://www.dropbox.com/s/0dnlszujxk5akcw/Screenshot_19.png?dl=0
6. Now I have 2 local disk in Windows Explorer https://www.dropbox.com/s/tw8vf0c14dcf18j/Screenshot_22.png?dl=0
Now it will be interesting
7. Create test folders https://www.dropbox.com/s/fhv3vg2x9z4gnhv/Screenshot_23.png?dl=0
8. Take snapshot https://www.dropbox.com/s/ce1x0r39d34ebfy/Screenshot_25.png?dl=0
9. Test folders deleted using SHIFT+DEL https://www.dropbox.com/s/icjf5t3wyjmz4qh/Screenshot_28.png?dl=0
10. Shutting down VM and restore Test 1 snapshot https://www.dropbox.com/s/orv5cr5ijt29v65/Screenshot_31.png?dl=0
I expect to restore test folder on only drive C:\ (Normal type)
11. Why test folder restored on Write-trough disk (E:\)? https://www.dropbox.com/s/edqmh7ojn7ngmbx/Screenshot_33.png?dl=0",CyanCetus
14058,Snapshots does not work if VHD files are not in default VB folder,VirtualBox 4.3.26,2015-04-19T13:40:06Z,2018-11-20T11:07:58Z,2018-11-20T11:07:58Z,"I use Virtual Box in Windows 7 Prof machine using VHD hard drives.  The snapshots feature does not work if the VHD files are not in the default virtual machine folder (C:\Users\[username]\VirtualBox VMs\[VM name]\).

The error I get when trying to start a VM with snapshot taken in this case is:
----------------
Failed to open a session for the virtual machine XPMCEV.

No error info.

Result Code: E_FAIL (0x80004005)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
-----------------

If I try to delete the snapshot I get the following error:
-----------------
Failed to delete the snapshot Snapshot 1 of the virtual machine XPMCEV.

Parent UUID {00000000-0000-0000-0000-000000000000} of the medium 'C:\Users\T\VirtualBox VMs\XPMCEV\Snapshots\{aa909f03-903f-49a6-95e4-86be9b669c90}.vhd' does not match UUID {58c773b9-e66b-2a4f-a805-91367074598d} of its parent medium stored in the media registry ('C:\Users\T/.VirtualBox\VirtualBox.xml').

Result Code: E_FAIL (0x80004005)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
-----------------

When I move the VHD file to the default machine folder, the snapshot works.

I put the VHD file in a different drive due to space and performance constraints.

The snapshot feature really makes it easy to test and rollback changes when needed.

Thank you in advance.",S T
20039,Snapshot remove from disk but still in logical path,VirtualBox 6.1.16,2020-11-15T14:50:31Z,2020-11-15T14:52:24Z,2020-11-15T14:52:24Z,"While the VM is running, I remove a snapshot. The removed snapshot is a parent snapshot of the running state. The snapshot is removed from disk but is still in the virtual media tree. 
In consequence the VM can't be started because the media (deleted) can't be read 

I tried to remove the media from the media manager, but the manager can't removed from the list because this media has 1 child.

How can I solve this problem and rescue the VM (the snapshot removed is a very old one and i need to restore on of his child).
 

 



 ",dingdingdong
16936,Snapshot Deletion of Encrypted VM always corrupts filesystem,VirtualBox 5.1.24,2017-07-22T16:27:41Z,2019-01-24T20:23:59Z,2019-01-24T20:23:59Z,"Given this setup:

* Windows 10 Pro Host
* VitrualBox 5.1.22/24
* Ubuntu 16.04 Guest
* VBox Additions Installed
* Guest is encrypted.
* VBox Web Service is running

I wrote a java tool that uses the web service and does the typical thing in creating a VM backup.  This includes taking a snapshot prior to copying the VDI(s) to an archive and then once completed, deletes the snapshot.  This occurs while the VM is running (or off as well).  The duration of the VM running on the snapshot is probably on the order of 20-30 minutes.

I have several VMs I use day to day. 1 is encrypted and the other 1 isn't.  Invariably the deletion of the snapshot on the encrypted VM results in a corrupt and non-bootable system even though the merge back into the parent is 100% successful.  This does not happen on the non-encrypted VM.

As an additional validation of the issue, I removed the encryption from the encrypted VM and I do the same thing with my java tool.  No problems at all and the VM is fine.  I put the encryption back on the VM and get the same original corruption problem.

In addition I run the tool with the encrypted VM off, and I don't see the problem.  All works as expected.

I've run this over 10 times and the same thing happens every time.  My running + encrypted VM always corrupts the filesystem when the Snapshot deletion/merge occurs.

I read another Bug report on the VirtualBox support site that states the same thing (from a few versions back I believe).

Thanks and let me know what else you need.

",declay
8625,Shared Floppy Images cannot be accessed from several VMs,VirtualBox 4.0.4,2011-03-24T09:16:41Z,2011-03-24T09:16:41Z,2011-03-24T09:16:41Z,"Host: Win7, x64, VBox 4.0.4

I have a shared floppy image, read-only. 

After I start first VM, second VM wouldn't start, erroring: ""Locking of Attached Media Failed"".

I expect read-only floppy images to be accessible to many VMs at once. (like ISO)

-Technologov",Technologov
18711,SCSI port 7 can not be used,VirtualBox 5.2.30,2019-06-15T08:59:45Z,2019-06-16T13:34:02Z,2019-06-16T13:34:02Z,"[root@rac01-priv ~]# lsscsi -d
[0:0:0:0]    disk    ATA      VBOX HARDDISK    1.0   /dev/sda [8:0]
[2:0:0:0]    disk    VBOX     HARDDISK         1.0   /dev/sdb [8:16]
[2:0:1:0]    disk    VBOX     HARDDISK         1.0   /dev/sdc [8:32]
[2:0:2:0]    disk    VBOX     HARDDISK         1.0   /dev/sdd [8:48]
[2:0:3:0]    disk    VBOX     HARDDISK         1.0   /dev/sde [8:64]
[2:0:4:0]    disk    VBOX     HARDDISK         1.0   /dev/sdf [8:80]
[2:0:5:0]    disk    VBOX     HARDDISK         1.0   /dev/sdg [8:96]
[2:0:6:0]    disk    VBOX     HARDDISK         1.0   /dev/sdh [8:112]
[2:0:8:0]    disk    VBOX     HARDDISK         1.0   /dev/sdi [8:128]
[2:0:9:0]    disk    VBOX     HARDDISK         1.0   /dev/sdj [8:144]
[2:0:10:0]   disk    VBOX     HARDDISK         1.0   /dev/sdk [8:160]

As you can see, when I attach disks to SCSI controller, I can never use the 7th one:  [2:0:7:0]. My OS is oracle linux 7.6",Nil
9723,"same disk boots with fullDevice, but not with partitionedDevice",VirtualBox 4.1.2,2011-10-08T20:53:59Z,2011-10-08T20:53:59Z,2011-10-08T20:53:59Z,"i've recently started to use vbox with debian stable, don't remember which version, and then switched to debian unstabe because of unsupported hw. with that vbox got upgraded to 4.1.2_Debian r38459

what i'm doing and what used to work before this:
 - i boot/attach the physical disk to the guest
 - to avoid screwing up the boot fs, i replace its FLAT entry to ZERO in the vmdk file

after the upgrade it stopped working: grub hangs before it could bring up the menu. so, while searching for a workaround, i switched to using the whole disk, and then everything works fine. but just now i f***d up my hypervisor, because vbox opened a warning window and grabbed my keyboard and i couldn't get to grub within the default 5 secs, and it booted the already booted linux... ARGH!

the command i use to create the virtual disk:
VBoxManage internalcommands createrawvmdk -filename /opt/virtualbox-images/sda.vmdk -rawdisk /dev/disk/by-id/ata-KINGSTON_SNVP325S2256GB_30LS10FHT74Z -partitions 1,2,3,5,6,7

i'm attaching my current, edited version of the vmdk, but the same happens with the original, unedited one.

one unusual thing is that my partitions in the partition table are not in disk layout order.",attila.lendvai
12352,Request: Option to store differencing image on same host device as base image,VirtualBox 4.2.18,2013-11-12T20:33:09Z,2013-11-12T20:33:09Z,2013-11-12T20:33:09Z,"I have a host with two drives, one SSD and one HD.
I have a guest with two .vdi's. The guest os (/) is on the host SSD and file storage .vdi (/home) is on the larger host HD.
However when snapshots are used, the differencing image is always stored in the default VM location. This makes snapshots unusable with multiple host storage locations.
whatever folder structure you would like is fine, (i.e. subfolder called snapshots) I would just like to see an option to store the differencing images on the same host media.

I have read through the forums, about the closest thing I've found was a request for a custom differencing folder (ramdisk)",ImEdwardo
5595,Request: built in VDI disk-size optimization routine,VirtualBox 3.0.12,2009-11-30T02:44:58Z,2018-08-11T05:39:54Z,2018-08-11T05:39:54Z,"Currently there are few available routes for shrinking a VDI image file successfully. Zeroing unused space is an unsupported requirement which requires software outside of virtualbox. Additionally, third party utilities can be flakey, or may not exist for the platform at hand. A terrific addition would be an integrated solution to the problem of dynamically expanding storage. Perhaps an all encompassing routine a user can run to clean up wasted space in a VDI file (i.e. shrink them in place), incorporated directly into virtualbox, without the need to run third party software.",DGF
19410,"Remove, and delete files of the VMs will close the Virtualbox",VirtualBox 6.1.4,2020-03-17T07:28:35Z,2020-03-17T10:57:18Z,2020-03-17T10:57:18Z,"I just upgraded the application to 6.1.4.r136177(Qt5.6.2), the first thing I did to remove old VMs which was migrated from the old version.

I have around 7 VMs and deleted them one by one and to be specific , the problem occurred only when I removed and deleted files of Linux OS.

attached is the Event viewer event.",Mahmood.Shehab
14854,regression: failed to open session VD: error VERR_NOT_SUPPORTED opening image file,VirtualBox 5.0.10,2015-11-21T04:10:57Z,2015-11-22T10:29:34Z,2015-11-22T10:29:34Z,"I have a VM that uses raw disk function for an SSD partition, with the proper permissions to do so on OS X. There is a .vmdk file created to point to this partition. The VM works without error using VirtualBox 5.0.0 but somewhere between 5.0.1 and 5.0.8 this now results in an error. I'm using 5.0.10 for this bug report.

Host: Mac OS X 10.9.5
Guest: Fedora 23 (but the VM fails before I even get to the emulated firmware)",Chris Murphy
14461,Raw disk VM gives ahci-0-0 BLKCACHE_IIOERR if block cache turned off on VirtualBox 5.0.1 and later => fixed in SVN/5.0.x,VirtualBox 5.0.2,2015-08-17T17:46:41Z,2021-06-27T12:09:02Z,2021-06-27T12:09:02Z,"VirtualBox builds 5.0.2-102096 and 5.0.1-102010 fail to run correctly a full-raw-disk-based virtual machine that 5.0.0-101573 loads correctly. The failure occurs when the ""Use Host I/O Cache"" option (StorageController: useHostIOCache) is off for the controller of the raw VMDK.

This is the case even though VirtualBox is being run as an administrator, which I've found required for it to work with raw disks at all. Maybe something changed about what process accessed the drive?

The machine doesn't die straight away, but immediately after the initrd system loads up - the ""Root: clean"" line of fsck is printed (there are many things that happen just after that, so I don't want to imply it's part of fsck) - it freezes and a message is printed:

----

An error has occurred during virtual machine execution! The error details are shown below. You may try to correct the error and resume the virtual machine execution.

The I/O cache encountered an error while updating data in medium &quot;ahci-0-0&quot; (rc=VERR_ACCESS_DENIED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.

Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error

----

The log also mentions ""Invalid machine state Paused when checking if the guest entered the ACPI mode"".

----
ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Invalid machine state Paused when checking if the guest entered the ACPI mode)}, preserve=false aResultDetail=0
00:00:10.967017 Console: Machine state changed to 'Stopping'
----
Host is Windows Vista 32-bit, guest is Debian 8.x 64-bit (though I figure it probably doesn't matter so I left the type as 'all'). The controller is the LSI logic, listed as ""AHCI"" in the GUI.

Attached are logs from when the files work, and when they don't, and the vmdk and vbox in question.",Laurence 'GreenReaper' Parry
14613,raw disk access to bootcamp partition fails with 5.0.2 & 5.0.4,VirtualBox 5.0.4,2015-09-20T16:20:44Z,2016-05-25T00:50:03Z,2016-05-25T00:50:03Z,"I've had a Windows 7 guest configured for raw disk access to my bootcamp partition for a long time.  The guest works in VirtualBox 5.0.0, but it fails to start in the version 5.0.2, and 5.0.4.  I've attached the VBox.log file and contents of the pop-up error from version 5.0.4.

Reverting to 5.0.0 fixes the problem.",aschmitz
19416,random file system corrruption on Windows 10,VirtualBox 6.1.4,2020-03-20T15:59:35Z,2020-03-20T16:15:32Z,2020-03-20T16:15:32Z,"My system info:



{{{
Host Name:                 PENTIUM
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          vagiz
Registered Organization:
Product ID:                00330-80000-00000-AA650
Original Install Date:     2/29/2020, 8:24:00 AM
System Boot Time:          3/19/2020, 1:14:52 AM
System Manufacturer:       Micro-Star International Co., Ltd.
System Model:              MS-7B98
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~3696 Mhz
BIOS Version:              American Megatrends Inc. 1.80, 12/25/2019
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume5
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (UTC) Coordinated Universal Time
Total Physical Memory:     16,248 MB
Available Physical Memory: 5,630 MB
Virtual Memory: Max Size:  16,248 MB
Virtual Memory: Available: 1,731 MB
Virtual Memory: In Use:    14,517 MB
Page File Location(s):     N/A
Domain:                    WORKGROUP
Logon Server:              \\PENTIUM
Hotfix(s):                 8 Hotfix(s) Installed.
                           [01]: KB4534132
                           [02]: KB4497727
                           [03]: KB4500109
                           [04]: KB4503308
                           [05]: KB4537759
                           [06]: KB4538674
                           [07]: KB4541338
                           [08]: KB4551762
Network Card(s):           3 NIC(s) Installed.
                           [01]: Intel(R) Ethernet Connection (7) I219-V
                                 Connection Name: Ethernet
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.1.1
                                 IP address(es)
                                 [01]: 192.168.1.30
                                 [02]: fe80::2525:f387:2d51:482c
                                 [03]: fdaa:bbcc:ddee:0:d549:d972:f087:7aea
                                 [04]: fdaa:bbcc:ddee:0:98a1:602:e24a:c661
                                 [05]: fdaa:bbcc:ddee:0:2525:f387:2d51:482c
                           [02]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::c0ff:26ea:bebe:8ea6
                           [03]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.18.26.193
                                 [02]: fe80::1819:a7d9:5836:496b

}}}
Vagrant file:

{{{
Vagrant.configure(""2"") do |config|
  # The most common configuration options
  # https://docs.vagrantup.com.

  # boxes at https://vagrantcloud.com/search.
  # https://app.vagrantup.com/bento
  config.vm.box = ""bento/centos-7""

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing ""localhost:8080"" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  config.vm.network :forwarded_port, guest: 22, host: 12022
  config.vm.network :forwarded_port, guest: 12080, host: 12080
  config.vm.network :forwarded_port, guest: 12443, host: 12443
  #config.vm.synced_folder ""."", ""/vagrant"", :mount_options => [""dmode=777"",""fmode=666""]
  config.ssh.username = 'vagrant'
  config.ssh.password = 'vagrant'
  config.ssh.insert_key = false
  config.vm.provider ""virtualbox"" do |vb|
        vb.memory = ""1600""
        vb.cpus = ""2""
        end
end
}}}

Random file corruption, e.g. wget https://files.phpmyadmin.net/phpMyAdmin/4.9.4/phpMyAdmin-4.9.4-english.tar.gz

I have tried Hyper-V on/off multiple times with different disks: SSD, NVMe, SATA and disable/enable windows/Vagrant caching.
sometimes cannot even boot from the beginning (system displays emergency mode). tried to reinstall VirtualBox multiple times, use different install image version. nothing changed, random corruption especially with heavy write.

as an example, internal MariaDB output when importing:

{{{
Mar 20 14:22:37 localhost systemd: Starting MariaDB 10.4.12 database server...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] /usr/sbin/mysqld (mysqld 10.4.12-MariaDB) starting as process 8606 ...
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using Linux native AIO
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Uses event mutexes
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Number of pools: 1
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: Completed initialization of buffer pool
Mar 20 14:22:38 localhost mysqld: 2020-03-20 14:22:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Waiting for purge to start
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: 10.4.12 started; log sequence number 60496037333; transaction id 79440
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Mar 20 14:22:40 localhost mysqld: 2020-03-20 14:22:40 0 [Note] Plugin 'FEEDBACK' is disabled.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] 'proxies_priv' entry '@% root@localhost.localdomain' ignored in --skip-name-resolve mode.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] InnoDB: Buffer pool(s) load completed at 200320 14:22:41
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Reading of all Master_info entries succeeded
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] Added new Master_info '' to hash table
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=localhost-relay-bin' to avoid this problem.
Mar 20 14:22:41 localhost mysqld: 2020-03-20 14:22:41 0 [Note] /usr/sbin/mysqld: ready for connections.
Mar 20 14:22:41 localhost mysqld: Version: '10.4.12-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 0  MariaDB Server
Mar 20 14:22:41 localhost systemd: Started MariaDB 10.4.12 database server.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=256128, page number=2147483648], should be [page id: space=1511, page number=3530]
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace hpci/articles page [page id: space=1511, page number=3530]. You may have to recover from a backup.
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):
Mar 20 14:46:44 localhost mysqld: len 16384; hex 00000000800000000000000000003c000000a2998f692000998f692efb00000137000003e8800102000258003780000000003420a6000000000000800000000000000000003c000000a3998f693000998f693efb00000137000003e8800102000260003780000000003420a7000000000000800000000000000000003c000000a4998f694000998f694efb00000137000003e8800102040268003780000000003420a8000000000000800000000000000000003c000000a5998f695000998f695efb00000137000003e8800102000270003780000000003420a9000000000000800000000000000000003c000000a6998f696000998f696efb00000137000003e8800102000278003780000000003420aa000000000000800000000000000000003c000000a7998f697000998f697efb00000137000003e8800102000280003780000000003420ab000000000000800000000000000000003c00000000998f6a0000998f6a0efb00000137000003e8800102040288003780000000003420ac000000000000800000000000000000003c00000001998f6a1000998f6a1efb00000137000003e8800102000290003780000000003420ad000000000000800000000000000000003c00000002998f6a2000998f6a2efb00000137000003e8800102000298003780000000003420ae000000000000800000000000000000003c00000003998f6a3000998f6a3efb00000137000003e88001020002a0003780000000003420af000000000000800000000000000000003c00000004998f6a4000998f6a4efb00000137000003e88001020402a8003780000000003420b0000000000000800000000000000000003c00000005998f6a5000998f6a5efb00000137000003e88001020002b0003780000000003420b1000000000000800000000000000000003c00000006998f6a6000998f6a6efb00000137000003e88001020002b8003780000000003420b2000000000000800000000000000000003c00000007998f6a7000998f6a7efb00000137000003e88001020002c0003780000000003420b3000000000000800000000000000000003c00000008998f6a8000998f6a8efb00000137000003e88001020402c8003780000000003420b4000000000000800000000000000000003c00000009998f6a9000998f6a9efb00000137000003e88001020002d0003780000000003420b5000000000000800000000000000000003c0000000a998f6aa000998f6aaefb00000137000003e88001020002d8003780000000003420b6000000000000800000000000000000003c0000000b998f6ab000998f6abefb00000137000003e88001020002e0003780000000003420b7000000000000800000000000000000003c0000000c998f6ac000998f6acefb00000137000003e88001020402e8003780000000003420b8000000000000800000000000000000003c0000000d998f6ad000998f6adefb00000137000003e88001020002f0003780000000003420b9000000000000800000000000000000003c0000000e998f6ae000998f6aeefb00000137000003e88001020002f8003780000000003420ba000000000000800000000000000000003c0000000f998f6af000998f6afefb00000137000003e8800102000300003780000000003420bb000000000000800000000000000000003c00000010998f6b0000998f6b0efb00000137000003e8800102040308003780000000003420bc000000000000800000000000000000003c00000011998f6b1000998f6b1efb00000137000003e8800102000310003780000000003420bd000000000000800000000000000000003c00000012998f6b2000998f6b2efb00000137000003e8800102000318003780000000003420be000000000000800000000000000000003c00000013998f6b3000998f6b3efb00000137000003e8800102000320003780000000003420bf000000000000800000000000000000003c00000014998f6b4000998f6b4efb00000137000003e8800102040328003780000000003420c0000000000000800000000000000000003c00000015998f6b5000998f6b5efb00000137000003e8800102000330003780000000003420c1000000000000800000000000000000003c00000016998f6b6000998f6b6efb00000137000003e8800102000338003780000000003420c2000000000000800000000000000000003c00000017998f6b7000998f6b7efb00000137000003e8800102000340003780000000003420c3000000000000800000000000000000003c00000018998f6c0000998f6c0efb00000137000003e8800102040348003780000000003420c4000000000000800000000000000000003c00000019998f6c1000998f6c1efb00000137000003e8800102000350003780000000003420c5000000000000800000000000000000003c0000001a998f6c2000998f6c2efb00000137000003e8800102000358003780000000003420c6000000000000800000000000000000003c0000001b998f6c3000998f6c3efb00000137000003e8800102000360003780000000003420c7000000000000800000000000000000003c0000001c998f6c4000998f6c4efb00000137000003e8800102040368003780000000003420c8000000000000800000000000000000003c0000001d998f6c5000998f6c5efb00000137000003e8800102000370003780000000003420c9000000000000800000000000000000003c0000001e998f6c6000998f6c6efb00000137000003e8800102000378003780000000003420ca000000000000800000000000000000003c0000001f998f6c7000998f6c7efb00000137000003e8800102000380003780000000003420cb000000000000800000000000000000003c00000020998f6c8000998f6c8efb00000137000003e8800102040388003780000000003420cc000000000000800000000000000000003c00000021998f6c9000998f6c9efb00000137000003e8800102000390003780000000003420cd000000000000800000000000000000003c00000022998f6ca000998f6caefb00000137000003e8800102000398003780000000003420ce000000000000800000000000000000003c00000081998f669000998f669efb00000138000003e88001020003a0003780000000003420cf000000000000800000000000000000003c00000082998f66a000998f66aefb00000138000003e88001020403a8003780000000003420d0000000000000800000000000000000003c00000083998f66b000998f66befb00000138000003e88001020003b0003780000000003420d1000000000000800000000000000000003c00000084998f66c000998f66cefb00000138000003e88001020003b8003780000000003420d2000000000000800000000000000000003c00000085998f66d000998f66defb00000138000003e88001020003c0003780000000003420d3000000000000800000000000000000003c00000086998f66e000998f66eefb00000138000003e88001020403c8003780000000003420d4000000000000800000000000000000003c00000087998f66f000998f66fefb00000138000003e88001020003d0003780000000003420d5000000000000800000000000000000003c00000088998f670000998f670efb00000138000003e88001020003d8003780000000003420d6000000000000800000000000000000003c00000089998f671000998f671efb00000138000003e88001020003e0003780000000003420d7000000000000800000000000000000003c0000008a998f672000998f672efb00000138000003e88001020403e8003780000000003420d8000000000000800000000000000000003c0000008b998f673000998f673efb00000138000003e88001020003f0003780000000003420d9000000000000800000000000000000003c0000008c998f674000998f674efb00000138000003e88001020003f8003780000000003420da000000000000800000000000000000003c0000008d998f675000998f675efb00000138000003e8800102000400003780000000003420db000000000000800000000000000000003c0000008e998f676000998f676efb00000138000003e8800102040408003780000000003420dc000000000000800000000000000000003c0000008f998f677000998f677efb00000138000003e8800102000410003780000000003420dd000000000000800000000000000000003c00000090998f680000998f680efb00000138000003e8800102000418003780000000003420de000000000000800000000000000000003c00000091998f681000998f681efb00000138000003e8800102000420003780000000003420df000000000000800000000000000000003c00000092998f682000998f682efb00000138000003e8800102040428003780000000003420e0000000000000800000000000000000003c00000093998f683000998f683efb00000138000003e8800102000430003780000000003420e1000000000000800000000000000000003c00000094998f684000998f684efb00000138000003e8800102000438003780000000003420e2000000000000800000000000000000003c00000095998f685000998f685efb00000138000003e8800102000440003780000000003420e3000000000000800000000000000000003c00000096998f686000998f686efb00000138000003e8800102040448003780000000003420e4000000000000800000000000000000003c00000097998f687000998f687efb00000138000003e8800102000450003780000000003420e5000000000000800000000000000000003c00000098998f688000998f688efb00000138000003e8800102000458003780000000003420e6000000000000800000000000000000003c00000099998f689000998f689efb00000138000003e8800102000460003780000000003420e7000000000000800000000000000000003c0000009a998f68a000998f68aefb00000138000003e8800102040468003780000000003420e8000000000000800000000000000000003c0000009b998f68b000998f68befb00000138000003e8800102000470003780000000003420e9000000000000800000000000000000003c0000009c998f68c000998f68cefb00000138000003e8800102000478003780000000003420ea000000000000800000000000000000003c0000009d998f68d000998f68defb00000138000003e8800102000480003780000000003420eb000000000000800000000000000000003c0000009e998f68e000998f68eefb00000138000003e8800102040488003780000000003420ec000000000000800000000000000000003c0000009f998f68f000998f68fefb00000138000003e8800102000490003780000000003420ed000000000000800000000000000000003c000000a0998f690000998f690efb00000138000003e8800102000498003780000000003420ee000000000000800000000000000000003c000000a1998f691000998f691efb00000138000003e88001020004a0003780000000003420ef000000000000800000000000000000003c000000a2998f692000998f6974732061637469766573206120677265656e206c6561662067726164652061732077656c6c20617320696e6469636174696e67207768696368206172652045636f6365727420617070726f7665642c20776869636820617265207072657365727661746976652d6672656520616e64207768696368207061726162656e2d667265652e203c2f703e3c703e43726f64612068617320616c736f20676f6e6520646f776e2074686520677265656e20726f7574652c206c61756e6368696e6720557020436c6f736520616e6420477265656e2c2061206e657720677265656e20677569646520746f20697473207370656369616c69747920726177206d6174657269616c732e2054686520677569646520656e61626c657320666f726d756c61746f727320746f2064657465726d696e6520686f7720677265656e20612070726f647563742069732c2077697468207265666572656e636520746f206f726967696e2028706c616e742c20616e696d616c206f72206d696e6572616c292c20706574726f6368656d6963616c732c2073696c69636f6e65732c207072657365727661746976657320616e642062696f6465677261646162696c69747920616d6f6e677374206f74686572732e2054686520677569646520616c736f206665617475726573206120477265656e2043726974657269612074686174206d61726b7320612064656c69626572617465206d6f766520617761792066726f6d207468652063757272656e742063657274696669636174696f6e207374616e646172647320617661696c61626c652e20556e6465722074686520637269746572696120616c6c2070726f647563747320696e20746865206775696465206172652066726565206f6620657468796c656e65206f7869646520616e642070726f70796c656e65206f786964652d626173656420636f6d706f6e656e74732c20636f6e7461696e206e6f20706574726f6c65756d2064697374696c6c617465732c206e6f2070687468616c617465732c206e6f207061726162656e732c206e6f20666f726d616c6465687964652d72656c656173696e67207072657365727661746976657320616e642068617665206e6f74206265656e20746573746564206f6e20616e696d616c732e3c2f703e3c703ee2809c54686572652061726520736f206d616e792064697363726570616e63696573206265747765656e20656163682063657274696669657220746861742077652068617665206c65667420746865206f7074696f6e206f66207768696368207374616e6461726420746f20666f6c6c6f7720746f206f757220637573746f6d6572732ce2809d206578706c61696e6564205361726168204d696c6c6e732c206d61726b6574696e6720636f6d6d756e69636174696f6e7320636f6f7264696e61746f722c20706572736f6e616c2026206865616c746820636172652c2043726f64612e20e2809c57652061726520616c736f2077616974696e6720666f7220746865204575726f7065616e2063657274696669636174696f6e207374616e6461726420746f206c61756e63682c207768696368206d6179206368616e676520736f6d652063726974657269612ee2809d3c2f703e3c703e466f6c6c6f77696e6720746869732073656e74696d656e742c2074686520636f6d70616e792068617320646576656c6f7065642074776f206e65772073756e20636172652070726f64756374732c20536f6c617665696c2043542d33303020616e6420536f6c617669656c20435a2d3330302c20616e642074776f20687964726174696e672070657074696465732066726f6d206f7267616e696320736f75726365732e20487964726f6176656e612048704f20616e6420487964726f657863656c73612048704f20617265206d6f69737475726973696e67206167656e747320646572697665642062792067656e746c6520656e7a796d6174696320687964726f6c79736973206f6620636572746966696564206f7267616e69632063726f70732e3c2f703e3c703e53796d72697365206861732062726f6164656e656420697473206f7267616e696320706f7274666f6c696f2c20616464696e67206e65772070726f647563747320746f20697473204578747261706f6e65204f7267616e69632072616e67652c207768696368206973206261736564206f6e20636f6e74726f6c6c65642068617276657374696e672e204e65772070726f647563747320696e636c756465204e656f2041637469706f6e6520536f6170204e75747368656c6c2c20612031303025206e61747572616c2073757266616374616e74207375697461626c6520666f722075736520696e20706572736f6e616c2063617265206170706c69636174696f6e732073756368206173207368616d706f6f7320616e6420626f6479207761736865732e3c2f703e3c703ee2809c426f74616e6963616c73206172652070726f76656e20696e2073637265656e696e67206d6574686f647320746f20686176652072656c6576616e742065666665637473207375636820617320616e74692d6972726974616e7420616e6420616e74696f786964616e7420666f7220636f736d65746963206170706c69636174696f6e732ce2809d204d69636861656c205363687572696368742c20726567696f6e616c20627573696e657373206d616e616765722c2053796d726973652c20746f6c64205350432e3c2f703e3c703e54686520636f6d70616e792068617320616c736f2072656e616d65642069747320636f736d657469637320627573696e65737320756e69742c2077686963682077696c6c206e6f77206265206b6e6f776e206173204c69666520457373656e7469616c732c20627574206973207374696c6c20612070617274206f662053796d72697365e2809973205363656e7420262043617265206469766973696f6e2e3c2f703e3c703e53696c61622068617320616c736f20656e746572656420746865206f7267616e6963206172656e612c206c61756e6368696e672061206e65772045636f6365727420636572746966696564206f7267616e69632072616e67652c2077686963682077696c6c20696e697469616c6c7920636f6d7072697365207468726565206163746976652070726f6475637473202d204f73696c6966742042696f2c205374727563747572696e652042696f20616e6420566974616e6f6c2042696f2e20203c2f703e3c703e416e64204c69706f20686173206c61756e636865642061206e6577206c696e65206f66206e61747572616c20656d6f6c6c69656e74732c20646572697665642066726f6d2031303025206e61747572616c20706c616e7420736f75726365732e20546865204c69706f6275747465722072616e676520636f6d707269736573203131207661726965746965732c206569676874206f66207768696368206172652076616c6964617465642062792045636f636572742c207768696c652074686520726566696e6564206f7267616e696320736865612076617269616e7420697320636572746966696564206f7267616e69632062792045636f636572742e2056617269657469657320696e636c7564652061707269636f742c20726566696e656420636f636f612c206f6c6976652c206a6f6a6f62612c20726566696e6564206d616e676f20616e6420706561636820616e64206170706c69636174696f6e2073756767657374696f6e7320696e636c75646520736b696e2c2073756e20616e64206861697220636172652070726f64756374732c2066696e6520736f61707320616e6420626f647920627574746572732e3c2f703e3c2f703e3c703e5a656e6974656368e2809973206e6577204d6561646f77666f616d20616e64204f72616e6765206275747465727320616c736f20676976652061206e6f6420746f206e61747572616c2c20776974682045636f636572742076616c69646174696f6e2e205468652070726f647563747320617265207361696420746f206265207375697461626c6520666f7220612076617269657479206f66206170706c69636174696f6e7320696e636c7564696e6720736b696e20636172652c206861697220636172652c20636f6c6f757220636f736d657469637320616e64206e61696c20636172652e203c2f703e3c703ee2809c54686572652069732061206c6f74206f66206e6f6e73656e736520676f696e67206f6e2077697468206e61747572616c20616e64206f7267616e69637320617420746865206d6f6d656e742ce2809d207361696420436172746572204c61205661792c20707265736964656e742c205a656e69746563682e20e2809c54686520696e647573747279206e6565647320746f206368616e6765202d206974e28099732074696d6520776520776f6b6520757020616e64207265616c697365642074686520776f726c64206973206368616e67696e672e204920616d2070757474696e672045636f63657274206f6e2065766572797468696e6720492063616e206265636175736520492062656c6965766520696e20697420736f207374726f6e676c79202d206974e2809973207468652077617920666f72776172642ee2809d3c2f703e3c703e546865206f6e63652066616d696c696172206e616d65206f662046696e6574657820686173206e6f77206265656e2066756c6c79206162736f7262656420696e746f20496e6e6f737065632e205468652066616d696c6961722046696e736f6c7620656d6f6c6c69656e747320617265207374696c6c20617661696c61626c652c20616c74686f7567682070726f64756374696f6e2077617320726563656e746c7920657870616e6465642066726f6d2074686520555320746f204575726f70652028456c6c65736d65726520506f72742c20554b292c2062757420617420746869732079656172e280997320696e2d636f736d65746963732074686520636f6d70616e79207761732070726f6d6f74696e67204e6174726c71756573742045333020696e20706172746963756c61722c20612072656164696c792062696f64656772616461626c65206368656c6174696e67206167656e74207468617420726573706f6e647320746f2063757272656e7420726571756972656d656e74732e20e2809c50656f706c6520617265207265616c6c79207374617274696e6720746f2070617920617474656e74696f6e20746f20677265656e20616e6420677265656e20696e6772656469656e74732ce2809d2073616964205068696c204d6174656e612c20496e6e6f7370656320767020616e642067656e6572616c206d616e616765722e20e2809c5765e280997265207265696e76656e74696e67206f757273656c7665732061732061207370656369616c697479206368656d6963616c7320636f6d70616e7920616e64207765e28099766520676f742061206772656174206e65772070726f64756374206c696e652e204f75722073747261746567792069732067726f777468202d206f7267616e696320616e64207468726f756768206163717569736974696f6e2c2077686572652069742066697473206f75722073747261746567792ee2809d3c2f703e3c703e50726573657276617469766573207765726520616e6f7468657220617265612077686572652074686520677265656e207468656d652070726f647563656420736f6d6520696e746572657374696e67206e65772070726f64756374732e204472205374726165746d616e7320696e74726f64756365642061206e65772045636f636572742d6c697374656420616e74696d6963726f6269616c20696e6772656469656e74207468617420697320636c61696d656420746f2070726f766964652061206e61747572616c20616c7465726e617469766520746f2074686520636f6e76656e74696f6e616c207072657365727661746976657320746861742068617665206265656e20676976656e206120686172642074696d6520627920736f6d65207061727473206f6620746865206d6564696120726563656e746c792e3c2f703e3c703e4465726d61736f6674203638382045636f206973206120706c616e742d62617365642066756e6769636964616c20696e6772656469656e742c20646572697665642066726f6d20626173696c20616e64206973207361696420746f20706f7373657373207375706572696f7220616e74696d6963726f6269616c20636861726163746572697374696373207468616e206f7468657220706c616e74206465726976656420616c7465726e6174697665732063757272656e746c7920617661696c61626c652ee2809c54686572652068617320646566696e6974656c79206265656e206d6f72652064656d616e6420666f7220677265656e2070726f64756374732074686973207965617220616e64206f7572206e65772070726f6475637420686173206265656e206d65742077697468207665727920676f6f6420726573706f6e73652ce2809d20736169642044722e205374726165746d616e73e2809920537573616e6e65204ac3a46e696368656e2e20e2809c576520686176652045636f63657274206c697374696e6720616e6420617265206177616974696e6720536f696c204173736f63696174696f6e2063657274696669636174696f6e2ee2809d203c2f703e3c703e5769746820657665722067726561746572207365676d656e746174696f6e20696e2074686520736b696e206361726520736563746f722c2074686520636f6d7065746974696f6e20746f20646576656c6f7020696e6772656469656e74732074686174206f6666657220616476616e63656420736b696e20636172652062656e656669747320697320617420616e20616c6c2074696d6520686967682e204265696e67206120e28098677265656ee28099206272616e64206973206f6e65207468696e67206275742074686520696e6772656469656e7473206861766520746f2064656c6976657220736f706869737469636174656420726573756c74732e3c2f703e3c703e4761747465666f7373c3a920756e7665696c656420697473206c6174657374206c61756e63682c204379746f62696f6c204c756d696e2d4579652c20616e2061637469766520696e6772656469656e742077697468207374726f6e672076617363756c6f2d70726f746563746976652070726f70657274696573207468617420697320636c61696d656420746f20726564756365206461726b20636972636c657320616e6420707566667920736b696e2061726f756e64207468652065796520617265612e205468652061637469766520636f6e7461696e7320617368206261726b20657874726163742c206f7267616e69632073696c69636f6e20616e6420766974616d696e2042332c20776869636820616374206f6e2074686520736b696ee280997320637574616e656f7573206d6963726f63697263756c6174696f6e2e2056697369626c6520726573756c74732061726520636c61696d6564206166746572203238206461797320616e6420737567676573746564206170706c69636174696f6e7320696e636c7564652065796520636f6e746f75722074726561746d656e74732c207072652d20616e6420706f73742d737572676572792074726561746d656e74732c20616e74692d616765696e67206361726520616e6420666c6173682072616469616e63652074726561746d656e74732e3c2f703e3c703e4d6962656c6c65206d65616e7768696c65206c61756e636865642074776f206e657720616e74692d616765696e6720736b696e206361726520696e6772656469656e7473206261736564206f6e20706c616e7420736369656e63652e20506879746f43656c6c546563204d616c757320446f6d65737469636120697320616e20616374697665206261736564206f6e206170706c65207374656d2063656c6c732074686174207573657320706174656e742070656e64696e6720706c616e742063656c6c2063756c7475726520746563686e6f6c6f677920616e64206973207361696420746f2070726f7465637420736b696e207374656d2063656c6c7320616761696e737420616765696e672061732077656c6c2061732064656c6179696e67207468652073656e657363656e6365206f66206861697220666f6c6c69636c65732c2068656c70696e6720746f2070726573657276652074686520766974616c69747920616e6420796f75746866756c6e657373206f662074686520736b696e2e3c2f703e3c703e416c736f206d616b696e67206974732064656275742066726f6d204d6962656c6c6520776173204173747261466f7263652c20616e20616e74692d616765696e672070726f6475637420646576656c6f70656420666f7220626c656d697368656420736b696e2e2044656d616e6420666f7220616e74692d626c656d6973682070726f647563747320666f72206d6f7265206d61747572652c206e6f6e2d7465656e61676520736b696e2069732067726f77696e672072617069646c7920627574206163636f7264696e6720746f204d6962656c6c652c207468657265206172652076657279206665772070726f647563747320617661696c61626c6520746f207472656174207468697320636f6e646974696f6e2e2054686520696e6772656469656e7420636f6e7461696e7320417374726167616c7573206d656d6272616e61636575732c206120706c616e74207573656420696e20547261646974696f6e616c204368696e657365204d65646963696e652c20616e6420697320636c61696d656420746f206669726d20616e6420736d6f6f746820736b696e2c2072656475636520696d70657266656374696f6e732c2062616c616e636520736562756d2070726f64756374696f6e2c2070726576656e7420627265616b6f75747320616e64206c656176652074686520736b696ee280997320636f6d706c6578696f6e20636c65617220616e6420726566696e65642e3c2f703e3c703e446f7720416d657263686f6c2070726573656e7465642061206e65772c20706174656e742d70656e64696e6720656e63617073756c6174696f6e20616e642064656c69766572792073797374656d2c20536174696e46582c20776869636820656e61626c657320626f746820687964726f70686f62696320616e6420687964726f7068696c6963206163746976657320746f20626520656e63617073756c6174656420696e20612076617269657479206f6620736b696e20636172652070726f64756374732e204974206973207361696420746f2062652076657279206561737920746f206d69782062792073696d706c6520736865617220746f2063726561746520656e63617073756c6174696f6e20616e6420746f207369676e69666963616e746c7920696d70726f7665207468652073746162696c69736174696f6e206f662073656e73697469766520616374697665732061732077656c6c2061732067726561746572206566666963616379206f7665722074696d652e20566974616d696e73204120616e64204320616e64204448412077657265207374756469656420616e6420696d70726f7665642073746162696c697479207761732061636869657665642e20e2809c4974206365727461696e6c7920656e61626c6573207468652064656c6976657279206f66206e61747572616c206163746976657320736f2063616e206265207573656420696e20737570706f7274206f66206e61747572616c20636c61696d732ce2809d20636f6d6d656e746564204a656e6e696665722053696773776f7274682c20627573696e65737320636f6d6d756e69636174696f6e73207370656369616c697374207769746820446f7720416d657263686f6c2e20e2809c416e64207769746820746865206f6e676f696e672064656d616e6420666f72206d756c746966756e6374696f6e616c6974792c20706f74656e7469616c6c7920696e636f6d70617469626c6520696e6772656469656e7473206c696b652044484120616e6420616d696e6f20616369647320666f722073756e6c6573732074616e6e696e6720616e6420616e74692d616765696e672063616e20626520656e63617073756c6174656420746f6765746865722ee2809d20427920656e63617073756c6174696e6720706f74656e7469616c6c792069727269746174696e6720616374697665732c2074686520706f74656e7469616c20666f722069727269746174696f6e20697320726564756365642e20536174696e465820697320616c736f207361696420746f20696d70726f766520746865206165737468657469632070726f70657274696573206f66206661636520637265616d732c206579652067656c2c20736572756d20616e6420626f6479206c6f74696f6e20666f726d756c6174696f6e732e203c2f703e3c703e4c69676874657220616e642062726967687465723c2f703e3c703e5261686e20666f6375736564206f6e20736b696e206c69676874656e696e67206c61756e6368696e672043656c6c4163746976652057686974652c2061206e657720696e6772656469656e7420646576656c6f70656420666f722067656e746c6520736b696e206c69676874656e696e672c20616e6420636f6e7461696e696e67206120636f6d62696e6174696f6e206f6620766974616d696e2042332c2073756c706875726f75732065787472616374206f6620776174657263726573732c2062696f2d617661696c61626c65207a696e6320616e6420616e20457373656e7469616c2043656c6c20426f6f737420466163746f722e20496e20766974726f207465737473206f6e20334420736b696e206d6f64656c732073686f77656420757020746f2035302520726564756374696f6e20696e206d656c616e696e2070726f64756374696f6e20616e6420616e2031312520736b696e206c69676874656e696e67206f6620417369616e20736b696e2e20e2809c546865207461726765742077617320746f20646576656c6f7020616e2061637469766520666f722077686974656e696e67207468617420776173207361666520746f20736b696e2ce2809d206578706c61696e65642044616e69656c61204775696c646d616e6e2c2068656164206f66206d61726b6574696e672c205261686e2e3c2f703e3c703e4c69706f746563206c61756e63686564204368726f6d616272696768742c2061206e657720627269676874656e696e6720616374697665207468617420697320636c61696d656420746f20696e647563652061207369676e69666963616e74206c69676874656e696e67206566666963616379206f6e2074686520736b696e20616e642068656c707320746f20756e69667920736b696e20746f6e652e204368726f6d6f62726967687420646f6573206e6f742073686f7720616e79206379746f746f78696320656666656374732c206f7220616e792069727269746174696f6e206f722073656e73697469736174696f6e207265616374696f6e206163636f7264696e6720746f2074686520636f6d70616e792e3c2f703e3c703e456c656d656e74616c2070726f74656374696f6e3c2f703e3c703ee28098456c656d656e7473206f6620626561757479e280992077617320746865206e657720736c6f67616e20666f722043696261206174207468652073686f772e20e2809c49742064657363726962657320646966666572656e7420656c656d656e7473206f6620746563686e6f6c6f677920756e646572206f6e6520756d6272656c6c61202d207765e2809972652074616b696e672061206d6f726520686f6c697374696320617070726f61636820616e6420636f6d62696e696e6720636f6e6365707473206f66206265617574792c2077656c6c2d6265696e6720616e64206865616c74682ce2809d2073616964204d69636861656c2057696c6b6f702c20627573696e65737320686561642055562070726f74656374696f6e20262061637469766520627573696e657373206c696e6520686f6d65202620706572736f6e616c20636172652c20436962612e2054686520636f6d70616e79207761732070726f6d6f74696e6720e2809c62657474657220616765696e67e2809d2061732061206d6f726520706f73697469766520776179206f66206c6f6f6b696e6720617420616765696e672c206965206865616c746869657220616765696e67207468726f75676820616e20616e74692d616765696e6720617070726f61636820617320756e666f7274756e6174656c792061676520726576657273616c206973206e6f7420706f737369626c652e205468652069646561206973207468617420746869732063616e206265206163686965766564207468726f75676820757365206f662043696261e28099732054696e6f736f72622055562066696c746572732c2054696e6f6465726d206d6f6973747572697365727320616e642054696e6f6465726d20656e63617073756c6174656420616374697665733b2043696261207361696420697420657870656374732054696e6f736f7262205320616e642054696e6f736f7262204d20746f206761696e20616363657074616e636520696e207468652055532074686973207965617220736f20706c616e7320746f20626520726561647920666f7220746865206d6174657269616c7320746f20626520696e636c7564656420696e2066696e69736865642070726f6475637473206e65787420796561722e20e2809c57652077616e7420746f20657874656e64207468652073636f7065206f66206f75722061637469766974696573202d206974e2809973206e6f74206f6e6c7920612062656175747920746f7069632c206974e28099732061206865616c74682069737375652ee2809d20556c69204f7374657277616c6465722c20676c6f62616c206d61726b6574696e67206d616e616765722055562070726f74656374696f6e20616e642061637469766520656666656374732061646465643a20e2809c436962612077617320616e206561726c7920706c6179657220696e2055564120736f207765e2809972652061206d61726b6574206c65616465722e205765206e6f772077616e7420746f20776f726b207769746820637573746f6d65727320746f20636f6e76657920746865206d65737361676520746f2074686520756c74696d61746520636f6e73756d65722ee2809d2054686520636f6d70616e7920616c736f2077616e747320746f20776f726b2077697468206465726d61746f6c6f676973747320746f20696d70726f76652074686520756e6465727374616e64696e67206f662073756e2070726f74656374696f6e2074686572652e20e2809c5468657920646f6ee280997420616c6c20756e6465727374616e642053504620616e64206974e2809973207665727920696d706f7274616e742074686174207468657920646f2ce2809d2073616964204f7374657277616c6465722e20e2809c4974e280997320696d706f7274616e7420746f20776f726b206f6e2074686520696d616765206f662073756e73637265656e7320627574207765e28099726520636f756e74696e67206f6e20746865206661637420746861742070656f706c652077696c6c20616c776179732077616e7420746f206578706f7365207468656d73656c76657320746f2073756e2e20416e6420766974616d696e204420646566696369656e6379206973206e6f77206265696e67207365656e206173206265696e6720726573706f6e7369626c6520666f722061206c6f74206f662063616e636572732c207768696c6520766974616d696e2044207265717569726573205556422e204275742070726f74656374696f6e20636f6d65732066697273742ee2809d203c2f703e3c703e4e657874206d6f6e7468205350432077696c6c207265706f7274206f6e206d616e79206d6f7265206c61756e6368657320616e64206576656e74732066726f6d207468652073686f772c20696e636c7564696e6720746869732079656172e280997320696e737069726174696f6e616c20696e2d666f63757320666561747572652c2055746f7069612c20616e6420746865206576657220706f70756c6172207472656e64732070726573656e746174696f6e732e203c2f703e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000772915fce46b8b1f; asc               <      i    i.    7         X 7     4                  <      i0   i>    7         ` 7     4                  <      i@   iN    7         h 7     4                  <      iP   i^    7         p 7     4                  <      i`   in    7         x 7     4                  <      ip   i~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j.    7           7     4                  <      j0   j>    7           7     4                  <      j@   jN    7           7     4                  <      jP   j^    7           7     4                  <      j`   jn    7           7     4                  <      jp   j~    7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      j    j     7           7     4                  <      k    k     7           7     4                  <      k    k     7           7     4                  <      k    k.    7           7     4                  <      k0   k>    7           7     4                  <      k@   kN    7         ( 7     4                  <      kP   k^    7         0 7     4                  <      k`   kn    7         8 7     4                  <      kp   k~    7         @ 7     4                  <      l    l     7         H 7     4                  <      l    l     7         P 7     4                  <      l    l.    7         X 7     4                  <      l0   l>    7         ` 7     4                  <      l@   lN    7         h 7     4                  <      lP   l^    7         p 7     4                  <      l`   ln    7         x 7     4                  <      lp   l~    7           7     4                  <      l    l     7           7     4                  <   !  l    l     7           7     4                  <   ""  l    l     7           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      f    f     8           7     4                  <      g    g     8           7     4                  <      g    g     8           7     4                  <      g    g.    8           7     4                  <      g0   g>    8           7     4                  <      g@   gN    8           7     4                  <      gP   g^    8           7     4                  <      g`   gn    8           7     4                  <      gp   g~    8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h.    8         ( 7     4                  <      h0   h>    8         0 7     4                  <      h@   hN    8         8 7     4                  <      hP   h^    8         @ 7     4                  <      h`   hn    8         H 7     4                  <      hp   h~    8         P 7     4                  <      h    h     8         X 7     4                  <      h    h     8         ` 7     4                  <      h    h     8         h 7     4                  <      h    h     8         p 7     4                  <      h    h     8         x 7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      h    h     8           7     4                  <      i    i     8           7     4                  <      i    i     8           7     4                  <      i    its actives a green leaf grade as well as indicating which are Ecocert approved, which are preservative-free and which paraben-free. </p><p>Croda has also gone down the green route, launching Up Close and Green, a new green guide to its speciality raw materials. The guide enables formulators to determine how green a product is, with reference to origin (plant, animal or mineral), petrochemicals, silicones, preservatives and biodegradability amongst others. The guide also features a Green Criteria that marks a deliberate move away from the current certification standards available. Under the criteria all products in the guide are free of ethylene oxide and propylene oxide-based components, contain no petroleum distillates, no phthalates, no parabens, no formaldehyde-releasing preservatives and have not been tested on animals.</p><p>   There are so many discrepancies between each certifier that we have left the option of which standard to follow to our customers,    explained Sarah Millns, marketing communications coordinator, personal & health care, Croda.    We are also waiting for the European certification standard to launch, which may change some criteria.   </p><p>Following this sentiment, the company has developed two new sun care products, Solaveil CT-300 and Solaviel CZ-300, and two hydrating peptides from organic sources. Hydroavena HpO and Hydroexcelsa HpO are moisturising agents derived by gentle enzymatic hydrolysis of certified organic crops.</p><p>Symrise has broadened its organic portfolio, adding new products to its Extrapone Organic range, which is based on controlled harvesting. New products include Neo Actipone Soap Nutshell, a 100% natural surfactant suitable for use in personal care applications such as shampoos and body washes.</p><p>   Botanicals are proven in screening methods to have relevant effects such as anti-irritant and antioxidant for cosmetic applications,    Michael Schuricht, regional business manager, Symrise, told SPC.</p><p>The company has also renamed its cosmetics business unit, which will now be known as Life Essentials, but is still a part of Symrise   s Scent & Care division.</p><p>Silab has also entered the organic arena, launching a new Ecocert certified organic range, which will initially comprise three active products - Osilift Bio, Structurine Bio and Vitanol Bio.  </p><p>And Lipo has launched a new line of natural emollients, derived from 100% natural plant sources. The Lipobutter range comprises 11 varieties, eight of which are validated by Ecocert, while the refined organic shea variant is certified organic by Ecocert. Varieties include apricot, refined cocoa, olive, jojoba, refined mango and peach and application suggestions include skin, sun and hair care products, fine soaps and body butters.</p></p><p>Zenitech   s new Meadowfoam and Orange butters also give a nod to natural, with Ecocert validation. The products are said to be suitable for a variety of applications including skin care, hair care, colour cosmetics and nail care. </p><p>   There is a lot of nonsense going on with natural and organics at the moment,    said Carter La Vay, president, Zenitech.    The industry needs to change - it   s time we woke up and realised the world is changing. I am putting Ecocert on everything I can because I believe in it so strongly - it   s the way forward.   </p><p>The once familiar name of Finetex has now been fully absorbed into Innospec. The familiar Finsolv emollients are still available, although production was recently expanded from the US to Europe (Ellesmere Port, UK), but at this year   s in-cosmetics the company was promoting Natrlquest E30 in particular, a readily biodegradable chelating agent that responds to current requirements.    People are really starting to pay attention to green and green ingredients,    said Phil Matena, Innospec vp and general manager.    We   re reinventing ourselves as a speciality chemicals company and we   ve got a great new product line. Our strategy is growth - organic and through acquisition, where it fits our strategy.   </p><p>Preservatives were another area where the green theme produced some interesting new products. Dr Straetmans introduced a new Ecocert-listed antimicrobial ingredient that is claimed to provide a natural alternative to the conventional preservatives that have been given a hard time by some parts of the media recently.</p><p>Dermasoft 688 Eco is a plant-based fungicidal ingredient, derived from basil and is said to possess superior antimicrobial characteristics than other plant derived alternatives currently available.   There has definitely been more demand for green products this year and our new product has been met with very good response,    said Dr. Straetmans    Susanne J  nichen.    We have Ecocert listing and are awaiting Soil Association certification.    </p><p>With ever greater segmentation in the skin care sector, the competition to develop ingredients that offer advanced skin care benefits is at an all time high. Being a    green    brand is one thing but the ingredients have to deliver sophisticated results.</p><p>Gattefoss   unveiled its latest launch, Cytobiol Lumin-Eye, an active ingredient with strong vasculo-protective properties that is claimed to reduce dark circles and puffy skin around the eye area. The active contains ash bark extract, organic silicon and vitamin B3, which act on the skin   s cutaneous microcirculation. Visible results are claimed after 28 days and suggested applications include eye contour treatments, pre- and post-surgery treatments, anti-ageing care and flash radiance treatments.</p><p>Mibelle meanwhile launched two new anti-ageing skin care ingredients based on plant science. PhytoCellTec Malus Domestica is an active based on apple stem cells that uses patent pending plant cell culture technology and is said to protect skin stem cells against ageing as well as delaying the senescence of hair follicles, helping to preserve the vitality and youthfulness of the skin.</p><p>Also making its debut from Mibelle was AstraForce, an anti-ageing product developed for blemished skin. Demand for anti-blemish products for more mature, non-teenage skin is growing rapidly but according to Mibelle, there are very few products available to treat this condition. The ingredient contains Astragalus membranaceus, a plant used in Traditional Chinese Medicine, and is claimed to firm and smooth skin, reduce imperfections, balance sebum production, prevent breakouts and leave the skin   s complexion clear and refined.</p><p>Dow Amerchol presented a new, patent-pending encapsulation and delivery system, SatinFX, which enables both hydrophobic and hydrophilic actives to be encapsulated in a variety of skin care products. It is said to be very easy to mix by simple shear to create encapsulation and to significantly improve the stabilisation of sensitive actives as well as greater efficacy over time. Vitamins A and C and DHA were studied and improved stability was achieved.    It certainly enables the delivery of natural actives so can be used in support of natural claims,    commented Jennifer Sigsworth, business communications specialist with Dow Amerchol.    And with the ongoing demand for multifunctionality, potentially incompatible ingredients like DHA and amino acids for sunless tanning and anti-ageing can be encapsulated together.    By encapsulating potentially irritating actives, the potential for irritation is reduced. SatinFX is also said to improve the aesthetic properties of face creams, eye gel, serum and body lotion formulations. </p><p>Lighter and brighter</p><p>Rahn focused on skin lightening launching CellActive White, a new ingredient developed for gentle skin lightening, and containing a combination of vitamin B3, sulphurous extract of watercress, bio-available zinc and an Essential Cell Boost Factor. In vitro tests on 3D skin models showed up to 50% reduction in melanin production and an 11% skin lightening of Asian skin.    The target was to develop an active for whitening that was safe to skin,    explained Daniela Guildmann, head of marketing, Rahn.</p><p>Lipotec launched Chromabright, a new brightening active that is claimed to induce a significant lightening efficacy on the skin and helps to unify skin tone. Chromobright does not show any cytotoxic effects, or any irritation or sensitisation reaction according to the company.</p><p>Elemental protection</p><p>   Elements of beauty    was the new slogan for Ciba at the show.    It describes different elements of technology under one umbrella - we   re taking a more holistic approach and combining concepts of beauty, well-being and health,    said Michael Wilkop, business head UV protection & active business line home & personal care, Ciba. The company was promoting    better ageing    as a more positive way of looking at ageing, ie healthier ageing through an anti-ageing approach as unfortunately age reversal is not possible. The idea is that this can be achieved through use of Ciba   s Tinosorb UV filters, Tinoderm moisturisers and Tinoderm encapsulated actives; Ciba said it expects Tinosorb S and Tinosorb M to gain acceptance in the US this year so plans to be ready for the materials to be included in finished products next year.    We want to extend the scope of our activities - it   s not only a beauty topic, it   s a health issue.    Uli Osterwalder, global marketing manager UV protection and active effects added:    Ciba was an early player in UVA so we   re a market leader. We now want to work with customers to convey the message to the ultimate consumer.    The company also wants to work with dermatologists to improve the understanding of sun protection there.    They don   t all understand SPF and it   s very important that they do,    said Osterwalder.    It   s important to work on the image of sunscreens but we   re counting on the fact that people will always want to expose themselves to sun. And vitamin D deficiency is now being seen as being responsible for a lot of cancers, while vitamin D requires UVB. But protection comes first.    </p><p>Next month SPC will report on many more launches and events from the show, including this year   s inspirational in-focus feature, Utopia, and the ever popular trends presentations. </p>
Mar 20 14:46:44 localhost mysqld: w)   k  ;
Mar 20 14:46:44 localhost mysqld: InnoDB: End of page dump
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: Uncompressed page, stored checksum in field1 0, calculated checksums for field1: crc32 1274019770, innodb 28570114,  page type 39311 == PAGE TYPE CORRUPTED.none 3735928559, stored checksum in field2 1999181308, calculated checksums for field2: crc32 1274019770, innodb 3035797051, none 3735928559,  page LSN 41625 2406031360, low 4 bytes of LSN at page end 3832253215, page number (if stored to page already) 2147483648, space id (if created with >= MySQL-4.1.1 and stored already) 256128
Mar 20 14:46:44 localhost mysqld: 2020-03-20 14:46:44 81 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

}}}


I tried to use Windows 7 with the same version of VirtualBox - no problems at all.



",vagiz
14647,Ram Drive as another drive type,,2015-09-30T12:45:29Z,2015-09-30T12:45:29Z,2015-09-30T12:45:29Z,"Sometimes fast save times to disk are desired. I ran a secondary disk in a guest where the vdi was actually in a ram drive on the host. The access times were very fast.

Since Virtualbox already has the ability to set aside host ram for the guest, a possibly useful service could be to set aside additional ram as a ram drive, disguising the extra ram as another vdi for the guest to see on the IDE or SATA ports. No ram drive software on the host would be necessary. 

When the disk controller is clicked in the GUI settings, another icon could be placed next to Add CD and Add Disk, Add RAM Disk, maybe a little IC chip icon. A slider in the GUI could allow adjustment of how much ram to set aside. During the guest-shutdown process Virtualbox could store the ram drive vdi's contents to a file in the guest's folder, and restore the file's contents back to the ram drive during guest boot. ",scottgus1bug
18991,QCOW2: Compressed images,VirtualBox 6.0.12,2019-10-08T15:19:28Z,2019-10-09T07:19:27Z,2019-10-09T07:19:27Z,"Adding a compressed QCOW2 image as a hard disk to VirtualBox will work, but actually reading from the disk will fail silently.

== Expected behavior ==
If the QCOW2 image is using an unsupported feature, my expectation would have been that I get a corresponding information.

How to reproduce:
* Download any QCOW2 image from http://download.opensuse.org/tumbleweed/appliances/ (all of them seem to be using compression)
* Use this image as a boot disk for a virtual machine
 * ""FATAL: No bootable medium found! System halted.""
* When using / viewing the image as a secondary disk it will show up as an empty disk filled with zeros.
 * Writing to the disk (e.g. using `cfdisk`) will correctly prompt

   
{{{
The I/O cache encountered an error while updating data in medium ""ahci-0-2"" (rc=VERR_NOT_SUPPORTED). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
}}}
",laenion
18865,Prompt to assign another UUID when already exists.,VirtualBox 6.0.10,2019-08-24T22:37:50Z,2019-08-28T10:08:39Z,2019-08-28T10:08:39Z,"This happens when I move and rename 'D:\test\mydisk.vdi' to 'D:\ubuntu64.vdi', it doesn't detect that it's not present anymore in the old location and thinks it's duplicated.

{{{
Failed to open the disk image file D:\ubuntu64.vdi.

Cannot register the hard disk 'D:\ubuntu64.vdi' {e2855e0e-fd02-40b0-ac5e-0d8bd297f1db} because a hard disk 'D:\test\mydisk.vdi' with UUID {e2855e0e-fd02-40b0-ac5e-0d8bd297f1db} already exists.

Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBoxWrap
Interface: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
}}}

I would like to have a more friendly option to either re-check if the file exists in the previous location or alternatively change the UUID of the new file. The error message which is displayed looks pretty catastrophic like some sort of kernel panic or unrecoverable error with data loss.

Currently I have to run the following command manually to fix it.

{{{
VBoxManage.exe internalcommands sethduuid 'D:\ubuntu64.vdi'
}}}
",DeGarden
19541,Poor disk write performance for fully allocated sparse-extent VMDKs,VirtualBox 6.1.6,2020-04-28T22:48:04Z,2020-04-28T22:52:20Z,2020-04-28T22:52:20Z,"Using sparse VMDK disk images, VirtualBox's disk write performance drops dramatically if the ""sparse"" image is fully allocated. This was surprising and unintuitive since we figure that using a sparse image is meant to be a tradeoff where we sacrifice performance in exchange for a smaller file size. 

I've attached two 4GiB VMDKs. Both are completely empty and both are technically sparse-extent VMDKs, but one is 100% pre-allocated and the other is 100% unallocated. If you attach these VMDKs as second and third disks to an Ubuntu VM running on VirtualBox and measure their write performance (using dd to write to /dev/sdb and /dev/sdc, for example) the difference in write speeds is clear.",vorteil-alan
6307,Partitions larger than 2T are not supported with Raw disks,VirtualBox 3.1.4,2010-03-01T23:48:48Z,2010-03-18T18:31:54Z,2010-03-18T18:31:54Z,"Trying to create a raw partition for an 8TB Array on the host machine.  The partition IS created but will not mount on the guest.  The code for the creation of the raw disk looks correct, but the problem is the partition table in my opinion.

On the host, '''file -t''' sees this raw disk as a ext3 file system.  On the guest, the same command sees the raw disk as '''data'''.

My proof to this is that listpartitions command only sees 2TB.
{{{
VBoxManage internalcommands listpartitions -rawdisk /dev/sdc

Sun VirtualBox Command Line Management Interface Version 3.1.4
(C) 2005-2010 Sun Microsystems, Inc.
All rights reserved.

Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0xee  0   /0  /1   1023/254/63       2097151            1
}}}

parted -l shows:
{{{
Model: TRUSTED Mass Storage (scsi)
Disk /dev/sdc: 8796GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  8796GB  8796GB  ext3
}}}

My guess, having just scanned the code is that the problem lies within /src/VBox/Frontends/VBoxManage/VBoxInternalManage.cpp

In the '''partRead''', starting at line 646, it looks we are using u32 instead of u64.

That may be just part of the problem as 8T needs a GPT partition table and I am not sure that VB will read that correctly.  I would need to do more research to find that out myself and learn the VB code.

Because the bug exists on the host in reading the partition table in the first place, I am unsure of the VBox.log file needed.  I have attached a file with the host trying to connect using a 

The drive itself is a Drobo connecting via USB.

The reason this is a MAJOR priority is that this disk is a USB drive and ticket 4261 would also solve my problem.  But seeing as that is listed as minor and 8 months old, and VB will only give ~600kB/s bandwidth to USB devices, this becomes a MAJOR priority to guests working with large files.  Either solution would work.

As it stands right now, VBox is NOT able to deal with large files or large systems.",Tony Plack
17061,NVMe w/o extension pack has too generic of error message,VirtualBox 5.1.26,2017-09-07T18:12:07Z,2017-09-07T18:12:07Z,2017-09-07T18:12:07Z,"Steps to reproduce:
- Create new Debian 64 VM using defaults for all choices
- Add NVMe controller
- Run VM and note that error message correctly indicates that extpack required but does not mention NVMe even though it does mention USB and RDP.",LNS
11570,NPIV Support Request,VirtualBox 4.2.8,2013-03-06T23:28:50Z,2013-03-06T23:29:36Z,2013-03-06T23:29:36Z,"Adding NPIV support would greatly enhance testing capbilities for VirtualBox for Scenarios like running Oracle VM Server, Microsoft Hyper-V or VmWare ESXi inside VirtualBox on hosts with SAN Storage (Closed LAB). Also alot of multipath developement tests could be run this way.",efstathiou_e
16775,Multiple snapshots cause inconsistent parent UUID in vdi causing VER_FILE_NOT_FOUND error,VirtualBox 5.1.22,2017-05-21T16:05:59Z,2017-05-21T16:05:59Z,2017-05-21T16:05:59Z,"'''Problem:'''  Snapshotting and deleting of old snapshots in a running VM results in the retention of a reference to a deleted snapshot, inhibiting the resume of saved state.

Setup and process of snapshotting and snapshot removal:

I have a situation where I need to run a long set of analytics in a guest VM.  I constructed a single base VM that installed all the software and base set of data.  I then created 4 linked clones of that base VM.  In each clone, I then configure the specific parameters of an algorithm.  The execution of each set of analysis is approximately 1 month.

To protect myself from unexpected problems that require a complete restart of the analysis, I began to use snapshots twice a day to capture the current state so if the VM crashed for any reason (e.g. power outage or the host becoming frozen), I have a state that I can revert to and resume, losing at most 12 hours of analysis.

After a couple of days, I decided to clean up a few of the older snapshots (using the UI to remove old snapshots in the order of oldest to newest until I had only one snapshot left and the current state for each clone).

I performed the snapshot operation one each of the running clones and I conducted the snapshot removal against the running clones.  In other words, as the VM was running, I began with the oldest snapshot and used the GUI to do the removal (merge and delete).  All worked well.  The VM continued to run and I was able to take another snapshot and then remove the older snapshot.  However, when I decided to do maintenance to the host, the problem emerged.  

I saved the state of each running clone, conducted my host maintenance (basic patching and rebooted the host).  When I went to restart the 4 clones, each reports that there is a missing snapshot.  The snapshot is the immediate parent which is the snapshot just prior to the current snapshot.  Error message below.


{{{
Error:
Could not open the medium '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{fe2f4eca-c178-4a2d-9092-8c82d6bab0b0}.vdi' (VERR_FILE_NOT_FOUND).


Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
MediumWrap
Interface: 
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

}}}

The missing snapshot that it cannot find I believe to be the most recently removed snapshot from the running VM prior to saving the state.

I've attached 2 views from the Virtual Media Manager.  View 1 shows the child of Clone1 which represents the current state (I believe).  It also shows its parent ""missing"".  View 2 is the same but I highlighted the ""missing"" snapshot.

The third attachment is from the VBox Manager showing the snapshots for Clone1.

Doing a showmediuminfo command against the lowest level snapshot (current state), it shows that the Parent UUID as the missing snapshot (which was deleted via the GUI after it merged it with the base).
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage showmediuminfo f1a42411-6f9a-44ae-be07-00ae7de93f89
UUID:           f1a42411-6f9a-44ae-be07-00ae7de93f89
Parent UUID:    fe2f4eca-c178-4a2d-9092-8c82d6bab0b0
State:          created
Type:           normal (differencing)
Auto-Reset:     off
Location:       /home/jpb/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots/{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
Storage format: VDI
Format variant: differencing default
Capacity:       81920 MBytes
Size on disk:   678 MBytes
Encryption:     disabled
In use by VMs:  OT-Strat-Dev Clone1 (UUID: 640b91f3-4748-480a-8d8e-51c576201b5e)
}}}


However, when I use the dumphdinfo, I get a different value for the uuidParent - which is actually the higher (and correct) UUID of the surviving and recent snapshot.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ vboxmanage internalcommands dumphdinfo {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi
--- Dumping VD Disk, Images=1
Dumping VD image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" (Backend=VDI)
Dumping VDI image ""{f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi"" mode=r/o uOpenFlags=9 File=0x00563f4bf61680
Header: Version=00010001 Type=4 Flags=0 Size=85899345920
Header: cbBlock=1048576 cbBlockExtra=0 cBlocks=81920 cBlocksAllocated=676
Header: offBlocks=1048576 offData=2097152
Header: Geometry: C/H/S=1024/255/63 cbSector=512
Header: uuidCreation={f1a42411-6f9a-44ae-be07-00ae7de93f89}
Header: uuidModification={eff43f9a-8441-4e7b-9956-17fad78601a5}
Header: uuidParent={3f80396b-40b9-4c17-aa02-8013bf5a3ea6}
Header: uuidParentModification={44e04488-2274-4b00-92ac-1d0c0a02d180}
Image:  fFlags=00020000 offStartBlocks=1048576 offStartData=2097152
Image:  uBlockMask=000FFFFF cbTotalBlockData=1048576 uShiftOffset2Index=20 offStartBlockData=0

}}}

I haven't found the way to change the uuid that shows up in showmediuminfo to match the uuidParent of the dumphdinfo.  I believe this would resolve my problem and allow me to restore the saved state of my clones.

My snapshot directory also interestingly has multiple saved state files which I assume happens as part of the snapshotting of a running VM since the date and time stamp corresponds to the snapshotting events.  So, these do not look to be cleaned up by the snapshot process.
{{{
jpb@explorer:~/VirtualBox VMs/OT-Strat-Dev Clone1/Snapshots$ ls -l
total 11186860
-rw------- 1 jpb jpb  905360735 May 10 16:03 2017-05-10T21-03-44-944351000Z.sav
-rw------- 1 jpb jpb  872413499 May 20 07:54 2017-05-20T12-53-55-899688000Z.sav
-rw------- 1 jpb jpb  970377870 May 20 17:29 2017-05-20T22-28-49-589899000Z.sav
-rw-r--r-- 1 jpb jpb 7647264768 May 20 07:55 {3f80396b-40b9-4c17-aa02-8013bf5a3ea6}.vdi
-rw------- 1 jpb jpb  352321536 May 17 09:55 {7b0b9120-8a8d-46a1-a82b-fec4448e9b9f}.vdi
-rw------- 1 jpb jpb  710934528 May 20 17:28 {f1a42411-6f9a-44ae-be07-00ae7de93f89}.vdi

}}}




My current option is to revert to the snapshot, discarding the current state and reprocess the work from the last 12 hours.  I'll save clone1 as is incase you need more information.






",jbrown10
9103,modifyvm --resize doesn't work with snapshots,VirtualBox 4.0.8,2011-06-24T10:27:29Z,2017-09-13T14:31:41Z,2017-09-13T14:31:41Z,"I have a 20GB dynamic .vdi which I want to resize to 40GB so I issue:

VBoxManage modifyhd /full/path/to/hd.vdi --resize 40960

and it responds (instantly) with:

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Running VBoxManage showhdinfo on the image tells me:

...
Logical size:         40960 MBytes
Current size on disk: 18464 MBytes
Type:                 normal (base)
Storage format:       VDI
Format variant:       dynamic default
...

and also reports the same logical size for the snapshot files.

The problem is that gparted reports that the drive is still 20G (not the partition; the whole drive).

Windows disk management also sees the drive as 20G.

It looks like while VirtualBox can see the new logical size, it's not reporting it to the guest correctly.",jonsiddle
13046,modifyhd --resize should not be permitted when snapshots exist,VirtualBox 4.3.10,2014-05-18T22:02:19Z,2017-09-13T12:19:16Z,2017-09-13T12:19:16Z,"Currently, a VM with snapshots can be ""resized"" via `VBoxManage modifyhd --resize`. However, this puts the user between a rock and a hard place. The VM settings show the new size, but the guest OS does not. The VM cannot be reduced to its former size (`VBOX_E_NOT_SUPPORTED`). The snapshots cannot be deleted. Basically, the program claims the snapshot is being deleted, then when that dialog disappears, all VMs say ""Information Unavailable"" and the Settings windows are blank. When !VirtualBox Manager is restarted, all the VMs are fine again, but the snapshot still exists.

The issue is irreversible. The only solution I've found thus far ([http://www.codereactor.net/changing-size-of-virtualbox-disks-before-and-after-deleting-snapshots/ here]) is to clone the VM without also cloning the snapshots, assign a new UUID to this disk (another issue), and proceed from there. 

This issue has existed for many years, yet remains completely undocumented. Furthermore, because it is not mentioned in the User Guide or the numerous blog posts outlining how to expand a VM, the only way the user will discover it is when they search for information //after// they've done an irreversible procedure. 

This is essentially a duplicate of ticket:9103. However, I felt the need to open a new ticket because that ticket and its specified version are over 3 years old, no support activity has occurred in over 3 years (though 1 user commented on it recently), and the issue has yet to be addressed. At the very least, this caveat should be documented under section 8.23 of the User Manual.",skittleys
17923,miracast on Windows 10 guest system not working,VirtualBox 5.2.16,2018-08-10T13:37:52Z,2018-08-11T05:41:59Z,2018-08-11T05:41:59Z,"trying to use miracast on windows 10 (virtual) system of virtualbox not working?
could you please tell me if it's possible to make it work or is it a limitation.
thanks",babouchka
14769,Merging snapshots takes ages,VirtualBox 5.0.8,2015-10-31T10:59:17Z,2015-11-02T22:30:28Z,2015-11-02T22:30:28Z,"I took three snapshots of a VM (with a few seconds between them), shutd own the vm and I'm trying to merge the first one for three hours now.

Progress bar is stuck at ""36 seconds"" left, I dont see any activity (no changing timestamps, no changing file sizes, nothing).

I guess something's pretty wrong here :)

Can you please tell me on how to investigate this issue further?",Eduard Warkentin
14770,merging of snapshots destroys VM,VirtualBox 5.0.0,2015-10-31T19:54:17Z,2016-02-17T23:24:32Z,2016-02-17T23:24:32Z,"Whenever I try to merge a snapshot, regardless of wether I get error messages about OBJECT NOT FOUND or wether the merge is successful, I am unable to (re)start the VM, since a snapshot file is missing.

Trying to restart Virtualbox GUI ends up in a warning that there are missing disk files, the missing snapshot.

This happens on Linux hosts, OSX hosts, with Virtualbox 5.0.0 to 5.0.8.

For me, its totally breaking virtualbox, and I am forced to downgrade to 4.3.32.

Please just add a comment in case you need more information.",Eduard Warkentin
11857,"medium type ""dvddrive"" cannot be used via a readonly iscsi target",VirtualBox 4.2.12,2013-06-12T14:11:49Z,2020-01-21T21:23:06Z,2020-01-21T21:23:06Z,"ISO mediums exposed in a {{{dvddrive}}} cannot be used over iSCSI when the target is readonly.

According to [http://www.virtualbox.org/manual/ch05.html#hdimagewrites documentation], CD/DVD images are created read-only, but this doesn't seem to be the case, at least with iSCSI.  I need access to a series of readonly iscsi targets that are exposing ISOs, but this does not seem possible unless I start snapshotting guests after the medium is added, and before it is turned on.


A sample target I am trying to connect to
{{{
ryan@TehDualLinux:~$ sudo tgtadm --lld iscsi --mode target --op show
Target 2: iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: IET     00020000
            SCSI SN: beaf20
            Size: 0 MB, Block size: 1
            Online: Yes
            Removable media: No
            Readonly: No
            Backing store type: null
            Backing store path: None
            Backing store flags: 
        LUN: 1
            Type: disk
            SCSI ID: IET     00020001
            SCSI SN: beaf21
            Size: 1013 MB, Block size: 512
            Online: Yes
            Removable media: No
            Readonly: Yes
            Backing store type: rdwr
            Backing store path: /usr/local/storage/linuxmint-14.1-mate-dvd32bit.iso
            Backing store flags: 
    Account information:
    ACL information:
        ALL

}}}



Adding the above target to VirtualBox
{{{
VBoxManage storageattach ""NewPasswordWindowsReadOnly2"" --storagectl ""MyController"" --port 1 --device 0 --type dvddrive --medium iscsi --server localhost --target ""iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b"" --lun 1 --tport 3260
}}}



It was added successfully.
{{{
vboxmanage list hdds

...
UUID:        2d4790e0-678b-4fc0-b529-32aebfec6f97
Parent UUID: base
Format:      iSCSI
Location:    localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1
State:       created
Type:        normal
Usage:       NewPasswordWindowsReadOnly2 (UUID: e86ffe75-2412-4aa6-9b36-3a0c0f3e4780)
...

}}}


After we try and turn the machine on, it fails with:
{{{
Failed to open a session for the virtual machine NewPasswordWindowsReadOnly2.
VD: error VERR_VD_IMAGE_READ_ONLY opening image file 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' (VERR_VD_IMAGE_READ_ONLY).
Failed to open image 'localhost|iqn.2001-04.com.TehDualLinux-2260f94a-90f3-4147-9e32-39c773f7095b|1' in read-write mode rc=VERR_VD_IMAGE_READ_ONLY (VERR_VD_IMAGE_READ_ONLY).
Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY).
AHCI: Failed to attach drive to Port1 (VERR_VD_IMAGE_READ_ONLY).
}}}

Steps to replicate:

1.  Make an iSCSI target with any iSCSI software and make it readonly
2.  Add the target to your guest via vboxmanage stoargeattach and do not take snapshots
3.  Turn on the guest.

Summary:

- If you remove the readonly flag on the iscsi target everything works perfectly (even through VirutalBox does not need write on this medium)
- If you take a snapshot (thus a differencing medium is created), everything works perfectly
- If you add the DVD as multiattach instead of ""normal"", it creates a differencing medium, and everything works perfectly.
- If you add the medium normally, even though VirtualBox's documentation claims it is readonly, it tries to access the medium as read/write.",rshaw
18498,Machine switch to power off,,2019-03-15T16:48:05Z,2019-03-15T16:48:05Z,2019-03-15T16:48:05Z,"My virtual machine have a virtual disk vdi file hosted in the USB external disk.[[BR]]
When this external disk is diconnected, '''no''' dialog box
""read error disk [[BR]]
Abort Retry Ignore""[[BR]]
is showing.[[BR]]

Imagine that there is a false electrical contact of a USB port to the external disk.[[BR]]
This dialog box which is not showed if for avoiding power off and restart virtual machine.[[BR]]

It would require the implementation of a dialog box Read error disk with button [[BR]]
Abort Retry Ignore, and possibility to REOPEN (fopen) the VDI file if the usb disk [[BR]]
is reconnected again.[[BR]][[BR]]
Thank.


",Sizy458
5555,Mac OS X: Time Machine-friendly storage,,2009-11-25T02:26:45Z,2009-11-25T02:26:45Z,2009-11-25T02:26:45Z,"If you use VirtualBox and don't tell Time Machine to ignore your hard disks, you'll soon end up copying the entire image to the Time Machine server or disk every time you run the VM. Storing these hard disks in a sparse bundle would allow the OS to copy only the changes to the VMs' hard disks at update time.",Jeff Kelley
18813,Linux installation fails when machine folder points to non-OS directory | Win 8.1 x64,VirtualBox 6.0.10,2019-08-05T09:20:35Z,2019-08-17T02:55:43Z,2019-08-17T02:55:43Z,"Tried to install Ubuntu 16 x VM by selecting ""Machine Folder"" to a non-os directory. Installation always fails at Use entire disk and setup LVM.

ENV:
- Windows 8.1 x64 8GB RAM/500 GB HDD
- VM Conf: Memory: 1024 MB, create vhd now, VDI [dynamic alloc][10 GB]",cheruvattil
20000,Linux guests lock up with Host I/O cache disabled (NVMe and SATA),VirtualBox 6.1.14,2020-10-26T15:57:22Z,2021-02-23T21:37:44Z,2021-02-23T21:37:44Z,"I have been finding that Linux guests seem to lock up when Host I/O cache is disabled when disks are under load (for example when installing system updates). dmesg also shows disk timeouts, and it seems no further disk operations succeed after this point without killing the VM process and restarting.

A log is attached. I'm not sure how to reproduce this reliably, but it seems to happen when I'm installing updates. I have seen this with both Ubuntu and Fedora guests. I will also upload a screenshot shortly with the exact messages, but I seem to have misplaced it for the moment.

I should also note that this is with the VDI nonrotational option turned on and discard=on in the guest Linux OS.

Anything else I can do to help diagnose?",Hamish McIntyre-Bhatty
20365,Linux guest won't boot unless hard disk is set as the priority,VirtualBox 6.1.22,2021-05-13T19:11:02Z,2021-05-14T10:33:56Z,2021-05-14T10:33:56Z,"After installing the latest CentOS 7.8
The OS refuses to boot unless the boot order for the VM is specifically changed so that the VM boots from the disk first.
If I set the boot order to something else (for example network for IPXE testing),the operating system instead shows an error ""fatal: int18: BOOT FAILURE"".
Most of what I found online talks about installing the disk in GPT vs MBR, but that shouldn't have much bearing since I know I installed the VM as MBR. None the less, I still tried to change the VM to UEFI since that is what the online community instructs.  However, no effect was detected besides the VM booting into the UEFI shell. However, if the boot order for the VM is changed, even though the other boot options are not being used and the option for disk is eventually reached, the boot option for the disk will eventually show the error.

",Rusty_Almighty
13834,linked clone - uuid already exists,VirtualBox 4.3.22,2015-02-14T09:48:11Z,2015-02-14T09:48:11Z,2015-02-14T09:48:11Z,"goodmorning, I have this problem, and I think that all versions from 4.3 are affected, because the problem doesn't .
I created 1 virtualmachine, started, SO installed, closed, everything fine.
I want a (one or more) clone of this machine, type linked-clone, so I use the procedure to create a linked-clone.
If I remove 1 of the 2 machine (remove only) and than I re-add there is the error about ""uuid already exists"" and I can't re-add the machine.
I think the problem is that each machine load all the structure of snapshots for both the machine, so if I re-add the one removed, it sais that already exists.
I have this problem with host Linux and Windows",sigfrido.barb
21343,Keeps losing linked disk,VirtualBox-7.0.4,2022-12-16T11:16:33Z,2022-12-16T11:16:33Z,2022-12-16T11:16:33Z,"I had cause to delete a linked clone (not the files ..) to investigate something. Now, having re-added the clone (successfully ..), I'm having to keep adding the clone's disk snapshot to the list of hard disks (it appears under the parent as expected).

A restart of the application retains the added disk and the VM boots, but it seems that whenever I restart the host (I normally just sleep/resume), the snapshotted disk disappears from the list of registered disks and has to be added by hand again. The 'add' doesn't seem to be retained through a host restart - or at least I've only so far seen the phenomenon after restarts. Will add to the report if I see it on other occasions.",Granta
17506,It should be possible to boot a guest with an unconnected hotplug disk,VirtualBox 5.2.4,2018-01-27T15:18:51Z,2018-01-28T01:57:16Z,2018-01-28T01:57:16Z,"If there is a hotplug virtual disk (a VDI file on an external drive) attached to a SATA controller, the virtual disk is unplugged in the running guest, the external drive is removed and the guest is shutdown, then the guest cannot be booted anymore. I got the following message:
{{{
Could not open the medium 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi'.
VD: error VERR_PATH_NOT_FOUND opening image file 'E:\VirtualBoxDisks\Lubuntu-16.04-Backup.vdi' (VERR_PATH_NOT_FOUND).

Fehlercode:
E_FAIL (0x80004005)
Komponente:
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
}}}

Steps to reproduce the problem:

1. Assume you have a Windows 7 host (other host may have the same problem), an USB drive (an USB stick may have the same problem) and a Linux guest (other guests may have the same problem).
2. Shut down the guest.
3. Connect the USB drive to the host.
4. Add a new virtual disk to the guest as a VDI file on the USB drive with a virtual SATA controller. Mark the virtual disk as hotpluggable.
5. Start the guest.
6. Check that the hotplug disk is there: {{{ls /dev/sdb1}}}
7. Unplug the disk: {{{echo 1 > /sys/block/sdb/device/delete}}}
8. Check that the hotplug disk is unplugged (output should be an error message): {{{ls /dev/sdb1}}}
9. Disconnect the USB drive from the host.
10. Shut down the guest.
11. Start the guest.

For a simple test you can omit the steps 5 to 8 and 10.

From my point of view a hotplug disk should be handed like a DVD: It is not necessary that it there (is in the drive) to boot the guest.

Workaround: Disconnect the hotplug disk by hand from the SATA controller before booting, in cold state between step 10 and 11 (in the GUI or by the command {{{VBoxManage storagectl}}}).
 ",dlippold
20081,Installing Linux subsystem on windows 10 caused read/write error inside running linux mint (in virtual box),VirtualBox 6.1.16,2020-12-05T10:00:50Z,2021-01-24T12:07:45Z,2021-01-24T12:07:45Z,"I'm not used to write these, but if this is a real but, it's a serious one.

I don't have any log files, because during the search for a solution, things have been purged and reinstall many times.

but I'll try to describe as good as I can.

 Basically, I installed Linux subsystem on my windows 10 2004 machine.

Then I upgraded the wsl1 to wsl2 on windows.

Now after the night, I had some scripts running on my linux, scanning and identifying images /copying/sorting.

on the morning it had crashed, and in the terminal running the script it said something about ""segmentation fault core dumped""

I didn't realize it was so serious so I only restarted it. 

I got a few screenshots from a boot, don't remember what I booted, if it was a rescue disc or linux mint installation disc, but it shows some error info.

I uninstalled linux subsystem and Ubuntu 20 that I had installed on Windows, and tried to install linux mint on a new  virtual box, but after a while updates started to fail, and installation of software resulted in read/write error.

after a while I remembered that I didn't uninstall the wsl2 update from windows.

I uninstalled it, tried to reinstall linux mint, an now everything worked fine, no issues,  no errors, everything worked as it should.

so apparently did the wsl2 update interfere with how virtual box was accessing the .vdi files?

well, that's basically what happened.. sorry I can't give any logs, but this issue might be worth investigating..",Nemesis 77
16847,Incomplete DMG support,VirtualBox 5.1.22,2017-06-19T08:56:04Z,2017-06-19T08:56:04Z,2017-06-19T08:56:04Z,"Some DMG cannot be mounted in a VM with a ""`VERR_VD_DMG_INVALID_HEADER`"" error. Example [https://dl.bintray.com/xquartz/downloads/XQuartz-2.7.11.dmg XQuartz-2.7.11.dmg], but there are actually the majority. The validity of each of the DMGs has been verified. Full error message:

> ''Could not open the medium '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""'''. [[br]] [[br]]
> VD: error VERR_VD_DMG_INVALID_HEADER opening image file '''""/Users/Shared/_Downloads/_System/XQuartz-2.7.11.dmg""''' (VERR_VD_DMG_INVALID_HEADER)''

[[br]]
Other examples include:
* Any DMG created from the Disk Utility will not mount. I believe I've tried all possible combinations, but they all fail with the above error message.
* [http://adcdownload.apple.com/Developer_Tools/Xcode_7.3.1/Xcode_7.3.1.dmg Xcode 7.3.1], that's actually the weirdest. The VM (OSX) shows a ""`The disk you inserted was not readable by this computer. Ignore | Eject`"". If you copy the same exactly DMG in the VM, it is mounted and works as expected.
",Socratis
14268,Implementing VMDK relative raw disk partitions on Windows,VirtualBox 5.0.0,2015-07-13T14:15:02Z,2015-10-13T13:39:01Z,2015-10-13T13:39:01Z,"This bug serves to track progress of implementing the -relative option for the '''VBoxManage internalcommands createrawvmdk -filename ... -rawdisk ... -partitions ...''' command on Windows hosts.

See [https://www.virtualbox.org/manual/ch09.html#rawdisk section 9.9.1] of the docs regarding using physical partitions as a Virtual Drive for a VM. The -relative option for the above command was only available on Linux hosts.",regedit
12616,Implement write support for VHDX,VirtualBox 4.3.6,2014-01-16T14:47:51Z,2017-07-17T11:16:26Z,2017-07-17T11:16:26Z,"When trying to create a virtual machine, when selecting hard drive, I've selected a vhdx create by Windows 8 Hyper-V. I get the following errors:

Failed to open the hard disk file C:\SharePointDev.vhdx.

Could not open the medium 'C:\SharePointDev.vhdx'.

VD: error VERR_NOT_SUPPORTED opening image file 'C:\SharePointDev.vhdx' (VERR_NOT_SUPPORTED).

Result Code: E_FAIL (0x80004005)
Component: Medium
Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac}
Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)




",mrwjr2003
9072,implement copy-on-read for disk images,VirtualBox 4.0.8,2011-06-14T11:53:04Z,2011-06-14T11:53:04Z,2011-06-14T11:53:04Z,"There is already support for read-only images with copy-on-write semantics. In some cases, where the disk image resides on a NAS connected over a relatively slow network link (e.g. Samba, NFS), it is desirable to have copy-on-read behaviour too:

Whenever a block from the read-only image is read, it is stored in the differential image (which the user can place on a local partition). The second and following accesses to the same block (e.g. when the VM is rebooted) will then be considerably faster.

This way, fast image access can be provided without explicitly copying the entire image to the local machine.",Marc Schütz
21416,"If you have multiple LVM partitions for example on sda2 on Oracle 9.1 Linux Guest on Windows 10 Host, the cloned or exported VM will not boot properly",VirtualBox-7.0.6,2023-01-18T10:09:55Z,2023-01-18T10:09:55Z,2023-01-18T10:09:55Z,"Hello,

You replicate the problem like this:

1. Install a new VM from the Oracle 9.1 iso. 
2. Define just one disk and ensure it is very large e.g. 2TB. 
3. Ensure the default installation creates at least two LVM partitions:
    e.g. ol-root and ol-home on sda2
4. When cloned or exported/imported even to the same host machine, the resulting cloned VM will not boot properly, because only the first of the partitions is retained. In the example above, only ol-root is visible to the machine. ol-home disappears off the face of the earth.

As you can see the steps to replicate the problem is trivial. 

Thanks for your attention.

Cheers!

Yuet
",Yuet
7791,"If disk images are on a shared storage(eg. samba), clients crashes if there is networking error.",VirtualBox 3.2.12,2010-12-04T16:37:19Z,2010-12-06T15:51:50Z,2010-12-06T15:51:50Z,"I keep all disk images in a samba share, and sometimes, If there is network problem, The guests fail constantly, Even if the share which contains disk images offline and go back within in a second, The guest fails(both windows and linux) still. Asked in #vbox channel, And finally the conclusion might be:

00:13 < lacqui> But honestly, the issue is that VBox is attempting to access a file that it assumes is constantly available
00:13 < lacqui> When there are network issues, that may no longer be the case.
00:13 < lacqui> VBox has the file open constantly.
00:13 < lacqui> I beleive that file pointers may be lost (on the OS level); I don't know if there is an application-level method of bypassing that
00:14 < xinming> Since the samba share returns again really soon, So I believe there may be a work around to detect this, and re-open the file.

Possible to fix this?
Or if this won't be fixed, Is there a way to prevent this situation please?

Thanks!
",yiyihu
21440,I/O errors with virtio-scsi,VirtualBox-7.0.6,2023-01-28T00:22:38Z,2023-02-09T18:44:17Z,2023-02-09T18:44:17Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
21439,I/O errors with virtio-scsi,VirtualBox-7.0.6,2023-01-28T00:22:36Z,2023-01-28T00:22:36Z,2023-01-28T00:22:36Z,"I have just created a new guest, and to improve performance, I have chosen the virtio-scsi for the storage controller.

The host I/O cache is disabled.

Under medium IO load, I started to get I/O errors on the console of the guest within 15 minutes.

I'm attaching the log (which doesn't show any errors as far as I can tell), and a screenshot which shows the guest console.

I am aware that some related bugs were allegedly fixed for 7.0.4, but I'm on 7.0.6, and still see it. 
",csillag
19666,I tried to install Latest Kali linux on Latest Virtual Box. i am not able to get installed on to my Windows laptop,VirtualBox 6.1.10,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,2020-06-15T00:34:03Z,,Universal007
10031,High I/O causing filesystem corruption,VirtualBox 4.1.4,2011-12-15T18:30:45Z,2021-04-22T15:10:32Z,2021-04-22T15:10:32Z,"Hello,
We are running an Ubuntu 10.04 32bit guest on a RHEL 64 bit host. The guest storage control is SATA AHCI with host I/O caching enabled. 
Host info:
OS Type:	Linux (2.6.18-194.el5)
VirtualBox:	4.1.4 (74291)
Processors:	Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2)
HWVirtEx, PAE, Long Mode (64-bit)

It seems during times of high I/O, like backups and etc, the guest filesystem resets to read-only. We have this issue with both ext3 and ext4 filesystems. Switching to ext3 seemed to lessen the occurrences though.

Here is a snip of syslog around the time of the corruption..


{{{
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12
Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12
Dec 15 08:02:29 vault kernel: [ 2338.011698] ata4.00: exception Emask 0x0 SAct 0xffff SErr 0x0 action 0x6 frozen
Dec 15 08:02:29 vault kernel: [ 2338.011714] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011721] ata4.00: cmd 61/00:00:b7:5c:9d/04:00:09:00:00/40 tag 0 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011723]          res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011726] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011729] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011736] ata4.00: cmd 61/00:08:77:31:9d/04:00:09:00:00/40 tag 1 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011737]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 15 08:02:29 vault kernel: [ 2338.011740] ata4.00: status: { DRDY }
Dec 15 08:02:29 vault kernel: [ 2338.011743] ata4.00: failed command: WRITE FPDMA QUEUED
Dec 15 08:02:29 vault kernel: [ 2338.011749] ata4.00: cmd 61/00:10:77:35:9d/04:00:09:00:00/40 tag 2 ncq 524288 out
Dec 15 08:02:29 vault kernel: [ 2338.011751]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
}}}
And then later on in the file....
{{{
Dec 15 08:02:29 vault kernel: [ 2338.011969] ata4: hard resetting link
Dec 15 08:02:29 vault kernel: [ 2338.332268] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 15 08:02:33 vault kernel: [ 2342.108804] ata4.00: configured for UDMA/133
Dec 15 08:02:33 vault kernel: [ 2342.108811] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108815] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108818] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108820] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108823] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108826] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108829] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108831] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108834] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108837] ata4.00: device reported invalid CHS sector 0
Dec 15 08:02:33 vault kernel: [ 2342.108840] ata4.00: device reported invalid CHS sector 0
}}}

At this point the guest needs to be shut down and the drive mounted and fsck, which complains about allot of IO handle stuff.",Indigo42
6979,Hard disk boot order,VirtualBox 3.2.4,2010-06-13T10:18:04Z,2018-01-15T16:10:37Z,2018-01-15T16:10:37Z,"When you have several hard drives set in your VM and the actual boot disk is SATA or on any other controller than IDE, while you have an IDE hard drive attached, it will fail to boot. There is no way to set the controller priority in the VM settings for booting the VM. The first detected hard drive is tried, but never another if that one fails.

Here is one of the examples, though the issue describes something else too:
http://forums.virtualbox.org/viewtopic.php?f=6&t=31956
The first reply (second post) is the vital one.

It is reported for version 3.2.4, but I think this problem exists in all versions where more controllers are available. It doesn't matter which host or Guest you have. It also appears that the OS you want to boot using the boot menu (F12) may fail.

I have attached two log files, it's the same VM, one where I let it boot without intervention and it just stays on a black screen with a blinking _ and 100% CPU on one core. It tries to boot from a data VDI, it doesn't contain an OS.
The second log is where I selected the proper device (AHCI SATA drive) and got the error ""A Boot Error Occurred"".",Sasquatch
17673,Guru Meditation,VirtualBox 5.2.8,2018-04-10T13:36:56Z,2018-04-10T13:37:54Z,2018-04-10T13:37:54Z,Both Ubuntu and Win7 Guest VM,maxine
20546,Guest suspended with DiskFull error when using fixed size VDI,VirtualBox 6.1.26,2021-09-13T21:58:24Z,2021-09-14T06:52:48Z,2021-09-14T06:52:48Z,"VirtualBox guest with fixed size VDI file is suspended when the host runs low on disk space.
Fixed size VDI files should never trigger a disk full condition as they are a fixed preallocated size that will never expand.

VirtualBox build 146314
Host: Fedora Linux 33
Guest Fedora Linux 34
Log File Info:
VD#1: Host disk full
VM: Raising runtime error 'DrvVD_DISKFULL' (fFlags=0x6)
Console: VM runtime error: fatal=false, errorID=DrvVD_DISKFULL message=""Host system reported disk full. VM execution is suspended. You can resume after freeing some space""

VBoxManage showmediuminfo disk ...
Storage format: VDI
Format variant: fixed default
Capacity:       66560 MBytes
Size on disk:   66562 MBytes",RP15873
8148,Guest pre-boot check cycle of .vmdks with raw disks does not detect mismatch in drive geometry,VirtualBox 4.0.2,2011-01-22T15:39:56Z,2011-01-22T15:39:56Z,2011-01-22T15:39:56Z,"Hi! :)

I asked a question about this on the forums (http://forums.virtualbox.org/viewtopic.php?f=6&t=38285&start=0), and then did some testing to try to satisfy my concerns.

Issue at hand: If I have set up my VBox guest on a Windows host to access disks using raw device .vmdks, what will happen when I add a new controller, change BIOS drive order, remove a drive, or similar, which would cause Windows' \.\PhysicalDriveX links to point to physical devices different to what has been described in the .vmdks. E.g. that a 2TB physical disk is referenced to by a .vmdk describing the geometries of the 1TB disk that used to be at that PhysicalDriveX path.

<Copy/paste from my post in the forums>
First test:
I picked out two .vmdks, one pointing at a 1TB drive, the other pointing at a 2TB drive. I then switched them around, i.e. renamed them.

The ""Storage"" list in the main manager window did not pick up on this change. It still listed the ""old"" settings, i.e. the sizes for the previously corresponding \.\PhysicalDrive targets. However, upon booting, the OS report I/O errors on the drives in question.

This suggests that VB kept the geometry info from when the drives were attached, but read in the new \.\PhysicalDrive paths. Not good. Had I set up md and zfs already, I'm guessing this would not have been good for my data.

Second test:
I edited the two .vmdks to switch around physical drives.

Again, there's no update in sizes in the ""Storage"" list, and again, booting results in ""Buffer I/O error"" messages in logs and TTYs. No warning from VB.
</Copy/paste from my post in the forums>

With these raw disk .vmdks, VBox is spending quite a bit of time doing its checks before booting a VM the first time. I believe this time should also be spent comparing the geometries registered in the .vmdk with the actual, current, geometries of each drive, and when finding a mismatch either aborting (seems sane) the process with an error, or at least warning the user and blocking the boot until the user has determined what to do.

The way it works now, a broken power line to a drive could cause complete reordering of a list of drives upon reboot (possibly initiated automatically by the BIOS subsequent to a crash on behalf of the failing drive). If the VM is set to automatically boot, and ignores the discrepancies in geometries, you might find yourself starting RAID systems or ZFS pools on drives that have bad geometries and will I/O error out on everything, possibly causing severe data corruption.
",Daniel Smedegaard Buus
20766,"Frequest VM crashes, looks like host virtio driver issues",VirtualBox 6.1.30,2022-01-10T06:47:19Z,2022-01-13T08:53:02Z,2022-01-13T08:53:02Z,"After upgrade of host system from Debian Buster to Debian Bullseye (including upgrade of virtualbox package), I'm getting frequent crashes of linux VMs.

It looks like I'm away for a while, and when I return, VMs are not running, status in GUI is ""Aborted"", and several last log lines look like


{{{
...
00:55:34.164526 Pausing VM execution, reason 'host suspend'
00:55:34.164560 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:55:34.164612 PDMR3Suspend: after     0 ms, 1 loops: 1 async tasks - virtio-scsi/0
00:55:34.204298 AIOMgr: Endpoint for file '/home/nikita/VirtualBox VMs/vzvm/vzvm.vdi' (flags 000c0781) created successfully
00:55:34.225496 PDMR3Suspend: 60 917 038 ns run time
00:55:34.225515 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:55:34.225530 Console: Machine state changed to 'Paused'
00:55:34.225681 GUI: Releasing keyboard on pause/stuck
00:55:34.225884 GUI: Releasing mouse on pause/stuck
00:55:45.439541 Resuming VM execution, reason 'host resume'
00:55:45.439633 Changing the VM state from 'SUSPENDED' to 'RESUMING'
00:55:45.439825 AIOMgr: Endpoint for file '/home/nikita/VirtualBox VMs/vzvm/vzvm.vdi' (flags 000c0723) created successfully
00:55:45.445823 virtioCoreVirtqAvailBufCount: Driver not ready or queue not enabled
00:55:45.445875 virtioCoreVirtqAvailBufCount: Driver not ready or queue not enabled
}}}


I'm not sure what is ""host suspend"" mentioned here, there was no manual host suspend at the shown time, although it could be something system-initiated.

Virtualbox is from virtualbox-6.1 package version 6.1.30-148432~Debian~bullseye

Host kernel is from debian package linux-image-5.10.0-10-amd64 5.10.84-1.",nikita_yoush
17624,Files containing only zeroes gets modified after restart,VirtualBox 5.1.12,2018-03-16T16:49:37Z,2018-03-16T16:49:37Z,2018-03-16T16:49:37Z,"Hi,

I would like to report that files containing only zeroes, gets modified after turning the virtual machine off and on.

Before the restart:
{{{
piotrek@sue:~> dd if=/dev/zero of=zeroes_1GB bs=1M count=1024
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,678558 s, 1,6 GB/s
piotrek@sue:~> cmp /dev/zero zeroes_1GB
cmp: EOF on zeroes_1GB
}}}

After the restart:
{{{
piotrek@sue:~> cmp /dev/zero zeroes_1GB
/dev/zero zeroes_1GB differ: byte 647411201, line 1
}}}

The place of the first difference seems to be pretty much random. This can be illustrated by another example.

Before the restart:
{{{
piotrek@sue:~> for i in {1..10}; do dd if=/dev/zero of=zeroes_1GB_$i bs=1M count=1024; done
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 0,62127 s, 1,7 GB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 1,80431 s, 595 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,4662 s, 310 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,16451 s, 339 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,0117 s, 357 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 3,51445 s, 306 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 2,57957 s, 416 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 6,12661 s, 175 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 7,04536 s, 152 MB/s
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB, 1,0 GiB) copied, 5,41265 s, 198 MB/s

piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
cmp: EOF on zeroes_1GB_1
cmp: EOF on zeroes_1GB_2
cmp: EOF on zeroes_1GB_3
cmp: EOF on zeroes_1GB_4
cmp: EOF on zeroes_1GB_5
cmp: EOF on zeroes_1GB_6
cmp: EOF on zeroes_1GB_7
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

After the restart:
{{{
piotrek@sue:~> for i in {1..10}; do cmp /dev/zero zeroes_1GB_$i; done
/dev/zero zeroes_1GB_1 differ: byte 794570753, line 1
/dev/zero zeroes_1GB_2 differ: byte 242036737, line 1
/dev/zero zeroes_1GB_3 differ: byte 184365057, line 1
/dev/zero zeroes_1GB_4 differ: byte 10874881, line 1
/dev/zero zeroes_1GB_5 differ: byte 460075009, line 1
/dev/zero zeroes_1GB_6 differ: byte 48693249, line 1
/dev/zero zeroes_1GB_7 differ: byte 101187585, line 1
cmp: EOF on zeroes_1GB_8
cmp: EOF on zeroes_1GB_9
cmp: EOF on zeroes_1GB_10
}}}

When I cat one of the files, I recognize the content that is normally on my disk (for example xml requests that I store).

VirtualBox version: 5.1.12 r112440 (Qt5.6.2)

Host: Windows 7

Guest: OpenSuse 42.2

Linux kernel version: 4.4.104-18.44-default

Laptop: Dell Precision 3510

Screenshots of applicable virtual machine settings attached.

Best regards,

Piotr",PeterC
15506,Feature request: compression,,2016-06-14T04:52:38Z,2016-07-13T18:30:47Z,2016-07-13T18:30:47Z,"Just as encryption was introduced, it would be nice to have compression as well.
Benefits:
- saves storage space, especially on VMs living on an SSD
- saves data when downloading pre-built appliances
- increases the entropy for the encryption operation

Info:
I tried to use Windows's built-in transparent compression on a Windows 7 guest: the space got shrinked from over 30GB to 16GB.",Lieutenant
8848,Feature Request: Ability to map VDI to Windows and use them as a harddrive,VirtualBox 4.0.6,2011-05-04T22:12:35Z,2011-05-04T22:40:54Z,2011-05-04T22:40:54Z,"Ability to map vdi to windows and use them as a harddrive storage directly. Windows doesn't have easy way loop-mount facility. This will require writing Windows-host SCSI driver to make it work. Possible, but hard.",DNS
15842,Error with VBoxManage internalcommands createrawvmdk on SAS 4K block size drive.,VirtualBox 5.1.4,2016-08-21T22:16:56Z,2016-08-21T22:16:56Z,2016-08-21T22:16:56Z,"  - The host (and guests) are under Ubuntu 16.04.1 LTS.
  - My system has 2 X SAMSUNG MZ7KM480 SSD and 6 X SEAGATE  Model: ST1000NX0323. I can create virtual drive on SSD drives without any problem but it does NOT work on SAS drives. The problem is the same with DOS or GPT format.
  - The user is in vboxusers and disk groups.
  - Partitions are readable with the dd command.

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdatah6.vmdk -rawdisk /dev/sdh -partitions 6
VBoxManage: error: Logical partition without magic
VBoxManage: error: Cannot read the partition information from '/dev/sdh'
VBoxManage: error: The raw disk vmdk file was not created
ma@X10DRi:~$ fdisk -l /dev/sdh
Disk /dev/sdh: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x44def683

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdh1            256 244190645 244190390 931,5G  5 Extended
/dev/sdh5            512  52429311  52428800   200G 83 Linux
/dev/sdh6       52429568  55051007   2621440    10G 83 Linux

ma@X10DRi:~$ VBoxManage internalcommands createrawvmdk -filename /export/VirtualBox/VMs/VM-A1/lvdataf6.vmdk -rawdisk /dev/sdf -partitions 6
VBoxManage: error: Cannot read the partition information from '/dev/sdf'
VBoxManage: error: The raw disk vmdk file was not created

ma@X10DRi:~$ fdisk -l /dev/sdf
Disk /dev/sdf: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3D5F9AA3-AA3D-49E4-88B7-1E9CD35FFDF8

Device        Start      End  Sectors  Size Type
/dev/sdf5       512 52429311 52428800  200G Linux LVM
/dev/sdf6  52429568 55051007  2621440   10G Linux filesystem

#
# The behavior is exactly the same with the root user.
#
 - hdparm works well with our SSD drive seems NOT to be working with our ST1000NX0323 drives
 - smartctl works well on our both type of drives
 ",michelparis
16026,"error reuse physical disk after open ""computer management"" console",VirtualBox 5.1.6,2016-10-04T16:38:21Z,2016-10-06T09:28:24Z,2016-10-06T09:28:24Z,"If I open ""computer management"" console (in Win 7x64 host), to use the physical disk becomes impossible (io error, write error etc.), guest system becomes unbootable. 
Also to install guest, had to remove pre-existing disk partition. Only then became possible to format it from the guest system.

Is it possible to make a mapped physical drive does not fall off when restart host system?

I used the following command:

cd C:\Program Files\Oracle\VirtualBox

VBoxManage.exe internalcommands createrawvmdk -filename H:\VBoxHDTools\ssd7.vmdk -rawdisk \\.\PhysicalDrive5


",Nick07
16784,Encrypting an unregistered disk from command line while no VBoxSVC.exe running may cause data loss,,2017-05-24T19:05:38Z,2017-05-26T18:23:14Z,2017-05-26T18:23:14Z,"If the command ""VBoxManage encryptmedium"" is run on an unregistered disk file while no Virtualbox window is open, data loss may result:

1. Release a good disk from a test guest (make a copy for a backup). Unregister the disk from the Media Manager so it does not show in the list. Close all Virtualbox windows. Ensure that the VboxSVC.exe process has closed.

2. Run the command line on the good disk file.

3. The running of the command will launch a new VBoxSVC.exe to support the command. When the command completes, the associated VBoxSVC.exe will close in a few seconds. If you can get the main Virtualbox window open before the VBoxSVC.exe from the command line closes, the main Virtualbox Window will know about the newly-encrypted disk and use it properly.

4. If you cannot get the main Virtualbox window open before the command's associated VboxSVC.exe closes, then the main Virtualbox windows will not know the disk was encrypted. The DEK for that disk will be lost, and the disk's internal data is scrambled and unusable.",scottgus1bug
11802,Enable user to set a separate directory for current state,VirtualBox 4.2.12,2013-05-15T05:25:23Z,2017-03-16T13:16:54Z,2017-03-16T13:16:54Z,"This enhancement is an alternative solution to Ticket #11726.

While the suggested enhancement in 11726 covers the problem somewhat, this here would be the fullscale solution.

Just as you can set a directory for snapshots of a given virtual machine, you could now also set the directory for the current state.
This would enable running current state from faster drives, such as RAM disks.",bostjan
17200,Disable COW for disk images on btrfs,VirtualBox 5.1.30,2017-10-22T17:41:02Z,2018-06-04T21:52:50Z,2018-06-04T21:52:50Z,"Since copy-on-write (COW) feature of modern file systems (e.g. BtrFS) decreases the performance of disk images significantly, it should be turned off by default.

Therefore, I suggest adding a checkbox in the ""New VM"" and ""VM Properties"" dialogues to disable COW and set this by default.

This way, the user still has full control, nothing happens ""in the background"" without the user noticing and it is a useful default for most of the users!

See some discussion on this topic in #11862",darkdragon
15893,Differencing disk for shared immutable disk saved to wrong VM settings file,VirtualBox 5.1.4,2016-09-06T15:03:25Z,2016-09-06T15:07:30Z,2016-09-06T15:07:30Z,"Sharing an immutable drive across two VMs causes VirtualBox to save the differencing disk configuration in the wrong VM's configuration file. This is causing my scripts to fail when they search for the differencing disk UUID in the configuration.

After creating both VM's, the following appears in VM1's configuration file:

{{{
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid=""{c1487c8e-ab83-41ca-8efa-92e14b36c4dc}"" location=""E:/Golden Images/W2K12.vhd"" format=""VHD"" type=""Immutable"">
          <HardDisk uuid=""{a721fb7e-9bae-4347-9e32-f6e73fab310e}"" location=""Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" format=""VHD""/>
          <HardDisk uuid=""{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}"" location=""E:/Machines/VM2/Snapshots/{ac2da970-c422-4c48-9b7d-9b7ce9d8c5d1}.vhd"" format=""VHD"" autoReset=""true""/>
        </HardDisk>
      </HardDisks>
    </MediaRegistry>
}}}

No MediaRegistry exists in VM2's configuration file. I expected to see a MediaRegistry in both configuration files, each containing only their specific VM's differencing disk.

I can reproduce the issue with the following commands. To create VM1:
{{{
VBoxManage.exe createvm --name VM1 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM1 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM1 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM1 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM1 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM1 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
VBoxManage.exe modifyhd ""E:\Golden Images\Snapshots/{a721fb7e-9bae-4347-9e32-f6e73fab310e}.vhd"" --autoreset off
VBoxManage.exe modifyvm VM1 --nic1 hostonly --hostonlyadapter1 ""VirtualBox Host-Only Ethernet Adapter""
}}}

To create VM 2:
{{{
VBoxManage.exe createvm --name VM2 --ostype Windows2012_64 --register
VBoxManage.exe modifyvm VM2 --memory 4096 --vram 128 --vrde off --accelerate3d on --accelerate2dvideo on --usb on
VBoxManage.exe storagectl VM2 --name ""SATA Controller"" --add sata --controller IntelAHCI
VBoxManage.exe storagectl VM2 --name ""IDE Controller"" --add ide
VBoxManage.exe storageattach VM2 --storagectl ""IDE Controller"" --port 0 --device 0 --type dvddrive --medium emptydrive
# This line is redundant, but executed by my scripts to ensure the shared disk is immutable.
VBoxManage.exe modifyhd ""E:\Golden Images\W2K12.vhd"" --type immutable
VBoxManage.exe storageattach VM2 --storagectl ""SATA Controller"" --port 0 --device 0 --type hdd --medium ""E:\Golden Images\W2K12.vhd""
}}}

I apologize if this is simply because I'm not using the command line interface correctly.",Joshua Rehm
8485,Differencing disk created from multiattach base disk is marked as auto-reset,VirtualBox 4.0.4,2011-03-03T18:48:31Z,2011-03-03T19:08:39Z,2011-03-03T19:08:39Z,"According to the [http://www.virtualbox.org/manual/ch05.html#hdimagewrites VirtualBox] docs:
  ''Technically, a ""multiattach"" image behaves identically to an ""immutable"" image '''except the differencing image is not reset every time the machine starts'''.''

This doesn't appear to be the case.

I created a VM with a dynamically sized disk, installed Win7, sysprepped the VM and shut it down. I released the HDD and used '''VBOXMANAGE MODIFYHD ... -TYPE MULTIATTACH''' to mark this HDD as immutable and that children should not auto-reset.

I then created a new VM, using the base HD which created a differencing disk for its own data.

Using '''VBOXMANAGE SHOWHDINFO ...''', I examined the new VM's differencing disk and saw that it claims auto-reset is on.

I booted the new machine, completed the OOBE (Out Of Box Experience) and modified the desktop wallpaper. I shut down the VM and then rebooted it and was sent straight back to the OOBE again.

VirtualBox is a great product, but its poor handling of differencing disks, requiring users to delve around in the command-line tools to configure even the most rudumentary differencing scenarios, is, in my opinion, VirtualBox' biggest weakness, especially when compared to Hyper-V and VMWare.

PLEASE fix this bug and consider improving VirtualBox' GUI for handling differencing disks.",bitcrazed
17938,Deleting snapshot on-line causes I/O errors in guest,VirtualBox 5.2.16,2018-08-18T21:53:28Z,2018-08-19T09:09:22Z,2018-08-19T09:09:22Z,"Host: Fedora 28
Guests: Fedora 28 x2 + (2 older Fedora machines)

Both guests in this event are F28 & had a single snapshot + current state, and were up (but largely idle).

Deleted snapshot of first machine.  (Using VirtualBox GUI).  It took quite a while, as the snapshot was almost 2 yrs old.

While the delete was running, I had an ssh session into the VM.  I got an error ""Read only filesystem"", then ""ps not found"".  ls worked - for a while.

This typically means that the kernel got an unrecoverable Disk I/O error - e.g. a timeout.  But as the logs live on the disk in question, and it went read-only, I can't prove it.

shutdown was also not found.  I waited a while, and commands started getting bus errors.  Seemed clear that the disks were off-line.

So I waited for the disk merge (snapshot delete) to finish, did a vboxmanage reset, and rebooted the VM.

Log file will be attached.  Note that it also shows a lot of display resize events - I see no reason for this.  The VM was started detachable; the GUI is visible, but it seems to blink for no particular reason...

Here is an 'ls' of the VDI involved:
{{{
 ls -lih /home/root/VirtualBox_VMs/Overkiller/*.vdi /home/root/VirtualBox_VMs/Overkiller/*/*.vdi
12323679 -rw-------. 1 root root 1.6G Mar 20  2016 /home/root/VirtualBox_VMs/Overkiller/Fedora23_Overkiller.vdi
12320772 -rw-------. 1 root root  35G Aug 18 16:04 /home/root/VirtualBox_VMs/Overkiller/Fedora_17_Overkill.vdi
13893639 -rw-------. 1 root root  22G Aug 18 15:49 /home/root/VirtualBox_VMs/Overkiller/Snapshots/{e981f25e-0fc7-4ba7-9666-9d00bc48eae3}.vdi
}}}

The I/O errors don't appear to be a one-off event.  I had a second VM which also had a single snapshot that I deleted the same way.  It suffered the same fate.  Log also attached.  Its ls:
{{{
ls -lih /home/root/VirtualBox_VMs/WikiWorld/*.vdi /home/root/VirtualBox_VMs/WikiWorld/*/*.vdi
9306120 -rw-------. 1 root root 30G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/Snapshots/{1bb6e5e7-1e5a-40c8-8d61-daf4ff6611be}.vdi
9306115 -rw-------. 1 root root 49G Aug 18 16:08 /home/root/VirtualBox_VMs/WikiWorld/atto_wiki.vdi

}}}

Snapshot delete times were on the order of 30 minutes (each).

If deleting a snapshot on-line can cause this much havoc, it should not be allowed...
",Timothe Litt
16540,"Deleting older snapshot reproducibly, deterministically corrupts newer snapshot",VirtualBox 5.1.14,2017-03-08T17:54:28Z,2017-03-17T10:44:30Z,2017-03-17T10:44:30Z,"On a virtual machine with a series of snapshots, deleting one of the older snapshots will, under some circumstances, cause changes to the contents of the virtual disk on newer snapshots. (That may be an overly simplified description, but I believe the reduced test case will clear up the details.)

The real-world manifestation of this bug is that, on a Win10 1607 VM of mine, deleting one of the older snapshots causes the Start menu to malfunction (lose the Settings button and all tiles) on newer snapshots.

I created a reduced test case by deleting as many snapshots as I could without the corruption happening, then creating and using a quick-and-dirty program to replace each non-empty (i.e. not all zeroes) 1MB block in each VDI file with a repeated byte value. (By the way, if I do this on all blocks rather than all non-zero blocks, the bug is no longer reproducible.)

Instructions to reproduce:
1. Extract the attached xz-compressed tar archive (it will expand to something like 33GB) and add the resulting VM to VirtualBox.
2. There are 3 snapshots: Snapshot 1, Snapshot 5, and Snapshot 11. Get the md5sum of Snapshot 11 by doing one of the following:
  a. `VBoxManage clonemedium 7e718487-9538-4552-b223-69ce21b421d0 good.raw --format RAW` then something like `openssl md5 good.raw`
  b. Boot into a simple Linux CD/DVD (I used the Slackware 14.2 installer DVD), run `md5sum /dev/sda`, then power off the VM.
3. Delete Snapshot 5. (By the way, if you delete Snapshot 1 before deleting Snapshot 5, the corruption does not occur.)
4. Check the md5sum of Snapshot 11 again by doing one of the following:
  a. `VBoxManage clonemedium 750ff504-0292-427f-b108-f4c9b78f88df bad.raw --format RAW` then something like `openssl md5 bad.raw`
  b. Repeat step 2(b).

Expected results: md5sum should be `94157a72c97d2d61e288748ec4029b6a` both times.

Actual results: md5sum is originally `94157a72c97d2d61e288748ec4029b6a` but becomes `75dc8ef4596478dee7abf47780471c98`. An examination of the difference between good.raw and bad.raw shows that some sectors that are filled with zeroes in good.raw are filled with 0x2A ('`*`') in bad.raw (the pattern that I used to fill the non-zero blocks in the base VDI).

I think what's happening is, data that was originally non-zero in the base VDI and that was overwritten with zeroes later on (probably in Snapshot 5) is being incorrectly reverted back to the older non-zero data in Snapshot 11 after Snapshot 5 is deleted. (This is the same pattern of corruption that I was seeing with the original Windows 10 VM. I did not dig into why this particular pattern of corruption causes the Start menu to malfunction.)

Emotionally, I'm tempted to set the priority of this bug to ""blocker"" because I'm not happy about data corruption. However, I'm able to reproduce this bug going back at least to VirtualBox 4.3.4 (the oldest that I've tested so far), so this bug has been around for a while and I'm guessing that either it doesn't happen often in general use or it usually has insignificant consequences.

So far I have only tested this on a Mac OS X host -- I have not yet tested a Windows or Linux host.",Barry K. Nathan
18405,Deleting a snapshot with multiple children,VirtualBox 6.0.4,2019-02-01T15:09:28Z,2019-02-01T15:09:28Z,2019-02-01T15:09:28Z,"Currently, deleting a snapshot with multiple children is not possible:
> Snapshot [...] cannot be deleted, because it has 2 child snapshots, which is more than the one snapshot allowed for deletion.

I suggest merging the disk images for each child separately.",robert@…
17606,DeleteSnap ERROR with aRC=VBOX_E_FILE_ERROR (0x80bb0004),VirtualBox 5.2.8,2018-03-08T12:02:31Z,2018-04-14T08:39:55Z,2018-04-14T08:39:55Z,"I am running VBox 5.2.8 under fc26. When I tried to delete the oldest snapshot from my Guest Win10x64 it showed progress 4, 3, 2 minutes,
but the all of a sudden the CPU consumption of all 4 cores went up
and the Delete Snapshot ended with a dialog message 
""Callee RC: NS_ERROR_CALL_FAILED (0x800706BE)"".
In the VBoxSVC.log I found the last message:

00:11:03.872176 DeleteSnap ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not merge the medium '/home/ksp/VB/Machines/Win10/Snapshots/{299f0e8c-9fca-4d32-be09-8e3201ee7117}.vdi' to '/home/ksp/VB/Machines/Win10/Win10-disk1.vdi' (VERR_INVALID_PARAMETER)}, preserve=true  aResultDetail=0

The problem is reproduceable
",snoopy26
12894,Deleted snapshots leave removable media attached,VirtualBox 4.3.10,2014-03-31T10:22:54Z,2018-11-03T06:41:37Z,2018-11-03T06:41:37Z,"When taking a snapshot, removable media such as DVD images or floppy disks images are also referenced as part of that snapshot. However, deleting the snapshot still leaves the media attached to the snapshot and it can't be released or removed. This was done under Linux version 4.3.10 but the issue has been around for a while as far as I can tell.

For example:

1. Create a new guest, with a floppy drive controller
2. Attach a floppy disk image as drive a:
3. Take an offline snapshot of the guest
4. Edit the new guest's settings, and remove the floppy disk image
5. Delete the snapshot of the guest.

Go to the VMM and highlight the floppy disk image, it will still show it as being attached and it can't be released. This can be worked-around (on Linux at least) by doing

/etc/rc.d/init.d/vboxdrv restart

which obviously unloads and reloads the kernel modules, releasing the disk image.


When using the API, querying a floppy image for example to see what it's attached to, generates an invalid object reference, presumably the IMachine or ISnapshot reference no longer exists. Using the API I've tried to detach the disk before deleting the snapshot, but I can't because the IMachine reference returned by the ISnapshot class is immutable. Also using IMachine::MountMedium with a null medium reference doesn't work.

I suspect that IConsole::DeleteSnapshot should be taking care of releasing any removable media attached to the snapshot.

",oddsocks
7381,Delete all snapshots at once,VirtualBox 3.2.8,2010-08-26T07:01:04Z,2023-02-03T19:58:49Z,2023-02-03T19:58:49Z,"Hello,

I'd like to request the ability to delete all snapshots with one command.  Something like having an ""all"" parameter to the VBoxManage snapshot delete command, or other means to fully automate the updating of all snapshots back into the base virtual disk.

""Sasquatch"" suggested I open a ticket here and give a link to my suggestion thread in the forums: http://forums.virtualbox.org/viewtopic.php?f=9&t=33864

Thank you for your consideration.

Kind Regards,
--appyface
",appyface
13298,Custom snapshot location for each virtual disk,VirtualBox 4.3.14,2014-08-18T15:41:39Z,2014-08-18T15:41:39Z,2014-08-18T15:41:39Z,"I was hoping to set up a mirrored disk set up with zfs having two vdi'a stored on two different physical disks.  In theory then if one physical disk was lost I would still have my mirrored data.  However, due to the fact that I have snapshots the data is actually be written to the same physical disk despite the real vdi's being on two separate physical disks.

I request a feature to be able to define the location of snapshot files for each virtual disk.",jeremywj
16950,crashis when adding virtual device to sata controller,VirtualBox 5.1.24,2017-07-27T09:32:16Z,2017-07-27T09:32:16Z,2017-07-27T09:32:16Z,"in mashin settings window i opens the storage tab and right click on the controller's item on the list of the devices and select add harddisk or dvd in context menu
next the VirtualBox Manager crashis.",ilyapashuk
13079,clonevm makes immutable hard disks normal in clone,VirtualBox 4.3.12,2014-05-31T12:22:05Z,2014-05-31T12:22:05Z,2014-05-31T12:22:05Z,"When cloning a VM, '''ALL''' the cloned new VM's hard disks are of type '''normal''' whereas some of the source VM's hard disks are of type '''immutable'''.  Cloning is not preserving hard disk type and is resetting immutable hard disks to normal.

Both host and guest are Ubuntu Trusty Server.",Senthil Nathan
9964,cloned(full) openSUSE12.1 is not able to find it´s harddrive,VirtualBox 4.1.6,2011-11-28T16:49:27Z,2011-11-28T16:56:50Z,2011-11-28T16:56:50Z,"I´ve made two clones of a working openSUSE12.1 64bit vm(on a openSUSE12.1 64 bit host).

Both have problems to start up correctly.

They tell me that they have problems to find their harddrive and give me an option to make a fallback to a other drive as far as I could see.

It´snot important what I choose then, both failed.

I attach a screenshot for the exact error message and the logs.",maninred2
17138,Changes to VMDK image on USB Storage Not Preserved,VirtualBox 5.1.28,2017-10-04T17:52:33Z,2017-10-05T14:06:38Z,2017-10-05T14:06:38Z,"I have a VM with a VMDK file mounted on a USB mass storage device (e:\ drive).  The Guest OS is CentOS 7.3.1611 (32 bit).  I have been using it without issues for about a week.

Yesterday, I modified a few files on the VM and then rebooted the VM --- and the file changes were gone!  I thought maybe user error, but I created a test file in my home directory and rebooted, and the file did NOT persist (as if the disk was a ramdisk, even though it's not).  I tried this several times, with different ways of rebooting (shutdown -r, manually typing sync first, CentOS GUI, etc), with the same result.

I looked through log files but didn't see anything that looked out of the ordinary.

I have a feeling this has to do with USB -- maybe plugging/unplugging other USB devices confused the OS or VirtualBox -- just a guess.  But in any case, there was no warning that my changes were not being saved onto the disk image.

After this testing, I restarted my host PC (Windows 7), and now things appear to be working -- although I have lost some trust with this setup since I don't really know what happened and it caused data loss.",Joe E Clark
20432,Cannot write to raw disk under Windows 10 21H1 guest in VBox 6.1.22,VirtualBox 6.1.22,2021-06-27T13:05:56Z,2021-06-27T14:06:44Z,2021-06-27T14:06:44Z,"Severe bug, results in complete loss of all data written.

Quick description: I have some mechanical Western Digital Purple SATA drives hooked up via a Perc H310 SAS HBA. (SAS can use SATA drives). Windows 10 host, Ubuntu guest. Some of them can be written, but one which is larger and has NTFS on it can't. The ones that can be written to use ext4 and btrfs partitions. This probably isn't relevant, but who knows.

I had been using VBox 6.1.15 on a Windows 10 host (updated to latest non-insider version which is 21H1, build 19043.1081) with a Ubuntu 20.04 guest, with guest additions installed. Recently, I tried using it with a 14 TB WDC WD140PURZ-850A82 (Western Digital Purple 14TB mechanical SATA drive) connected via a Perc H310 SAS HBA. It is completely new and I created a single partition on it spanning the whole disk. I formatted it to NTFS using Windows 10 and put it offline, then created a VMDK using 

{{{
PS C:\WINDOWS\system32> & 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe' internalcommands createrawvmdk -filename C:\VirtualBox\SAS-PhysicalDrive5-14tb.vmdk -rawdisk \\.\PhysicalDrive5
}}}

and then set it to write-through under the VBox gui. Finally I hooked it up to a SATA AHCI controller with 16 ports. The ""Use Host I/O Cache"" box was originally empty (unchecked), and I would get this error:

{{{
The I/O cache encountered an error while updating data in medium ""ahci-0-4"" (rc=VERR_WRITE_PROTECT). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards.
Error ID: BLKCACHE_IOERR
Severity: Non-Fatal Error
}}}

If I DO check the ""Use Host I/O Cache"" box, then the data seems to get written and no error is produced - but when I unmount and remount the partition, it's gone.

What's weird is that there are other drives, also from the same drive family (WD Purple) and on the same SAS controller, which don't have the same issue. But they're linux formatted (either ext4 or btrfs) and also smaller (less than 10 TB).

If I turn on ""Use Host I/O Cache"", I am able to write to the disk. However, 3 issues remain still:

1. performance is very, very poor. On the order of 20 MB/sec. These drives are capable of 150 MB/sec when used under the Windows 10 host on the same controller.

2. if I type sync in the guest, it takes > 5 minutes, and meanwhile hangs up all disk IO

3. The data isn't ACTUALLY written to the disk.


Things I tried include:
- formatting the disk again. Didn't help
- I tried whether writing to the disk works when it's hooked up to the host (and not offlined). It works - files written to disk remain after offlining and again onlining the disk (which essentially unmounts and again mounts the disk on Windows 10).
- I updated to VBox 6.1.22 with latest guest additions, no improvement
- In the VM, I created a new LsiLogic SAS controller, and put the drives under that, no improvement

Finally, I am always running VBox GUI as admin, which is required in order for raw disk access to work in the first place, for all drives, even the ones where writing to disk does work.

Also, I've noticed that when I format the disk to a single NTFS partition under Windows 10, it actually creates two partitions: one tiny ~15MB one that's a ""Microsoft reserved partition"" (/dev/sde1 under Linux for me), and one that spans the rest of the disk (/dev/sde2) (which is where the data lives). Under the Windows 10 Disk Management panel, only one partition is shown. When I mount /dev/sde2, I can see the System Volume Information directory and some other files I put on that drive when it was mounted directly on the host, so I know it's the right partition.

P.S. I have previously re-opened #14461 thinking that was the same bug, but it's not - in #14461 you could work around to write data to the disk, in my situation the same workaround results in data being written to a black hole. Could someone please close that ticket?",cheater
9808,Cannot delete snapshot due to hidden differencing image,VirtualBox 4.1.4,2011-10-25T08:40:44Z,2011-12-08T12:20:07Z,2011-12-08T12:20:07Z,"Fairly regularly, I find that when I try to delete a snapshot, the VBM (VBox Manager) reports that it cannot because there is more than one child hard disk.  However, the VBM does not show any indication of its existence in the snapshot hierarchy.  I can only see the extra disk in the VMM (VMedia Manager), where I can delete it and then successfully delete the snapshot from the VBM.

However, that the VBM and VMM disagree about the disk/differencing hierarchy must be a bug, right?

In all of the situations where this has occurred, I have done nothing more complex than periodically create snapshots and periodically delete them.  The disks are not shared across machines and I've not cloned any machines.  Unfortunately, it's not reproducible, it just occasionally happens.  I've come across this problem on 2 different hosts with 4.1.4.  I think I've seen it in earlier versions too.",simon marshall
12045,Cannot attach new vm via multiattach when another vm is running,VirtualBox 4.2.14,2013-08-22T17:55:08Z,2013-08-22T17:55:08Z,2013-08-22T17:55:08Z,"Cf. bug report: https://www.virtualbox.org/ticket/11700. The suggested solution doesn't work if the vdi file is read only (on the file system).

After running the commands

NAME=test1

VBoxManage createvm --name ""${NAME}"" --ostype Ubuntu --register

VBoxManage modifyvm ""${NAME}"" --memory 1024

VBoxManage storagectl ""${NAME}"" --name ""sata1"" --add sata

VBoxManage storageattach ""${NAME}"" --storagectl ""sata1"" --port 0 --device 0 \
    --type hdd --medium /path/to/my.vdi --mtype multiattach

to create a new vm (with an existing multiattach virtual disk), I start up the vm. While it's running, I create a new vm with similar commands, but I get the following error:

VBoxManage: error: Medium '/home/charlesj/vm/2100vm.vdi' is locked for reading by another task
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component Medium, interface IMedium, callee nsISupports
VBoxManage: error: Context: ""COMSETTER(Type)(mediumType)"" at line 678 of file VBoxManageStorageController.cpp
VBoxManage: error: Failed to set the medium type

It looks like it's trying to set the medium type prematurely (in case it isn't multiattach).

Setting up a new vm with multiattach works when all attached vms are powered down / suspended, even when the vdi file is read only.

I've attached the log file for the first machine that successfully boots; the second machine does
not produce a log file on failure.",charlie-jacobsen
21206,Can't start vm after update,VirtualBox-7.0.2,2022-10-26T10:11:12Z,2022-10-26T20:22:32Z,2022-10-26T20:22:32Z,I have an ubuntu virtual machine with an encrypted disk on windows host. After update from 6.1.40 to 7.0.2 it does not start (there is no window where I can print my password for decryption). After downgrading to 6.1.40 I successfully started my vm.,sorsdt
21424,can't create new vdisks; verr_write_protect returned,VirtualBox-7.0.6,2023-01-22T07:22:10Z,2023-01-22T07:22:10Z,2023-01-22T07:22:10Z,"Hi!
I'm using Mac OS X Ventura 13.0.1 M1 
VirtualBox Version 7.0.6_BETA4 r155176 (Qt6.3.0) and tried to create a new vdisk but returned ""verr_write_protect""
",Red Cactus
2282,Blue screen during install of Windows XP with slipstreamed SATA driver,VirtualBox 2.0.2,2008-09-20T01:31:27Z,2013-10-21T06:20:57Z,2013-10-21T06:20:57Z,Attempt to install Windows XP SP3 (slipstreamed) with slipstreamed driver Intel Matrix 7.0.0.1020 results in blue screen ,vadimrapp
11137,BIOS call int13h cannot access more than 4 HDDs on the SATA or SCSI controller.,VirtualBox 4.2.4,2012-10-28T13:06:25Z,2014-04-06T21:32:35Z,2014-04-06T21:32:35Z,"When I set up 6 HDDs on SATA controller, BIOS in VirtualBox does not recognize last 2 HDDs. If the last 2 HDDs are connected to SCSI controller, i.e. 4 HDDs on SATA and 2 HDDs on SCSI, all the 6 HDDs can be accessed via int13h.

Similarly, more than 4 HDDs on SCSI and SAS controller cannot be accessed by int13.

This causes boot failure problem of linux in software RAID5 partition with 6 HDDs.

The ""User Manual"" says VirtualBox supports 4 HDDs to IDE, 30 HDDs to SATA, 15 HDDs to SCSI and 8 HDDs to SAS controller. Since real PC BIOS can access all the HDDs connected to SCSI controller as usual, this is a bug of VirtualBox BIOS, I believe.

This problem is also in version 4.2.2 and 4.2.0, and maybe older version.
",Yano
15552,attaching differencing vhd on host makes it unusable on guest,VirtualBox 5.0.22,2016-06-28T08:18:11Z,2016-08-10T12:28:37Z,2016-08-10T12:28:37Z,"When you attach a differencing VHD on Windows host using diskpart or mmc, there's a chance that VBox will no longer understand the format of that VHD. If guest booted, it will see a corrupted filesystem.

I attach my VHD file on Windows 7 host. It's virtual size is 50G and it has one partition formatted to NTFS. I created a dummy VM in VBox GUI to manage snapshots. Currently, the chain consists of 4 image files. 

I didn't boot the guest until now. When I did, guest chkdsk spew tons of errors. Then I stopped the guest and attached the VHD on host again. chkdsk showed no errors.

I went further and restored the 'good' backup (there's a backup of all the .vhd and .vbox files I made before the guest boot). Marked the volume as readonly using diskpart and compared the contents of the block device using cygwin. They're indeed different!

",lfmeloman
17028,ata2.00 exception Emask 0x0 SAct 0x0 SErr action,VirtualBox 5.1.22,2017-08-21T06:25:54Z,2017-08-21T09:50:55Z,2017-08-21T09:50:55Z,"Hi

Every alternate day on Guest VM running with RHEL 6.5 64bit cpu usage is high and after reboot it shows this error
 
ata2.00 exception Emask 0x0 SAct 0x0 SErr action  on 0x6 is frozen

attached screen shot for more details[[Image()]]",prabhakarraksan
12549,async I/O bug,VirtualBox 4.3.6,2013-12-28T19:31:18Z,2013-12-28T19:31:18Z,2013-12-28T19:31:18Z,"Hello,[[BR]]
I had some problems with async I/Os so I looked at the implementation in more details. VirtualBox is not able to handle multiple requests, when e.g. VD.cpp!vdIOIntWriteMeta is called several times and crash.

Repro steps:
1. Assume VD.cpp!vdIOIntWriteMeta is called (pMetaXfer block is allocated, pfnWriteAsync is called, pMetaXfer is insterted into pTreeMetaXfers).
2. Another vdIOIntWriteMeta call is invoked, let's say for the same block. The first request has not been completed yet so pMetaXfer is received (line 4428) from the tree. Assert on line 4443 is invalid, because pMetaXfer->fFlags is set to VDMETAXFER_TXDIR_WRITE. Now, vdMetaXferCompleted is invoked for the first request - pMetaXfer context is removed from the tree (line 3784) and freed (line 3786). When the second request is completed, this request works with already freed pMetaXfer context.

The same problem is also for vdIOIntReadMeta + vdIOIntFlush functions.

I fixed this by referencing volatile VDMETAXFER.cRefs (ASMAtomicDecU32/ASMAtomicIncU32) before I call pfnReadAsync (line 4336)/pfnWriteAsync/pfnFlushAsync functions. 

Thanks,[[BR]]
Petr Kurtin",Petr Kurtin
21334,arcaos hard disks not recognized,VirtualBox-7.0.4,2022-12-12T04:35:48Z,2023-01-31T17:31:12Z,2023-01-31T17:31:12Z,"In Arcaos (OS/2) guests, hard disks are no longer recognized with Win ver 7.x.  The hard disks worked normally with ver 6.x.  The hard disks fail to be seen and partitioned. This defect is in BIOS or EFI installations.  This defect is seen with SATA, IDE, NVME type virtual storage.  The CD ROM is recognized and works normal in SATA. I had to revert back to 6.1.40.  Everything works in ver 6.x.",Rich87
6990,"AIOMgr documentation, transparency needed",VirtualBox 3.2.4,2010-06-14T10:35:26Z,2010-06-14T11:06:37Z,2010-06-14T11:06:37Z,"There's nothing much available in terms of AIOMgr documentation. Some of the things I'd like:

 1. recommended system settings to enable AIO (e.g. kern.aioprocmac sysctl on OS X)
 2. several settings are referenced in the logs (cache commit interval, cache commit threshold), but it's not clear where these settings are made and where it might be appropriate to change them
 3. it's not clear where to get metrics to determine whether tunings are working as expected or where problems may crop up in the I/O path

In terms of metrics and debug, I've got a number of cases where CPU utilisation on Windows guests maxes out in the middle of disk I/O, and I can't really tell at what level the problem occurs. I noticed that SAS controllers don't produce metrics at all. Perhaps more importantly, the primary metrics interfaces don't appear to show disk I/O (I can only find this through the session information dialog in the GUI) or allow me to understand how the queuing looks to the guest or how it's being passed on to the host. I can't really understand whether there's some synchronisation problem in the drivers in the guest that are causing the problem or whether the guest is queuing I/O faster than the host is dispatching it, leading Windows to throw a tantrum because I/Os are appearing to time out or some such. As this is an issue where the guest hangs without giving me much in the way of data about whatever it was that caused it to hang (and this is in the middle of things like running Windows Update, so it's not the kind of case where a hang would be expected), it would be extremely useful to be able to observe the guest behaviour as it interacts with the virtualisation layer to get some idea of what's going on in there.",Bayard Bell
19859,After executing a tutorial virtualbox is becoming super slow to run a Windows 10 instance,VirtualBox 6.1.10,2020-09-04T15:12:27Z,2020-09-04T15:12:27Z,2020-09-04T15:12:27Z,"I wanted to find out how to do this task : https://www.youtube.com/watch?v=6wVJUimaq2U

I executed it without trouble up until 08:40 ... which means that I didn't need to go to execute the following steps since VirtualBox recognized the UEFI drive and start the Windows from the boot manager.

Version : [https://pasteboard.co/JpxlUmV.png]

Running screenshot : [https://pasteboard.co/JpxldMc.png]

So the problem is VirtualBox is running at 40% CPU usage, I have enable UEFI and 16 GB RAM with 8 cores but it is hanging in the screenshot which I sent.

It seems that there is a bug.",vritual-boxer
16656,"after command init 6, generate core dump and duplicate UUID",VirtualBox 5.1.18,2017-04-15T19:51:50Z,2017-04-18T20:12:40Z,2017-04-18T20:12:40Z,"Hello,
unfortunately I answered yes to upgrade on Virtualbox 5.0.12 hang on create new disk, resolved on 5.1.19 and install it.
Virtualbox 5.1.19 corrupted 6 Guest Machine and install 5.1.51-114298

Now it is not present later, he returned to version 5.0.12 that worked well?
I honestly did not know if the problem is in virtualbox core or in the host machine, with win7.

the problems that I see right now are:
- Duplication of Guest UUID that worked and you can not run the start
- see attach: although, on this generated core dump I found something and I just solved will update

Regards, Massimo",maximilian
8147,Adding devices to virtual SCSI controller will use reserved port 7,VirtualBox 4.0.2,2011-01-22T15:21:28Z,2011-01-22T15:26:00Z,2011-01-22T15:26:00Z,"Hi! Fantastic work on VBox, thank you so much! I think the V4 is better than VMware :)

If this guy is right - http://forums.virtualbox.org/viewtopic.php?f=1&t=38319&start=0 - i.e. that the SCSI port 7 is reserved for the host adapter ID (or something more accurate, not a SCSI-savvy guy myself), then there's a bug in the interface when adding devices to the virtual SCSI controller. It will automatically assign the new device to port 7 when ports 0 thru 6 are already occupied, and you end up with missing devices in your OS (at least in my Ubuntu OS ;)",Daniel Smedegaard Buus
16622,Adding an SSD on 2-HD system can confuse drive assignments,VirtualBox 5.1.18,2017-03-29T18:55:10Z,2017-03-31T15:00:41Z,2017-03-31T15:00:41Z,"Starting with a 2 HD Dell M6800, VB sees the drives as HD1 = sda & HD2 = sdb.

Adding a Samsung EVO 250GB SSD drive caused Linux to assign drives as:
 HD1 = sda, SSD = sdb & HD2 = sdc

My local Mageia Linux install repository resides on HD2p7. This physical source disk was originally defined in DIST[-pt].vmdk as sdb.  After the SSD was installed, VB could not see the installation files because HD2(sdb) was now at sdc.  

Simply editing DIST.vmdk to change the only occurrence of sdb to sdc resolved the problem.

Could this have been overcome by using UUID instead of sdX?
",Pierre Fortin
3061,Add Virtual Disk Tasks to Virtual Media Manager,VirtualBox 2.1.0,2009-01-16T14:24:45Z,2009-12-01T20:05:14Z,2009-12-01T20:05:14Z,"On a periodic basis one can save a fair deal of disk space on a host by running ""VBoxManage modifyvdi [SomeVDI] compact"".  I would suggest that this documented but currently CLI-only feature be added to the Virtual Media Manager portion of the VirtualBox GUI.  Being able to manually specify when to compact a .vdi file in the GUI would save a lot of hassle for less-CLI-savvy users.

To use such a feature one might:
Open VirtualBox
Open the Virtual Media Manager
Select a Virtual Disk Image
Click a ""Compact"" button in the toolbar

Integration of virtual disk image management into Guest Additions could suggest that the user ""Compact"" when the guest's reported disk usage is beneath some threshold of the actual disk usage of the .vdi file on the host.
To use such a feature in a Windows guest one might:
Install Guest Additions
Guest Additions could run ""dir"" or some similar command in the background to get Windows' current free disk space estimate
VirtualBox could compare Windows' reported free disk space to the space left on a virtual disk image (Maximum size - current .vdi file size)
If the free space number differ significantly (say 20%) VirtualBox could, from within the guest, prompt the user to run a ""Guest VDI Compaction Routine""
VirtualBox could run ""sdelete -c"" in the background on the guest, send a shutdown signal after sdelete finishes, and then compact the .vdi once the guest is shut down

This second approach would be much more OS-specific and may not work (or be necessary) with all operating systems and file systems.  It would, however, simplify things for former Windows users who most run Windows for a handful of programs which have no practical replacements on the host platform.",Ryan Stonecipher-Fisher
7694,Add SCSI device passthrough support,VirtualBox 3.2.10,2010-11-07T12:04:26Z,2010-11-07T14:25:44Z,2010-11-07T14:25:44Z,"Unable to register raw SCSI tape device (used for controlling wide format print / scan mode).

{{{
VBoxManage -nologo internalcommands createrawvmdk -filename scanner.vmdk -rawdisk /dev/st0
Error opening the raw disk '/dev/st0': VERR_DEV_IO_ERROR
The raw disk vmdk file was not created
}}}

Right now VmWare ALREADY supports this type of SCSI passthru (as with LPT passthru)",linuxrulez
11092,Add option to pass through guest trim/UNMAP by punching holes in VDI file to free host disk space,VirtualBox 4.2.0,2012-10-20T17:35:32Z,2019-05-14T10:21:11Z,2019-05-14T10:21:11Z,"With VirtualBox 4.2, one of the new features was ""Storage: implemented support for discarding unused image blocks through TRIM for SATA and IDE and UNMAP for SCSI when using VDI images""

If my thinking is correct, that means that for expanding VDI files, the guest OS tells VirtualBox (via trim/UNMAP) which regions of the virtual disk can be erased. Then when the guest next writes new data, VirtualBox knows it can re-use those regions of the VDI which were marked as freed-up, instead of increasing the size of the VDI file.

The benefit of that is, the rate of expansion of VDI files is reduced. There is another related feature which would be very useful.

Windows and recent Linux kernels support ""punching holes"" in files. Unused regions of the file can be made into holes, so the file becomes sparse. The new hole regions read back as all-zero. You can think of hole-punching as analogous to trim/UNMAP, but for files.

It would be great if an option could be added to pass through trim/UNMAP requests from the guest, so that VirtualBox punches holes in the VDI file. Benefits of that:
 - When files are deleted in the guest, the VDI file would occupy less disk space on the host. Very useful if you're tight on disk space. The amount of space occupied by the VDI file would be roughly equal to the amount of space actually used in the guest. E.g. 100GB VDI, guest has used 50GB of that -> VDI occupies ~50GB on host, even though the apparent VDI file size may be larger. (Expanding VDI apparent file size will correspond approximately to the high water mark of disk usage in the guest.)

 - VDI would always occupy the minimum amount of space on the host drive, without needing to do VBoxManage modifyhd --compact manually.

 - If the user has a fixed-size VDI file but needs more disk space on the host, they could enable hole punching and thus free up approximately the amount of free space in the VDI, on the host drive.
",Donuts
20288,absurd delay to start virtualization,VirtualBox 6.1.18,2021-04-04T13:41:19Z,2021-04-04T13:41:19Z,2021-04-04T13:41:19Z,"I tried in many ways to correct this, I installed medications (Oracle_VM_VirtualBox_Extension_Pack-6.1.18)

and also a distribution pack that I use (virtualbox-6.1_6.1.18-142142_Debian_buster_amd64 (1) .deb)

And so far nothing, I use the Linux of the offensive security (https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/#1572305786534-030ce714-cc3b) image ready.


I start the machine and leave the computer on, and it went 28 hours without leaving the black screen with the kali logo
",anjo gelado
17562,[Feature Request] Treat virtual USB hard disk as removable,VirtualBox 5.2.6,2018-02-23T13:04:21Z,2018-02-28T08:42:49Z,2018-02-28T08:42:49Z,"Hello,

when adding a virtual hard disk drive via an USB storage controller, at least Windows will treat the connected drive as an ""USB Mass Storage"" device but in **fixed**-layout.

Also, when checking the ""Hot-plug""-feature of the hard disk, the Drive will be treated as fixed-disk.

My expectation was, that when checking ""Hot-Plug"" it would be a removable one.

Would it be possible to optionally set the ""Removable-Bit"" in the USB-Drive's properties, so that it is marked as ""removeable"" ?

Would be great, as some applications check drives for this.

Thank you and kind regards,
Wolfgang",Wolfgang Andreas
20469,6.1.24 Memory can't be written,VirtualBox 6.1.24,2021-07-22T12:00:47Z,2021-07-22T12:00:47Z,2021-07-22T12:00:47Z,"Windows 11 guest restarted after update normally.[[BR]]

Bootmgr messaged about HDD corruption and couldn't proceed. I closed guest window and it showed message from VirtualBox that memory can't be written.

The error appeared once only and I couldn't reproduce it again.",MikhailRokhin
8974,--bootable=off doesn't apply to IDE controller,VirtualBox 4.0.8,2011-05-26T20:27:00Z,2011-05-26T20:27:00Z,2011-05-26T20:27:00Z,"In deciding what's Hard Disk 0, the controller order is internal. IDE controllers are first in that order, and they can't be excluded, unlike every other type of controller. I don't know that the use case for this is tremendous, so it might be sufficient simply to document it. I was trying to use it in benchmarking to determine the performance difference between SATA and IDE, particularly because some recent bugs have had people suggesting that one ought at least try it. Solaris in particular has problems dealing with changes to the path to its boot device (grub will find the rpool and bootfs, but boot subsequently breaks because other config files store the path to the device), so things break if I've previously installed with a SATA boot VDI but want to try a benchmark with data stored on an IDE data VDI.

I already discussed the particulars on this one with MichalN on #vbox.",Bayard Bell
