Bug#611861: [Pkg-virtualbox-devel] Bug#611861: virtualbox-ose: general protection fault after g_abExecMemory on a xen domU

2011-02-03 Thread Timo Juhani Lindfors
Frank Mehnert frank.mehn...@oracle.com writes:
 Running VirtualBox in DomU or in Dom0 is not supported.

Ok I can understand that (thanks for the speedy reply btw). Could you
consider adding something like

--- virtualbox-ose.orig 2011-02-03 10:58:53.0 +0200
+++ virtualbox-ose  2011-02-03 10:57:44.0 +0200
@@ -54,7 +54,13 @@
 start()
 {
log_begin_msg Starting VirtualBox kernel modules
-
+
+   if [ -d /proc/xen ]; then
+   log_failure_msg Running virtualbox under xen is not supported
+   log_end_msg 1
+   return 1
+   fi
+
if ! running vboxdrv; then
# HACK: disable the hardware performance counter framework
if [ -e /proc/sys/kernel/perf_counter_paranoid ]; then

to the init.d script? This way users would get an error message
instead of a system crash.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#611861: [Pkg-virtualbox-devel] Bug#611861: virtualbox-ose: general protection fault after g_abExecMemory on a xen domU

2011-02-03 Thread Frank Mehnert
Timo,

On Thursday 03 February 2011 10:00:15 Timo Juhani Lindfors wrote:
 Frank Mehnert frank.mehn...@oracle.com writes:
  Running VirtualBox in DomU or in Dom0 is not supported.
 
 Ok I can understand that (thanks for the speedy reply btw). Could you
 consider adding something like
 
 --- virtualbox-ose.orig 2011-02-03 10:58:53.0 +0200
 +++ virtualbox-ose  2011-02-03 10:57:44.0 +0200
 @@ -54,7 +54,13 @@
  start()
  {
 log_begin_msg Starting VirtualBox kernel modules
 -
 +
 +   if [ -d /proc/xen ]; then
 +   log_failure_msg Running virtualbox under xen is not supported
 +   log_end_msg 1
 +   return 1
 +   fi
 +
 if ! running vboxdrv; then
 # HACK: disable the hardware performance counter framework
 if [ -e /proc/sys/kernel/perf_counter_paranoid ]; then
 
 to the init.d script? This way users would get an error message
 instead of a system crash.

Sure, will do. Will this work for both DomU and Dom0?

Kind regards,

Frank
-- 
ORACLE Deutschland B.V.  Co. KG   Dr.-Ing. Frank Mehnert
Werkstrasse 24 Staff Engineer, VirtualBox
71384 Weinstadt, Germany   mailto:frank.mehn...@oracle.com

Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven


signature.asc
Description: This is a digitally signed message part.


Bug#611861: [Pkg-virtualbox-devel] Bug#611861: virtualbox-ose: general protection fault after g_abExecMemory on a xen domU

2011-02-03 Thread Timo Juhani Lindfors
Frank Mehnert frank.mehn...@oracle.com writes:
 Sure, will do. Will this work for both DomU and Dom0?

I think so.

dom0


overlord3:~$ ls -l /proc/xen
total 0
-r--r--r-- 1 root root 0 Jan 24 16:27 capabilities
-rw--- 1 root root 0 Jan 24 16:27 privcmd
-rw--- 1 root root 0 Jan 24 16:27 xenbus
-rw--- 1 root root 0 Jan 24 16:27 xsd_kva
-rw--- 1 root root 0 Jan 24 16:27 xsd_port
overlord3:~$ dmesg|head -n3
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-30) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 
05:46:49 UTC 2011


domU


lindi1:~$ ls -l /proc/xen
total 0
lindi1:~$ dmesg|head -n3
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 
03:40:32 UTC 2011

without xen
===

infra:~$ ls -l /proc/xen
ls: cannot access /proc/xen: No such file or directory
infra:~$ dmesg|head -n3
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.32-5-amd64 (Debian 2.6.32-29) 
(b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 
15:35:08 UTC 2010




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#611861: [Pkg-virtualbox-devel] Bug#611861: virtualbox-ose: general protection fault after g_abExecMemory on a xen domU

2011-02-03 Thread Frank Mehnert
Running VirtualBox in DomU or in Dom0 is not supported.

On Thursday 03 February 2011 00:25:02 Timo Juhani Lindfors wrote:
 Package: virtualbox-ose
 Version: 3.2.10-dfsg-1
 Severity: normal
 
 I tried to use virtualbox on a xen domU but it caused a general
 protection fault:
 
 [1668899.860029] tap1: no IPv6 routers present
 [1670426.400491] br0: port 2(tap1) entering disabled state
 [1670426.412252] br0: port 2(tap1) entering disabled state
 [1674996.276699] warning: `VirtualBox' uses 32-bit capabilities (legacy
 support in use) [1675047.499378] vboxdrv: Trying to deactivate the NMI
 watchdog permanently... [1675047.499383] vboxdrv: Successfully done.
 [1675047.499385] vboxdrv: Found 4 processor cores.
 [1675047.500045] VBoxDrv: dbg - g_abExecMemory=a017c6c0
 [1675047.500153] vboxdrv: fAsync=0 offMin=0x84a offMax=0x3f71
 [1675047.500796] vboxdrv: TSC mode is 'synchronous', kernel timer mode is
 'normal'. [1675047.500805] vboxdrv: Successfully loaded version 3.2.10_OSE
 (interface 0x00140001). [1675514.298848] general protection fault: 
 [#1] SMP
 [1675514.298867] last sysfs file: /sys/devices/system/cpu/cpu3/online
 [1675514.298871] CPU 0
 [1675514.298875] Modules linked in: vboxnetadp vboxnetflt vboxdrv tcp_diag
 inet_diag ext2 tun nls_utf8 isofs nls_base iptable_nat nf_nat
 nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables
 x_tables binfmt_misc fuse nfs lockd fscache nfs_acl auth_rpcgss sunrpc
 bridge stp loop evdev pcspkr ext3 jbd mbcache dm_mod xen_netfront
 xen_blkfront [last unloaded: stap_27c90217d4dade632344ca523a9b0f83_17490]
 [1675514.298926] Pid: 13117, comm: VirtualBox Not tainted 2.6.32-5-amd64
 #1 [1675514.298930] RIP: e030:[c9a54975]  [c9a54975]
 0xc9a54975 [1675514.298938] RSP: e02b:880069911ce0  EFLAGS:
 00010282
 [1675514.298942] RAX: 803b RBX: c9a8b340 RCX:
  [1675514.298946] RDX: c9a8b340 RSI:
  RDI: c9a8b000 [1675514.298950] RBP:
 880069911d38 R08: 0001ad00 R09: c9a8b000
 [1675514.298955] R10: c9a8b000 R11: 81152c80 R12:
 88002dc69290 [1675514.298959] R13: 0206 R14:
 7f885b692bb0 R15: a0306950 [1675514.298965] FS: 
 7f885b693710() GS:880003682000() knlGS:
 [1675514.298970] CS:  e033 DS:  ES:  CR0: 8005003b
 [1675514.298974] CR2: 7f8869d74de4 CR3: 79728000 CR4:
 0664 [1675514.298978] DR0:  DR1:
  DR2:  [1675514.298983] DR3:
  DR6: 4ff0 DR7: 0400
 [1675514.298988] Process VirtualBox (pid: 13117, threadinfo
 88006991, task 88000199a350) [1675514.298992] Stack:
 [1675514.298995]  c9a547d2 e033 a0190d8f
 636e795373736500 [1675514.299002] 0 0b3f 8100dc35
 00ff8100e242 636e795373736500 [1675514.299010] 0 88006ec16810
 88002dc69290 c0305687 880069911d78 [1675514.299019] Call
 Trace:
 [1675514.299027]  [a0190d8f] ? g_abExecMemory+0x146cf/0x18
 [vboxdrv] [1675514.299035]  [8100dc35] ?
 xen_force_evtchn_callback+0x9/0xa [1675514.299042]  [a0191205]
 g_abExecMemory+0x14b45/0x18 [vboxdrv] [1675514.299048] 
 [8100dc35] ? xen_force_evtchn_callback+0x9/0xa [1675514.299053] 
 [8100e242] ? check_events+0x12/0x20
 [1675514.299059]  [81152c80] ? cap_file_ioctl+0x0/0x3
 [1675514.299064]  [8100e242] ? check_events+0x12/0x20
 [1675514.299072]  [a016cee6] supdrvIOCtl+0x1240/0x2133 [vboxdrv]
 [1675514.299078]  [810e7cad] ? __kmalloc+0x12f/0x141
 [1675514.299083]  [8100e242] ? check_events+0x12/0x20
 [1675514.299091]  [a0170fbd] ? rtR0MemAlloc+0x88/0xb8 [vboxdrv]
 [1675514.299099]  [a0170fbd] ? rtR0MemAlloc+0x88/0xb8 [vboxdrv]
 [1675514.299106]  [a0169319] ? VBoxDrvLinuxIOCtl+0x116/0x191
 [vboxdrv] [1675514.299112]  [81048027] ?
 finish_task_switch+0x44/0xaf [1675514.299118]  [810fa68e] ?
 vfs_ioctl+0x21/0x6c
 [1675514.299122]  [810fabdc] ? do_vfs_ioctl+0x48d/0x4cb
 [1675514.299127]  [8100e242] ? check_events+0x12/0x20
 [1675514.299132]  [810fac6b] ? sys_ioctl+0x51/0x70
 [1675514.299137]  [81010b42] ? system_call_fastpath+0x16/0x1b
 [1675514.299141] Code: 88 06 00 00 48 83 e0 70 42 8b 8c 02 68 0a 00 00 23
 4a 20 09 c8 0b 42 24 0f 22 e0 42 8b 84 02 50 0a 00 00 83 e0 04 0d 3b 00 00
 80 0f 22 c0 42 0f 01 94 02 70 03 00 00 42 8b ac 02 20 03 00 00 b8
 [1675514.299201] RIP  [c9a54975] 0xc9a54975
 [1675514.299207]  RSP 880069911ce0
 [1675514.299219] ---[ end trace f60b712c70b93946 ]---
 [1675519.737380] hostname[13131] general protection ip:7ff31a82a134
 sp:7fff99f2ea40 error:0 in ld-2.11.2.so[7ff31a829000+1e000]
 [1675519.825499] hostname[13135] general protection ip:7f13cb247134
 sp:7fff3d20d180 error:0 in