VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1819 - 1821 of 16363)

Ticket Resolution Summary Owner Reporter
#2290 fixed vbox 2.0.2 unable to create 64-bit guest on opensuse 11 x64 => Upgrade ASUS BIOS suchindran
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

#16368 fixed VirtualBox Linux Guest: NVMe Controller With SPDK subbu_work
Description

Hi,

Some times back I have submitted the query in the forum, regarding the virtual NVMe Controller hang when we try with SPDK in Linux guest. Since people suggest to raise a bug hence I am filing the ticket. Below link has the detailed report about the bug.

https://forums.virtualbox.org/viewtopic.php?f=3&t=81059&p=381867&hilit=NVMe#p381867

Thanks & Regards, Subbu

#4201 fixed VBox 2.2.4 segfaults after heavy I/O => Fixed in 3.0 sub.mesa
Description

Also see this topic: http://forums.virtualbox.org/viewtopic.php?f=7&t=18462

I get regular segfaults when running VirtualBox 2.2.4 or 2.2.2 PUEL on Ubuntu 9.04 amd64, with guest OS FreeBSD 7-STABLE amd64. The dmesg shows:

[60327.316891] VirtualBox[21681]: segfault at 20 ip 00007f159fd66c32 sp 00007f1536ba5e10 error 4 in VBoxVMM.so[7f159fcbd000+12a000]

[164613.347935] VirtualBox[19352]: segfault at 20 ip 00007f5b68567c32 sp 00007f5afb112e10 error 4 in VBoxVMM.so[7f5b684be000+12a000]

The segfaults occur while performing heavy I/O on 8 raw disks attached via AHCI. The heavy I/O originates from a ZFS RAID-Z ("RAID5") configuration on those 8 disks, and performing a scrub on the volume, which is 100% disk bound and takes little over an hour to complete. But often the crash is triggered within the first run, between 30-50 minutes.

On the third try, i tried to run a backtrace and dump. Logs attached, but the dump is over 1.7GB. I could try reducing the memory to reduce the dumpsize, but ZFS likes to use lots of memory so this could be problematic. I've already tried 5-passes with Memtest86+ so memory corruption is not an issue here. I think these crashes are a defect of Virtualbox, and would like help to debug this thing.

Kind regards, sub

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