Custom Query (16363 matches)
Results (1063 - 1065 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3920 | fixed | The emulated SATA controller should report its port(s) as non-hot-pluggable, or make it user-configurable for each port => fixed in svn | ||
| Description |
I'm using a Windows Fundamentals for Legacy PCs (WinFLP) guest (which is a slightly cut-down version of Windows XP). I installed the Intel AHCI driver version 8.8.1009 and configured the emulated hard disk to be connected to the SATA controller. Everything works okay. However, a "Safely Remove Hardware" icon is now in the system tray. It is of course not possible to remove the emulated hard disk. Is it possible to have the emulated SATA controller report attached hard drives as non-removable/hot-pluggable? Then the useless system tray icon should not appear. Or better, make the behaviour user-configurable for each SATA port. Perhaps in future VirtualBox can support hot-plugging disk images on the guest SATA controller? |
|||
| #5554 | obsolete | Guru meditation on booting Damn Small Linux via PXE/boot.kernel.org | ||
| Description |
Hi. I downloaded a boot floppy image from http://boot.kernel.org/gpxe_images/gpxe.dsk After extending the image file size to 1.44MB, I created a VM to test that in. Booting over the internet worked and once the initial menu screen appeared I chose Live Images then DSL. Text on the screen is:
and then a Guru Meditation dialog box appears. The full log is attached but the relevant part seems to be: 00:03:08.545 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'. 00:03:21.366 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={0a51994b-cbc6-4686-94eb-d4e4023280e2} aComponent={Console} aText={Invalid machine state 6 when checking if the guest entered the ACPI mode)} aWarning=false, preserve=false |
|||
| #5629 | fixed | Suggestion: Add option to have emulated hard disk report itself as an SSD, and support TRIM | ||
| Description |
Add an option to have VirtualBox report the emulated hard disk as an SSD to the guest OS. (For ATA drives, word 217 of IDENTIFY DEVICE should be 1.) Also support TRIM (for ATA, the DATA SET MANAGEMENT command with TRIM bit set). That would allow an SSD-aware guest to tell VirtualBox which sectors it no longer needs. Then VirtualBox could reuse those sectors in the VDI file when "new" sectors are written to. In other words, that would reduce the rate of growth of dynamically-expanding VDI files. (Reading back TRIMed sectors should return all 0 bytes.) So SSD-aware guest OSes like Windows 7 would behave optimally, e.g. by not defragmenting/optimising the disk in the background. Even when the host VDI file is on a normal hard disk, that is a good idea. For dynamically-expanding VDI files, defragmenting/optimising disk layout by the guest has no beneficial effect, and causes VDI file size to increase unnecessarily. And any I/O scheduler behaviour in the guest to minimise seeks could be disabled. More generally, it would be great if the user could specify certain properties of any emulated hard disk. Apart from reporting as an SSD, allow the user to set the logical and physical block sizes, and logical sector offset. See for example http://mkp.net/pubs/storage-topology.pdf and other documents at http://mkp.net/computing.html That would be invaluable for testing purposes (not many people have real 4KB-sector drives to test with), but also has real-world uses. If the VDI file is on a drive with 4KB sectors, allowing the guest OS to know that would improve performance. More generally, it would make moving to and from physical media with non-512-byte sectors easy. (For example, DVD-RAM has 2048-byte logical sectors, 32768-byte physical. Some MO disks have 1024-, 2048- or 4096-byte sectors. Plasmon UDO disks have 8192-byte sectors.) |
|||

