Custom Query (16363 matches)
Results (1357 - 1359 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1256 | fixed | Linux Guest loses networking under heavy load | ||
| Description |
I have host Mandriva 2007.1 and guest Mandriva 2008.0. I'm using bridged networking in kind of advanced mode. I created private subnetwork for this guest and I'm doing SNAT for it. I can provide any details you may request, but It was working fine with previous versions of VirtualBox. After upgrading to VirtualBox 1.5.6 I'm experiencing an issue that the guest networking just stops working, and it usually happens when the heavier network load was generated to it (I have a web server on the guest and the network stops working on the guest when handling multiple connections) Stops working = the guest and host network devices are up, the tap device on the host is still connected to the br device, but connecting out and from the guest is impossible. Restarting the networking on the guest does not help. Restarting the whole guest by invoking 'reboot' command does not help. Only one thing that helps is to stop the guest and cold-start it from VirtualBox. I tried both e1000 and pcnet32 driver. Is there any log I can enable / any experiment to do / any more info I can provide? |
|||
| #1257 | fixed | VBoxSDL segfaults during startup, slow ssh connections | ||
| Description |
Dear VirtualBox team. It seems, that somehow I'm attractive for segfaults. Anyway, here are the problem descriptions: Host: openSUSE-10.3 + all Patches, Athlon64 in 32-bit mode, kernel-default-2.6.22.9, glibc-2.6.1 Guest: WindowsXP SP2 + all patches, German, guest-additions-1.5.6 installed Binary: VirtualBox-1.5.6_28266_openSUSE103-1.i586.rpm SGID-vboxusers: VBoxSDL is started with SGID-vboxusers wrapper Problem-1: If I call VBoxSDL over an ssh-forwarded (-X and -Y tested) and rather slow TDSL-cable connection (2 MBit), it segfaults always:
I admit, that this is much to slow to work with. But I was just curious. If I call VBoxSDL from the same computer over a fast ssh-connection, I do not get any segfaults:
Core dumps and segfaults of three VBoxSDL calls: http://rapidshare.de/files/38689424/core.5098.during-startup-over-ssh.dat.bz2.html http://rapidshare.de/files/38689429/core.5098.during-startup-over-ssh.VBox.log.html http://rapidshare.de/files/38689434/core.5354.during-startup-over-ssh.dat.bz2.html http://rapidshare.de/files/38689437/core.5354.during-startup-over-ssh.VBox.log.html http://rapidshare.de/files/38689443/core.6749.during-startup-over-ssh-Y.dat.bz2.html http://rapidshare.de/files/38689447/core.6749.during-startup-over-ssh-Y.VBox.log.html Problem-2: I had once and only once a direct VBoxSDL core dump, e.g. started without ssh from a terminal window. Here is the core-dump (unfortunately without log): http://rapidshare.de/files/38689515/core.9483.bz2.html Maybe the problems are connected. Many thanks for your help and your good work. Best regards |
|||
| #1258 | obsolete | Failure to install FreeBSD 7.0RC2 | ||
| Description |
VirtualBox-osx-1.5.51-r27946-beta3 on Mac OS X 10.4.11 fails to install FreeBSD 7.0RC2 while copying files from CD to the virtual Harddrive (no matter if the virtual HD is of growing or fixed size type). I used ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/7.0/7.0-RELEASE-i386-disc1.iso, checked the MD5 sums (correct) and configured VirtualBox to use that ISO image as CD-Rom for a OS type FreeBSD VM After booting the VM I choose the following options: Screen: Option choosen: ====================================================================== Welcome to FreeBSD: Boot FreeBSD [default] Country Selection: Germany System Console Keymap: German ISO FreeBSD/i386 7.0 RC2 sysinstall Main menu: Standart partitioning scheme: All Install Boot Manager: Standart (no boot manager) create BSD partitions: Auto Defaults Choose Distribution: X-Developer Ports Collection: yes Choose installation Media: CD/DVD However, the install always crashes after a while, mostly when the virtual HD LED has been red for quite a long time. See attached screenshots |
|||

