VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2473 - 2475 of 16363)

Ticket Resolution Summary Owner Reporter
#13677 fixed 4.3.20 VMs fail to start after today's Windows update KB3004394 [BUGGY UPDATE; RECALLED BY MICROSOFT] MaxR
Description

I am using Windows 7 64-bit Ultimate and use VirtualBox 4.3.20 r96997. After today's Windows updates VirtualBox fails to start any VM (I tried Windows, Linux, FreeBSD).

The GUI presents the following error: Errorcode: E_FAIL (0x80004005) Component: Machine Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

The VM startup logs all show an error with crypt32.dll. I am attaching three logs.

Please help resolve this problem, it is the second time (after 4.3.14) that Windows breaks VirtualBox, or the other way around. Thanks.

#9904 obsolete Panic on FreeBSD (initiate_write_inodeblock_ufs2) Max Savenkov
Description

I'm using VirtualBox to run FreeBSD 7.2-RELEASE. From time to time, I get panic with the following message:

"panic initiate_write_inodeblock_ufs2 already started"

I gather that it is related to problems with disk access. This VM use a single VDI virtual drive and nothing else. The same host machine is also running 3 other VirtualBox machines, one FreeBSD and two WinXP, all using different vdi drives, located on the same physical drive. May this be a problem? I also sometimes see one of my WinXP VMs BSOD, but not the other.

This problem persisted through all releases of Virtual Box I tried, from 3.x to 4.1.6.

Configuration: Hardware: CPU: Intel Core i5 760 RAM: 8Gb

Software: Host OS: Windows 7 64-Bit Professional, VirtualBox 4.1.16 Bridged LAN Guests: 2xFreeBSD 7.2-RELEASE (32bit), 2xWindows XP SP2 (32bit)

Detailed VM config and VBox.log are attached.

#6936 fixed High CPU consumption for multi-processor Windows guests Max Zinal
Description

Our install is:

  • 8-core 2-processor x86-based server with Xeon E5335 CPUs, 32 Gbytes of RAM.
  • Debian/GNU Linux 5 (Lenny) as a host system
  • Windows XP Pro SP3 as a guest system

We tried the following VirtualBox releases, with the same results: 3.1.8, 3.2.2, 3.2.4

We get high CPU consumption on host (up to 80-120%, measured by top) even when our guest system is idle. The effect goes away when we switch the system to a single CPU and turn off IO APIC (and move to single-processor kernel, of course).

We do not see same effect with exactly the same virtual machine on a notebook with Intel Core i7 processor, running Windows 7. So this problem might be processor- or even operating system-specific.

One of the interesting side-effects is that even when CPU usage on guest is near maximum (we use 4-core guest. and all cores are pretty busy at boot time), the CPU usage on host is about 170-180%.

The whole problem makes it pretty hard to use VirtualBox on that server, so we are abandoning our plans to buy VBox license for that host (at least until we can find a workaround).

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