Custom Query (16363 matches)
Results (172 - 174 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12345 | fixed | OVF 0.9 import fails => Fixed in SVN | ||
| Description |
Tried importing icinga image: Error Message:
Failed to import appliance C:\...\virtualbox-icinga-1.8.1-0.3-demo-centos6.ova.
Error reading "C:\...\virtualbox-icinga-1.8.1-0.3-demo-centos6.ova": element "Section" has no "type" attribute, line 18.
Result Code: VBOX_E_FILE_ERROR (0x80BB0004)
Component: Appliance
Interface: IAppliance {3059cf9e-25c7-4f0b-9fa5-3c42e441670b}
|
|||
| #8420 | fixed | Random lockups on linux guest | ||
| Description |
I have Virtualbox 4.0.2 running on Linux (Debian, 2.6.35-trunk-amd64). There are several virtual machines (~20) running but only a few seem to exhibit random lockups. When that happens the guest becomes completely unresponsive (no ping, vrde screen is empty and unresponsive) and on host side guest consumes 100% CPU. I've tried different guest kernels (2.6.32, .35, .37) but it always locks up eventually. Additionally the lockup is rather random but seems to occur daily (on one guest, on others maybe weekly). The difference between working and nonworking guests might be 64-bit kernel (not working) and 32-bit. Also the failing guests run weblogic app server whereas working servers run glassfish. Everything worked fine on Virtualbox 3.2.x. Attached is log of about three lockups (+reboots) and shutdown on final lockup. I also have guest and VBox coredumps if somebody wants to take a look. |
|||
| #2876 | fixed | PXE ("real") fails with virtual Intel adapters | ||
| Description |
Version 2.1.0 hosted on Windows XP (SP3) can do a PXE boot using the host interface ("bridged") with both AMD adapters. Changing to either one of the Intels results in a "No DHCP or ProxyDHCP offers were received." error followed by a "No bootable medium found! System halted." message. It looks like "real" DHCP/PXE is broken on the virtual Intel adpters. |
|||

