RDP connected client vm crash in VBoxHeadless started VM - Guru Meditation - 4011 (VERR_VMX_IN_VMX_ROOT_MODE)

[yanhuang]

Host: Ubuntu 13.04 Server AMD64

Client: Ubuntu 13.04 Desktop AMD64

When I try to install a client vm on Ubuntu 13.04 Server (AMD64) on VirtualBox 4.2.10 from command line, the client vm keeps crash each time with error message as below:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! !! Guru Meditation -4011 (VERR_VMX_IN_VMX_ROOT_MODE) !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! DBGF: No debugger attached, waiting 1 second for one to attach (event=100) 1.Stopping the VM!

see full log in attached log file, and below is the commands I use to create and start the vm:

---

VBoxManage createvm --name "Ubuntu" --ostype Ubuntu --register

VBoxManage modifyvm "Ubuntu" --memory 1000 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 em1 --vrdeport 5000,5010-5012

VBoxManage createhd --filename "vms/Ubuntu.vdi" --size 30000

VBoxManage storagectl "Ubuntu" --name "IDE Controller" --add ide --controller PIIX4

VBoxManage storageattach "Ubuntu" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium vms/Ubuntu.vdi

VBoxManage storageattach "Ubuntu" --storagectl "IDE Controller" --port 0 --device 1 --type dvddrive --medium ubuntu-13.04-desktop-i386.iso

VBoxHeadless --startvm "Ubuntu"

[yanhuang]

VBox.log - 05/10/2013

[yanhuang]

call trace as below

May 10 14:33:48 Ubuntu-Server kernel: [361360.455568] Call Trace:  
May 10 14:33:48 Ubuntu-Server kernel: [361360.462088]  [<ffffffff8117d4e5>] ? __kmalloc+0x55/0x170 
May 10 14:33:48 Ubuntu-Server kernel: [361360.468718]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.475515]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.482233]  [<ffffffffa0203ace>] ? supdrvIOCtl+0x155e/0x2a70 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.489078]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.496030]  [<ffffffffa01fe448>] ? VBoxDrvLinuxIOCtl_4_2_10+0x118/0x1f0 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.503075]  [<ffffffff811a5969>] ? do_vfs_ioctl+0x99/0x570
May 10 14:33:48 Ubuntu-Server kernel: [361360.510140]  [<ffffffff811a5ed1>] ? sys_ioctl+0x91/0xb0
May 10 14:33:48 Ubuntu-Server kernel: [361360.517270]  [<ffffffff816cf1be>] ? do_page_fault+0xe/0x10
May 10 14:33:48 Ubuntu-Server kernel: [361360.524472]  [<ffffffff816d37dd>] ? system_call_fastpath+0x1a/0x1f
May 10 14:33:48 Ubuntu-Server kernel: [361360.531700] Code: 00 0f 20 d8 4a 89 84 02 c0 06 00 00 0f 20 e0 4a 89 84 02 c8 06 00 00 48 83 e0 70 42 8b 8c 02 b8 0a 00 00 23 4a 20 09 c8 0b 42 24 <0f> 22 e0 42 8b 84 02 a0 0a 00 00 83 e0 04 0d 3b 00 00 80 0f 22
May 10 14:33:48 Ubuntu-Server kernel: [361360.547322] RIP  [<ffffc9001ce3aa42>] 0xffffc9001ce3aa41
May 10 14:33:48 Ubuntu-Server kernel: [361360.555164]  RSP <ffff8806e0c09d58>
May 10 14:33:48 Ubuntu-Server kernel: [361360.580137] ---[ end trace 665418ca79d46256 ]---

[Frank Mehnert]

Please attach the complete output of 'dmesg' from the host when this happened. That error code is normally a sign that some other VMM is running in parallel (e.g. KVM).

[yanhuang]

the guest iso I use is ubuntu-13.04-desktop-amd64.iso, and by following ​Perryg's suggestion, after I have enable ioapic, the client vm never crashes.

but I still have encountered client vm hang up using VRDP remote control, while seems the client vm quite stable without VRDP connection. Though this could be another issue.

below is the full log for previous crash:

