VirtualBox

Ticket #7415 (reopened defect)

Opened 4 years ago

Last modified 3 years ago

VB does not support LBA-64

Reported by: knguyen Owned by:
Priority: major Component: other
Version: VirtualBox 3.2.8 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

Host = Fedora Core 64bit Guest = Windows Server 2003 64bit

Host has a disk-array configured in raid6 mode, using LBA64 to hold 40TB, /dev/sdb Use VBoxManage to create vmdk file that linked to /dev/sdb Register vmdk file to windows-VM

First-boot: OK. Windows VM was able to 'see' the new disk , disk1, in diskmgmt.msc. Perform conversion to GPT disk to fully use 40TB..

Second-boot: FAILED. Windows VM cannot be booted. VB log file show this: 0:00:02.857 Guest Log: BIOS: CDROM boot failure code : 0003 00:00:02.857 Guest Log: BIOS: Boot from CD-ROM failed 00:00:02.860 Guest Log: BIOS: Booting from Hard Disk... 00:00:03.094 Guest Log: BIOS: int13_harddisk: function 15, unmapped device for ELDL=82 00:00:03.157 Guest Log: int13_harddisk: function 42. Can't use 64bits lba

forum discussion:  http://forums.virtualbox.org/viewtopic.php?f=7&t=34131&p=152869#p152869

Change History

comment:1 Changed 3 years ago by TrenShadow

Same issue here.

Host = Solaris Express 11 64bit Guest = Windows Server 2003 32bit (Windows Home Server)

Host has 4TB zpool with a zfs block device volume created on top of it, then converted to raw vmdk. Guest has 200GB vdi mounted as SATA 0 as boot drive, and this 4TB vmdk mounted as SAS 0.

Booting guest and manipulating the 4TB drive as a MBR type partition table (limited to 2TB) works fine. When I convert to GPT and reboot (even manually selecting the 200GB SATA as boot drive) it fails to boot with error:

00:00:10.007 Guest Log: BIOS: Booting from Hard Disk... 00:00:10.258 Guest Log: BIOS: int13_harddisk: function 15, unmapped device for ELDL=82 00:00:10.419 Guest Log: int13_harddisk: function 42. Can't use 64bits lba

comment:2 Changed 3 years ago by klaus

  • Status changed from new to closed
  • Resolution set to invalid

Booting off a MBR formatted disk bigger than 2T doesn't work. MBR partitioning doesn't support more than 2T, so you're asking for something which is impossible. See the problems with the 3T hard disks which just came out. Ask Microsoft if you don't believe what I'm saying. They support GPT only for non-boot drives in systems using a traditional BIOS. Any OS which uses the BIOS to access such big disks is severely broken.

EFI would in principle support booting off a disk partitioned with GPT, however this isn't a supported config at the moment for anything but MacOSX.

comment:3 Changed 3 years ago by JurgenD

  • Status changed from closed to reopened
  • Resolution invalid deleted

I do reopen this ticket because the devteam did not read pretty well the ticket.

I do have the same problem with FreeBSD 8 and pure GPT partitioning. There is no MBR in such case at all. The GPT comes in to solve the 2T limit, as the 4 primary partition limits. The previous poster did mention, he started with MBR, but converted his disk to GPT.

I did test this with a image from a real system. The image does run perfectly on other hypervisors, but Virtualbox fails with the error.

It seems virtualbox fails in FreeBSD x64 to use a GPT format with the error:

FATAL: int13_harddisk: function 42. Can't use 64 bits lba

comment:4 Changed 3 years ago by peetaur

I have the same problem, but my boot disk is not large; it is only 256 MB, with a GPT label.

I was able to boot with 2 256 GB disks and 5 3TB virtual disks attached, but after adding the ZFS file system to the larger disks (which I assume must be setting up a 64 bit LBA), the next boot failed. The large disks actually seemed to work perfectly fine before the reboot, since the OS was handling it rather than VirtualBox. VirtualBox shouldn't need to read my 3TB disks at all. (FYI: The small root system is also ZFS, and booted properly before adding more disks)

Certainly you could add a simple feature, to just let us boot off of the supported small disk we select, forgetting about whatever errors/lack of support there might be on/for the other disks.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use