VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1786 - 1788 of 16363)

Ticket Resolution Summary Owner Reporter
#9414 obsolete Can't import appliance because of "OVF describes no such image" MarcelS
Description

I've created a Linux guest under Windows host (VBox 4.1.0), for configuration see MBD_Workstation.xml (in short: nothing special, just some snapshots). If I try to import on Linux Host I step over Bug #7941, but fail at:

00:06:28.590 Appliance::Task ERROR [COM]:
aRC=NS_ERROR_FAILURE (0x80004005) aIID={3059cf9e-25c7-4f0b-9fa5-3c42e441670b} aComponent={Appliance}
aText={<vbox:Machine> element in OVF contains a medium attachment for the disk image
f1acf25f-eb04-45ca-a5a8-d8f91be48370 but the OVF describes no such image}, preserve=false

For more Information see VBoxSVC.log. Any help would be greatly appreciated, I'm feeling odd about this problems at a simple Ex-/Import. If you need more details don't hesitate to ask.

#9421 obsolete VM inaccessibe after restore to snapshot Clipper87
Description

I have Virtualbox v 4.1.0 r73009 on Windows 7 64 bit with Systematically after I restore to a snapshot the VM becomes inaccessible, in the snapshot folder there appears a 2nd snapshot. After quitting Virtualbox & then relaunching Virtualbox the VM is normally accessible but the 2nd snapshot worries me. Never seen this with older versions.

#9424 obsolete Solaris SMP problems Kevin Corby
Description

Hello all,

I am running VirtualBox 4.1.0 on a Solaris 10 host with the latest set of patches. The guest OS is Redhat 5.1. The hardware is a sunfire x4600 server with 8 pairs of CPUs for a total of 16. Hardware virtualization is available, enabled, and exclusive as far as I can tell, and all of the relevant settings seem to be correct (I/O APIC is enabled, cpuexecutioncap = 100).

I want to allow the guest OS (Redhat) to use 8 CPUs. I am able to configure the VM that way, and inside the guest OS it clearly believes 8 CPUs are available, and if I run 8 CPU-bound processes they will spread across them. However, this runs very slowly. If I look on the Solaris host machine, I can see that only a max of 12% of the CPU is ever getting used by the virtualbox process that is running the VM, even during its peak. This corresponds to 2 out of the 16 CPUs. The VM seems to run in one single process in Solaris, but that process has 57 threads (LWPs in Solaris-speak).

If I look at the CPU usage across the 16 processors in Solaris, I find that all 16 are 70%+ idle, which makes me think that the VirtualBox load seems to be getting shared across all processors, but it's clear that even with many more active threads than two I can only ever get up to 12% usage at a time. When I look at the CPU load caused by each LWP I can see a number of them that are active but stuck around 1.2% of CPU usage because of contention with each other.

Is there a reason the VM is not using more than 12% of the total CPU, like some kind of Solaris-imposed cap? Is there a way to remedy this?

Thanks, Kevin

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