VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1888 - 1890 of 16363)

Ticket Resolution Summary Owner Reporter
#1931 obsolete Cannot boot Coherent from bootable floppy image Andrzej Popielewicz
Description

I am using Solaris 10 x86, (uname -a -> SunOS unknown 5.10 Generic_Patch_118844-30 i86pc i386 i86pc) and using latest VirtualBox 1.6.2. I am trying to boot Coherent 4.2.10 from bootable floppy image. Kernel is loaded but crashes due to error in mounting/opening root filesystem(floppy). The identical message was produced in qemu previous to 1.6.1. Since qemu 1.6.1 Coherent bootable floppy boots OK and one can install Coherent to hard disk image.I suspect that some io addresses are not mapped correctly by VirtualBox.The error message is produced by Coherent kernel executing inb/outb instructions. It means comparison what was made in qemu 1.6.1 could be useful. The bootable floppy image for Coherent can be created from 4 installer files in TUHS archive. This bug report was suugested by Sun employee in the OpenSolaris forum.

#1932 duplicate Cannot boot Coherent from bootable floppy image Andrzej Popielewicz
Description

I am using Solaris 10 x86, (uname -a -> SunOS unknown 5.10 Generic_Patch_118844-30 i86pc i386 i86pc) and using latest VirtualBox 1.6.2. I am trying to boot Coherent 4.2.10 from bootable floppy image. Kernel is loaded but crashes due to error in mounting/opening root filesystem(floppy). The identical message was produced in qemu previous to 1.6.1. Since qemu 1.6.1 Coherent bootable floppy boots OK and one can install Coherent to hard disk image.I suspect that some io addresses are not mapped correctly by VirtualBox.The error message is produced by Coherent kernel executing inb/outb instructions. It means comparison what was made in qemu 1.6.1 could be useful. The bootable floppy image for Coherent can be created from 4 installer files in TUHS archive. This bug report was suugested by Sun employee in the OpenSolaris forum.

#1933 fixed VirtualBox doesn't detect my AMD virtualization Stanislav Georgiev
Description

Tried to enable hardware assisted virtualization, needed for OS/2 guest installation. After enabling the option - both in global preferences and in VM settings I found that the machine won't boot. I saw for a moment OS/2 logo, then it disappeared and VM stucks with black sceren. I examined Runtime Attributes in Session Information and there VT-x/AMD-V was disabled. I know my cpu is supporting AMD-V - it's already working in Parallels Workstation. I tested AMD-V with tools like "Securable" and I can confirm, that hardware assisted virtualization is detected and working well. My CPU is AMD Athlon 64 X2 5000+ AM2 - 65nm, code name: Brisbane, revision: BH-G1. My motherboard is Gigabyte GA-MA69G-S3H, Bios revision F6 (latest), virtualization support is enabled in BIOS settings. Hardware virtualization is not working (or can't be enabled) in VirtualBox 1.5.2 - 1.6.4, tested on my machine for several months.

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