VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (508 - 510 of 16363)

Ticket Resolution Summary Owner Reporter
#520 duplicate VB 1.4 crashes on fedora 7 launching a vm jcezanna56
Description

I can create a vm but when I try to launch it to install, a new window is opened, a dialog annouces starting and everything freezes. I have to kill and xkill everything. VirtualBox is unusable.


$ ls -d /opt/V* ; uname -a /opt/VirtualBox-1.4.0 Linux nadiav12 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 i686 i386 GNU/Linux


Syslog messages : Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: general protection fault: 0000 #2 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: SMP Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: CPU: 1 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EIP: 0060:[<052a10de>] Tainted: P VLI Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EFLAGS: 00010002 (2.6.22.1-27.fc7 #1) Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: EIP is at 0x52a10de Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: eax: 00000254 ebx: 00000046 ecx: 00000000 edx: 03e7e300 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: esi: 00000000 edi: 00000000 ebp: ea6c8fc4 esp: ea6c8f70 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Process VirtualBox (pid: 11132, ti=ea6c8000 task=ed67a000 task.ti=ea6c8000) Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Stack: 052a100b ec2b0060 f8c8c307 03e7e000 ed67a000 ed67a000 00000046 08e712e0 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ea6c8fb8 ea6c8000 c0407bc4 00000046 b66da0a0 00000001 00000003 08e712e0 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: b66da0e0 c0405082 03e7e000 64726962 03e7e000 b66da1a8 f8c68034 03e7e000 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c0407bc4>] do_syscall_trace+0x2f/0xc2 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Call Trace: Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c0405082>] syscall_exit_work+0x12/0x17 Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: [<c060007b>] xfrm_user_rcv_msg+0xac/0xfc Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: ======================= Message from syslogd@ at Thu Jul 26 16:49:04 2007 ... nadiav12 kernel: Code: Bad EIP value. Message from syslogd@ at Thu Jul 26 16:49:04 2007 ...

#521 wontfix shutdown of a VM with ALSA sound backend freezes host (Linux 2.6.11) larsf
Description

I have an IBM xSeries with 2 CPUs à 2,4GHz with Hyper-Threading (makes 4 virtual CPUs à 2,4GHz) and 2 GB RAM running Ubuntu Feisty (7.04) as host system.

Running three VMs via commands like "nohup VBoxVRDP -startvm sles10-node1 > /home/virtualbox/Machines/sles10-node1/Logs/nohup.log 2>&1 &" works without problems. Adding and starting a fourth node leads to the problem, that the kernel of the host completely freezes when trying to poweroff (VBoxManage controlvm sles10-node1 poweroff) or kill (kill -9 <pid>) one of the four processes for the four running VMs. On the console the following message appears: "BUG: soft lock detected for CPU#3".

Passing the parameter "nostflock" to the kernel via the menu.lst in /boot/grub/ was tried, but with the same result! :/ Disabling Hyper-Threading in the BIOS didn't improve the issue either.

A memtest86+ will run this night, but we don't really think the RAM is broken or something, but you never know... If the test does not indicate any errors tomorrow morning, the issue still remains unsolved... :(

The strange thing is that this issue only occurs when running 4 VMs (with 3 all works fine) and only when trying to poweroff or kill one of them. Until then, they run happily!

An extract of /var/log/messages is attached...

#522 obsolete Windows XP cannot boot if burning DVD in host steqve
Description

If I record a DVD (not tested CD) in VBox 1.4.0 I cannot boot my windows guests. It seems that windows tries to read information from the CD and there must be some kind of dead lock on the drive, cause the recording will halt and hang.

If I shutdown the guest, the host vill not recover from this error and the DVD never be completely written. The eject button on DVD drive will not work cause the entire drive is locked up. A reboot of the computer is necessary.

I have not tried to start a recording after windows has started! I assume that the same problem will arise.

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