Custom Query (16363 matches)
Results (562 - 564 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3914 | fixed | vbox 2.2.2: Bridged Networking using crossbow vnics on 5.11 snv_110 host and various guest systems unstable | ||
| Description |
After booting the host system you will be able to set up bridged networking over VNICs (crossbow vnics, as documented). For a short limited time you will be able to reach all configured addresses from host to guests and vice versa, as well as from guest to guest. Starting a round robin ping to all configured addresses however, after a certain time you will experience some of the configured NICs are not answering anymore. If the guest(s) are rebooted, no connection will be possible anymore, which means that Vbox does not reinitialise it's host driver(s) correctly, even if all guests were stopped and restartet. Rebooting the host will of course temporarily solve the problem. rem_drv and add_drv for vboxflt does NOT help. To test this behaviour I have 4 vnics created for each of 2 guests and 4 vnics for the host. and I put all vnics into the same network 10.0.0.0 (255.0.0.0). All vnics must be plumbed in the host first and configured with IPs different from the guests. I tested this behaviour positively with Linux and Solaris guests (both 32 and 64 bit), but as it's behaving like a host driver problem, this should hold true for all possible guests. |
|||
| #2290 | fixed | vbox 2.0.2 unable to create 64-bit guest on opensuse 11 x64 => Upgrade ASUS BIOS | ||
| Description |
upgraded to vbox 2.02 on opensuse 11 x64 host. unable to create 64-bit guest vms, vbox sees my proc only as i586. proc is virt-capable amd phenom 8450 3-core & bios has amd-v enabled. here is a sample vbox guest settings list: General Name Ubuntu-8.04.1-LTS-x64 OS Type Ubuntu Base Memory 1024 MB Video Memory 128 MB Boot Order CD/DVD-ROM, Hard Disk ACPI Enabled IO APIC Enabled VT-x/AMD-V Enabled PAE/NX Enabled Hard Disks IDE Primary Master Enterprise Linux.vdi [Normal, 10.00 GB] CD/DVD-ROM Host Drive ASUS DRW-1814BL (/dev/sr0) Floppy Not mounted Audio Host Driver PulseAudio Controller ICH AC97 Network Adapter 1 Intel PRO/1000 MT Desktop (NAT) Adapter 2 Intel PRO/1000 MT Desktop (NAT) Serial Ports Port 1 COM1, Disconnected USB Device Filters 0 (0 active) Shared Folders 2 Remote Display Disabled have tried to install following guests on opensuse 11 x64 with vbox 2.0.2: linux 64: ubuntu hardy, rpath foresight, debian lenny, sles 10 unix 64: solaris 10, freebsd 7, nexenta b86 solaris installs 32-bit by default and rest say they need a 64-bit cpu but find only a i586 under vbox. all above install individually without problems on physical partitions on same m/c, but then i will have a multiboot m/c rather then concurrent vms on one host... doesn't serve my purpose... have also tried same vbox2.0.2 binary on ubuntu hardy x64, same prob there with vbox, so it seems to be a vbox bug thingie... have even uninstalled vbox binary entirely and recompiled afresh from source, but problem persists... cs |
|||
| #1527 | wontfix | vbox 1.6.0 fails on OpenSolaris build snv_89 | ||
| Description |
I had vbox 1.6.0 running quite nicely on OpenSolaris build snv_83, then I upgraded last night to build snv_89. VBox now fails to start any of my guests, giving the message The VirtualBox support driver which is running is from a different version of VirtualBox. You can correct this by stopping all running instances of VirtualBox and reinstalling the software.. VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH). Result Code: 0x80004005 Component: Console Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} |
|||

