VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2500 - 2502 of 16363)

Ticket Resolution Summary Owner Reporter
#15601 fixed VBoxManage creates corrupted VHD with fixed size => fixed in SVN/5.1.x schrotti12
Description

The following command is used to create a VHD Images for hosts:

VBoxManage createmedium disk --filename "%USERPROFILE%\MyVdisks\disk1.vhd" --size 8192 --format vhd --variant fixed

The VHD file is corrupted as shown in the following diskpart output:

C:\Windows\system32>diskpart
Microsoft DiskPart version 10.0.10586
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: S10
DISKPART> select vdisk file="C:\<actual path to vdisk>\disk1.vhd"
DiskPart has encountered an error: The file or directory is corrupted and unreadable.
See the System Event Log for more information.
There is no virtual disk selected.

Also if it is included into VirtualBox via GUI there are errors:

Could not get the storage format of the medium 'C:\<path to vdisks>\disk1.vhd' (VERR_NOT_SUPPORTED).
Result Code:
VBOX_E_IPRT_ERROR (0x80BB0005)
Component:
MediumWrap
Interface:
IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}
Callee:
IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
Callee RC:
VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

If added via command line the VirtualBox Manager shows disk as dynamicaly resizeable instead of fixed size. Screenshots can be added if required.

#5199 fixed VBox Crashes on Ubuntu 9.10 when trying to boot Windows XP Guest from Physical Partition. Adam R. Schobelock
Description

The machines starts, loads grub, I choose Windows XP, choose hardware profile then crashes.

#2911 duplicate bad reads on SATA disks schnittchen
Description

I had massive filesystem corruption for no apparent reason, so I investigated a bit. Apparently, reads on (guest, virtual) SATA disks can produce wrong data.

My setups were linux (Ubuntu 8.04 and 8.10) guest and host (all combinations). In order to locate the problem, I attached a vmdk disk image with prepared data so that I could tell from the read data at which blocks something had gone wrong. The image came in two variations:

  • an "entire disk access" vmdk pointing to an entire mapper device
  • a modified version pointing to a file, created by editing the vmdk by hand.

The problem appeared in both situations.

This is a "heisenbug", I have read many megabytes of intact data and could not reproduce the symptom until it finally hit again. It seems to appear more often when a large number of blocks is read (I did the read using dd inside the guest, so I played with the block size parameter). It seems to be very well reproducable within 150 MBytes (my prepared disk was 25MB).

There is no such problem with IDE. After detaching the vmdk and reattaching on an IDE slot it disappeared, and reappeared when on SATA again.

I captured all badly read blocks in order to get a feeling for it. I looked at the first few kilobytes and found not a single sector from the prepared disk image! The data seems to come somewhere out of RAM, or from the other attached (IDE) disk of the guest. I have seen symbols, format strings and even directory nodes.

uname of one of the host systems: Linux myhost 2.6.24-23-generic #1 SMP Thu Nov 27 18:44:42 UTC 2008 i686 GNU/Linux

The guest is almost the same. vbox version is 2.1.0

I hope this is enough information to reproduce and locate the problem.

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

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