VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1150 - 1152 of 16363)

Ticket Resolution Summary Owner Reporter
#12848 duplicate cannot change the Host key -> duplicate of #12847 Edo777
Description

I installed the new version of Virtual Box 4.3.8.92456 on a new machine. I have been trying to set the host key differently from the default RIGHT-CTRL. The new key combination is apparently accepted on OK, but then it is auto-setting back to default RIGHT-CTRL. I am apparently unable to set the key on a different key combination. Is this a bug? thanks edo

#6279 invalid Kernel panic when running VMs with VBoxHeadless Edoardo
Description

Hello to all.

I've got an issue using VirtualBox with the VBoxHeadless mode in Solaris host.

My host is running on a Dell 400SC hardware with two 120GB disks in zfs mirror (rpool) and 6x 1TB external drive in zfs radiz (datas). Host running Solaris 10 10/08 s10x_u6wos_07b X86 with 142901-04 kernel (32bit). and I've tried both Virtualbox 3.1.2 and 3.1.4 with the same result.

I've got two linux VMs: IPCop with 2.4 kernel and Debian with 2.6 kernel

If I start and use the VMs with VirtualBox GUI over VNC or local console, all works perfectly.

Even If I try to use the VMs with the VBoxHeadless mode, the host machine crashes with kernel panic after few seconds from guest OS is loaded. Not immediately, but after few second (during logon via console or ssh on the guest OS, but it happens even if I did not logon on the guest)

No error in the VM logs, but here it is the crash log I've found in /var/adm/messages:

Feb 24 00:22:35 srv unix: [ID 836849 kern.notice]
Feb 24 00:22:35 srv ^Mpanic[cpu1]/thread=cbb34dc0:
Feb 24 00:22:35 srv genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=cbb34c2c addr=14a240cb occurred in module "genunix" due to an illegal access to a user address
Feb 24 00:22:35 srv unix: [ID 100000 kern.notice]
Feb 24 00:22:35 srv unix: [ID 839527 kern.notice] sched:
Feb 24 00:22:35 srv unix: [ID 753105 kern.notice] #pf Page fault
Feb 24 00:22:35 srv unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x14a240cb
Feb 24 00:22:35 srv unix: [ID 243837 kern.notice] pid=0, pc=0xfe8afb35, sp=0xe2b1d9f8, eflags=0x10202
Feb 24 00:22:35 srv unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6d8<xmme,fxsr,pge,mce,pse,de>
Feb 24 00:22:35 srv unix: [ID 936844 kern.notice] cr2: 14a240cb cr3: db89000
Feb 24 00:22:35 srv unix: [ID 537610 kern.notice]        gs: cc0d01b0  fs: e1070000  es:      160  ds:  d520160
Feb 24 00:22:35 srv unix: [ID 537610 kern.notice]       edi:        6 esi: fead4ffc ebp: cbb34c7c esp: cbb34c64
Feb 24 00:22:35 srv unix: [ID 537610 kern.notice]       ebx: deb9cdf8 edx:        0 ecx: 14a240cb eax:        0
Feb 24 00:22:35 srv unix: [ID 537610 kern.notice]       trp:        e err:        0 eip: fe8afb35  cs:      158
Feb 24 00:22:35 srv unix: [ID 717149 kern.notice]       efl:    10202 usp: e2b1d9f8  ss: cbb34ca4
Feb 24 00:22:35 srv unix: [ID 100000 kern.notice]
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34b8c unix:die+a7 (e, cbb34c2c, 14a240)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34c18 unix:trap+1130 (cbb34c2c, 14a240cb,)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34c2c unix:cmntrap+9b (cc0d01b0, e1070000,)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34c7c genunix:avl_walk+2d (cc0d6598, e2b1d9f8,)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34ca4 zfs:space_map_walk+45 (cc0d6598, fead4ffc,)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34cec zfs:metaslab_sync+1b5 (cc0d6340, 87d7a, 0)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34d14 zfs:vdev_sync+a8 (cb657200, 87d7a, 0)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34d5c zfs:spa_sync+38e (d209c680, 87d7a, 0)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34da8 zfs:txg_sync_thread+22c (d28fa080, 0)
Feb 24 00:22:35 srv genunix: [ID 353471 kern.notice] cbb34db8 unix:thread_start+8 ()
Feb 24 00:22:35 srv unix: [ID 100000 kern.notice]
Feb 24 00:22:35 srv genunix: [ID 672855 kern.notice] syncing file systems...
Feb 24 00:22:35 srv genunix: [ID 904073 kern.notice]  done
Feb 24 00:22:36 srv genunix: [ID 111219 kern.notice] dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
Feb 24 00:23:25 srv genunix: [ID 409368 kern.notice] ^M100% done: 140661 pages dumped, compression ratio 2.00,
Feb 24 00:23:25 srv genunix: [ID 851671 kern.notice] dump succeeded

My Solaris version:

root@srv{~}> uname -a
SunOS srv 5.10 Generic_142901-04 i86pc i386 i86pc


root@srv{~}> cat /etc/release
                       Solaris 10 10/08 s10x_u6wos_07b X86
           Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                            Assembled 27 October 2008

In attachment some logs and infos about my system. YAMJ.xml.txt is the xml config file of the VM.

#15395 obsolete vboxweb-service stop ok for debian EduardoDiaz
Description

Hi is a but on start stop script for debian on vboxweb-service

The script is not stop well because start-stop-daemon on debian don't delete the pid at stop. For this reason some times the script don't start well too.

The best way to solve this is add some rm of the pid if the script stop ok the software.

on line 142

change this.

killproc() {

start-stop-daemon --stop --exec $@

}

for this

killproc() {

start-stop-daemon --stop --exec $@ rm $PIDFILE

}

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