Custom Query (16363 matches)
Results (2392 - 2394 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4402 | fixed | Problems with SNMP in VBox3.0/NAT -> fixed in svn. | ||
| Description |
I've posted about the issues I've observed in the upgrade from 2.2.4 to 3.0.0 here: http://forums.virtualbox.org/viewtopic.php?f=8&t=19450 Basically, Cisco Fabric Manager fails to operate correctly with VT-x/AMD-V enabled in 3.0.0, and Cisco Device Manager fails to operate with either setting in 3.0.0. However, when I say "fails to operate", I mean there are issues with either the networking or display of information relating to fabric switches on our network. Reverting to 2.2.4 corrects both issues. I've attached vbox.log for runs of both 2.2.4 and 3.0.0 in case that helps, and I can gather additional information if needed (like packet sniffs using vboxmanage or whatever). |
|||
| #4403 | fixed | crash in VB 3.0.0: VBoxREM.so | ||
| Description |
VB 3.0.0, both host and guest are Ubuntu 9.04 64-bit. After several hours of use, my guest window crashes. Complete crash, where the window disappears and nothing about the crash is logged to VBox.log. In the host, the following is logged to dmesg: [286059.813502] VirtualBox[1000]: segfault at 0 ip 00007ffc0b8089f0 sp 00007ffc0b262d70 error 4 in VBoxREM.so[7ffc0b7f6000+7a000] |
|||
| #4404 | fixed | Guest fails to boot about 75% of the time | ||
| Description |
VB3.0.0, host and guest are both Ubuntu 9.04 64-bit. About 75% of the time, when I attempt to boot the guest, the guest's boot process is interrupted before the GNOME desktop comes up. This only started happening once I upgraded to VB 3.0.0. My linux guest then sits at a command-line window, with text such as: [ 137.991145] end_request: I/O error, dev sda, sector 2414097 init: Unable to execute "/sbin/getty" for tty1: Input/output error init: tty1 main process (1371) terminated with status 255 init: tty1 main process ended, respawning init: tty1 respawning too fast, stopped If I click on Machine->Reset, the guest window freezes for about 30 seconds and VirtualBox pops up a window with the following text: "The IDE async I/O thread remained busy after a reset, usually a host filesystem performance problem. ERROR ID: DevATA_ASYNCBUSY Severity: Warning" If I power off the guest, then eventually I can get the guest to start correctly. Note that this guest uses ext4 (in case that makes a difference). |
|||

