Ticket #17828 (new defect)

Opened 3 years ago

Last modified 10 months ago

Can't move media due to out of memory errors

Reported by: morungos Owned by:
Component: other Version: VirtualBox 5.2.12
Keywords: Cc:
Guest type: other Host type: other


I'm attempting to move media using the Virtual Media Manager, and getting VERR_NO_MEMORY messages, even when I have a good few gigabytes of RAM free, and no VMs running.

Seems to happen to some (not all) snapshots, so now I have them sprinkled across two different drives.

Full messages:

Could not move medium 'D:/IE11 - Win7/{f4e5739c-1ee9-4b9b-8872-a68e8816f364}.vmdk' (VERR_NO_MEMORY).

Result Code: VBOX_E_FILE_ERROR (0x80BB0004)

Component: MediumWrap

Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}

Change History

comment:1 Changed 3 years ago by socratis

It's usually better and faster, if issues get first addressed in the  VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.

Please open a new thread in the  Using VirtualBox section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

comment:2 Changed 3 years ago by VVP

Would you provide more information for investigation? VM settings, start conditions, sequence of your steps, end conditions, log files... Maybe it's kind of some corner case i can't say at moment because moving via the Virtual Media Manager works for me.

comment:3 Changed 10 months ago by timwood0

I'd like to co-sign this ticket. I have VBox 6.1.2, a base .vmdk on a Passport drive, with a .vmdk in the Snapshots directory on the faster main drive shadowing it, where (nearly) all the changed blocks reside. However the VM entry only shows a Current State, no snapshot files. The Virt. Media Mgr. shows the parent-child relationship between the base vmdk and the vmdk on the main drive.

I would like to move the base vmdk off the Passport onto the main drive, but I get the error the OP observed. I can create a new snapshot off the base vmdk, but I cannot move it, nor consolidate the two vmdks into one on the main drive.

One theory: The virtual size of the base vmdk is 477+GB; it only occupies 23GB. I have 12+GB free RAM. Yet there is "only" about 445GB free on the main drive. Could the VMM be making the silly mistake of rejecting the move because the *virtual* size of the media to move is greater than the free space on the destination?

Per the suggestion, I searched the forums for different forms of this topic, including the error code. No dice.  Forum posting.

Last edited 10 months ago by timwood0 (previous) (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use