May 10 14:33:48 Ubuntu-Server kernel: [361360.347117] CPU 5
May 10 14:33:48 Ubuntu-Server kernel: [361360.347181] Pid: 23192, comm: EMT Tainted: GF     D W  O 3.8.0-19-generic #30-Ubuntu Dell Inc. PowerEdge R720/0T0WRN
May 10 14:33:48 Ubuntu-Server kernel: [361360.357198] RIP: 0010:[<ffffc9001ce3aa42>]  [<ffffc9001ce3aa42>] 0xffffc9001ce3aa41
May 10 14:33:48 Ubuntu-Server kernel: [361360.362645] RSP: 0018:ffff8806e0c09d58  EFLAGS: 00010002
May 10 14:33:48 Ubuntu-Server kernel: [361360.368025] RAX: 0000000000000264 RBX: ffffc9000c0d8000 RCX: 0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.373636] RDX: ffffc9001ce51340 RSI: 0000000000000000 RDI: 0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.379299] RBP: ffff8806e0c09da0 R08: 000000000001ae80 R09: ffffc9001ce51000
May 10 14:33:48 Ubuntu-Server kernel: [361360.384904] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.390476] R13: 0000000000000206 R14: ffff8817314d0390 R15: ffff8817314d0390
May 10 14:33:48 Ubuntu-Server kernel: [361360.396006] FS:  00007f51aea36700(0000) GS:ffff88183fc40000(0000) knlGS:0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.401581] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 10 14:33:48 Ubuntu-Server kernel: [361360.407263] CR2: 00007f51b424a790 CR3: 000000151b7cd000 CR4: 00000000000427e0
May 10 14:33:48 Ubuntu-Server kernel: [361360.412994] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.418810] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 10 14:33:48 Ubuntu-Server kernel: [361360.424667] Process EMT (pid: 23192, threadinfo ffff8806e0c08000, task ffff880bf9b5ae80)
May 10 14:33:48 Ubuntu-Server kernel: [361360.430587] Stack:
May 10 14:33:48 Ubuntu-Server kernel: [361360.436524]  ffffc9001ce3a7b2 0000000000000010 ffffffffa0298310 0000000000000000
May 10 14:33:48 Ubuntu-Server kernel: [361360.442758]  0000000000000068 ffff8806e0c09d90 ffffffffa02325a0 00007f51aea35b30
May 10 14:33:48 Ubuntu-Server kernel: [361360.449110]  ffff8815954e9810 ffff8806e0c09de0 ffffffffa0298a30 ffffffff8117d4e5
May 10 14:33:48 Ubuntu-Server kernel: [361360.455568] Call Trace:
May 10 14:33:48 Ubuntu-Server kernel: [361360.462088]  [<ffffffff8117d4e5>] ? __kmalloc+0x55/0x170
May 10 14:33:48 Ubuntu-Server kernel: [361360.468718]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.475515]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.482233]  [<ffffffffa0203ace>] ? supdrvIOCtl+0x155e/0x2a70 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.489078]  [<ffffffffa020c4dd>] ? rtR0MemAllocEx+0x17d/0x250 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.496030]  [<ffffffffa01fe448>] ? VBoxDrvLinuxIOCtl_4_2_10+0x118/0x1f0 [vboxdrv]
May 10 14:33:48 Ubuntu-Server kernel: [361360.503075]  [<ffffffff811a5969>] ? do_vfs_ioctl+0x99/0x570
May 10 14:33:48 Ubuntu-Server kernel: [361360.510140]  [<ffffffff811a5ed1>] ? sys_ioctl+0x91/0xb0
May 10 14:33:48 Ubuntu-Server kernel: [361360.517270]  [<ffffffff816cf1be>] ? do_page_fault+0xe/0x10
May 10 14:33:48 Ubuntu-Server kernel: [361360.524472]  [<ffffffff816d37dd>] ? system_call_fastpath+0x1a/0x1f
May 10 14:33:48 Ubuntu-Server kernel: [361360.531700] Code: 00 0f 20 d8 4a 89 84 02 c0 06 00 00 0f 20 e0 4a 89 84 02 c8 06 00 00 48 83 e0 70 42 8b 8c 02 b8 0a 00 00 23 4a 20 09 c8 0b 42 24 <0f> 22 e0 42 8b 84 02 a0 0a 00 00 83 e0 04 0d 3b 00 00 80 0f 22
May 10 14:33:48 Ubuntu-Server kernel: [361360.547322] RIP  [<ffffc9001ce3aa42>] 0xffffc9001ce3aa41
May 10 14:33:48 Ubuntu-Server kernel: [361360.555164]  RSP <ffff8806e0c09d58>
May 10 14:33:48 Ubuntu-Server kernel: [361360.580137] ---[ end trace 665418ca79d46256 ]---

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.