VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (862 - 864 of 16363)

Ticket Resolution Summary Owner Reporter
#9614 fixed Freeze (one of two VMs) when resuming from saved state with Multi-attach and Immutable OS disk VirtualBoxBug
Description

Obviously this is a critical first-priority error. Try it yourselves and comment if you don't have this problem and what am I doing wrong?

I created two VMs. I attached an OS disk to them as immutable, and a data disk as writethrough. I took snapshots of them before starting so they would retain changes (autoreset off is another option). I started one, played video in VLC player, saved, resumed, no problems. I started another one, played video, saved them both. When I resumed, the second one froze with corrupted display. It didn't crash so the log doesn't have. The first one resumed ok. I tried changing the OS disk to Multi-attach. The same results.

I went back as far as 2.2.4 and it had the same bug.

#9615 fixed All VDIs lost (not physically): create and delete snapshot after creating VM, restart VirtualBox VirtualBoxBug
Description

I create a VM. OS disk is Multi-attach. (Immutable freezes when resuming.) Data disk is Writethrough. I take a snapshot using the UI of the VM while it's powered off in order to create a differencing disk. I delete the snapshot to get rid of the differencing disk but it still leaves a differencing disk, because it's Multi-attach . This is what I wanted. I don't know how to get it otherwise. I restart VirtualBox.

I see this on the VM:

A differencing image of snapshot {e533c43c-588b-4447-a42e-184097602f56} could not be found. Could not find an open hard disk with UUID {b7de1b6d-ddd7-4367-86a5-2d1391a1c910}. Result Code: E_FAIL (0x80004005) Component: SnapshotMachine Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

I took the snapshots using VBoxManage with the same results.

All disks have disappeared from Virtual Media Manager.

Please test creating, configuring, starting, stopping, deleting multiple VMs only with VboxManage you'll run into BSODs. They weren't there before 4.x.

Don't take this wrong, I'm just wondering - justifiably, I think: This is 4.x? Really? NO version 4 has this many simple and critical bugs. Do you test these things at all? Does anyone use this actually? I'm feeling like I'm alpha testing some 0.1 version. I hope you can fix all these bugs I've reported immediately, because they are true show-stoppers - I can't use your product while they're there.

#9618 fixed Power Off with Restore Snapshot: All VDIs lost (not physically) VirtualBoxBug
Description

I created three VMs with an OS and a data disk. I attached them all to a single OS disk that is type Normal. The Data disks are Writethrough. I took a snapshot of each of them before powering them off. I took another snapshot of one of them after configuring it. I used it and then hit Ctrl+Q and chose Power off the Machine with Restore current snapshot. The VM became inaccessible with

Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) Component: VirtualBox Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

in Virtual Media Manager there were no disks and all VMs got stuck.

I restarted VirtualBox and Virtual Media Manager shows everything, but the VM remains inaccessible.

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