VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (958 - 960 of 16363)

Ticket Resolution Summary Owner Reporter
#5281 fixed running some Linux operatingsystems makes my computer to crash Vatten
Description

Ubuntu, openSUSE, Fedora and other linux os, makes my compuer to crash on (guest:Linux) logon. My primary operating system is Windows 64 bit, fully updated. My first crash was on Ubuntu 9.10 (beta). (I think it was "starting to dump pysical memmory")

#19090 worksforme running qemu-img in guest over a file on shared folder makes system unusable Roman Valov
Description

Steps to reproduce:

  1. Install centos-7 guest with latest updates and qemu-img utility
  2. Install VirtualBox guest additions as described here: https://wiki.centos.org/HowTos/Virtualization/VirtualBox/CentOSguest
  1. Setup a shared folder
  2. Copy VMDK file onto the shared folder
  3. Run following commands in guest:

$ cd /mnt/shared $ qemu-img info <vmdk-file>

Results:

qemu-img exited with errors and any further invocation of standard linux utilities such as ls results into Segmentation fault.

#13709 duplicate running on btrfs causes hang and unstartable instances with 4.3.20 and 4.3.18 krichter
Description

Running on btrfs (with 4.3.20 and 4.3.18 on Linux 3.18.1, 3.17.6, 3.17.4, 3.16.7, 3.16.0 on Ubuntu 14.10 amd64) causes hangs of VMs (experienced with Ubuntu 15.04-daily amd64, Fedora 21 x86_64 and Fedora 21 i386 guests) at some point which require the VM process to be killed. After this kill the instance is no longer startable. The "Starting VM" dialog with progress bar stagnates at 0 % and after ~1 minute a second "Starting VM" dialog is displayed which stagnates at 20 %. This state stays for > 1 hour while 20 MB/s is constantly read from disk (on a system which usually reads data between 5 and 120 MB/s). Moving VirtualBox VMs to an ext4 filesystem (on a file image mounted via a loop device residing on the same btrfs) avoids this behavior. After 1 hour I usually kill the VM process.

The root system is btrfs and the VirtualBox VMs folder (usually created in the home directory is symlinked to another btrfs partition). Find attached `VBox.log of a hanging start on btrfs and a successful start on ext4 file image of the very same instance of Fedora 21 i386 unchanged between the two starts/start attempts.

The issue has been reproduced with 4.3.18 and 4.3.20 after ensuring that host kernel modules were installed correctly with both dkms autoinstall and /etc/init.d/vboxdrv setup.

I cannot test on a test build because the MD5 checksum validation fails after downloads with three different download managers. I suspect systematic failure which I can address in a separte issue, on the mailing list or in the forum if it is absolutely necessary.

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