VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1543 - 1545 of 16363)

Ticket Resolution Summary Owner Reporter
#2737 fixed iSCSI doesn't obey maximum transmit/receive values from target Glenn Matthys
Description

Hello

While testing with iscsitarget (http://iscsitarget.sourceforge.net/) I found that VirtualBox doesn't seem to obey the target's maximum segment lengths. It causes the iscsi_trgt to flood the kernel's buffer with error messages and very low performance.

Here is the original thread at the iscsi-target development mailinglist: http://sourceforge.net/mailarchive/forum.php?thread_name=493CED43.4080307%40pandora.be&forum_name=iscsitarget-devel

The default segment lengths are 8192. If I manually set these to 65536 on the target, the problem is solved.

#2739 fixed Fedora 10 (usually) panics on VBox 2.0.6 (under WinXP) - intermittent bug Rob
Description

Fedora 10 usually (but not always) panics and will not boot when installed on VirtualBox 2.0.6 (running under WinXP), this is an intermittent bug. Usually it fails, rarely it works.

I have searched this website for other Tickets and the Forums for similar issues. I found none that were "identical". I searched the Internet and found a few other people had "similar" troubles.

I downloaded http://fedora.mirror.iweb.ca/releases/10/Fedora/i386/iso/Fedora-10-i386-DVD.iso from http://fedora.mirror.iweb.ca/releases/10/Fedora/i386/iso/ .

I have installed F10 previously (and had everything working well) by following these tips:

Problem with Fedora 10 on VirtualBox http://www.my-guides.net/en/component/option,com_smf/Itemid,46/topic,94.msg142/topicseen,1/

Plymouth Graphical Boot http://www.my-guides.net/en/content/view/125/26/1/12/#plymouth

Other people have "similar" but not "identical" complaints:

kernel panic when trying to boot Fedora 10 live in VirtualBox http://linux.derkeiler.com/Mailing-Lists/Fedora/2008-09/msg02296.html

Fedora 10 fails to install http://www.virtualbox.org/ticket/2680

The Bug in this report is shown in the attached screenshot. The message is: "Kernel panic - not syncing: Fatal exception in interrupt" .

_Sometimes_ when there is a problem booting I see a 'Debug Trace' then keeps scrolling on the screen and does not terminate with a message (at least not within 20 minutes), it just keeps 'tracing' and does not print the "Kernel panic" message.

_Sometimes_ Fedora 10 will start normally and work properly.

_Sometimes_ Fedora 10 will get as far as the "Graphical Bootscreen" completion but will not start X11 and the Gnome Desktop.

I can (_sometimes_) fix this Bug by toggling the "Extended Features" "Enable ACPI" to ON, booting and it will work (or fail), and then turning it OFF, booting and it will work (or fail).

I find that leaving the "Extended Features" "Enable ACPI" turned OFF is necessary for Installation. I only turn it ON, then OFF, to 'toggle it' and attempt to cause Fedora 10 to 'fix itself' and boot.

Fedora 10 _seems_ to be able to boot correctly, more often, if the "Initial Updates" are NOT downloaded (there is a popup prompting you to update _after_ you install from the DVD .iso) and once they are downloaded the _chance_ that it will boot is greatly reduced.

_Prior_ to downloading and installing the "Initial Updates" you need to leave the "Enable ACPI" turned OFF all the time or you will get the endless error messages (and rarely they will end with the "Kernel panic" message).

Thanks, Rob

#2743 fixed Guru meditation (guest heap problem) following startup of guest and login Tomasz Konefal
Description

Vista guest crashed after login to the OS on guest. I had unplugged a USB device earlier on in the bootup sequence. Not sure if it's related.

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