Custom Query (16363 matches)
Results (1477 - 1479 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #14965 | fixed | CPU general protection fault when starting VM in newly released VirtualBox 5.0.12 | ||
| Description |
After upgrading to Virtualbox 5.0.12, we are getting a general protection fault when starting a VM: Dec 21 20:26:15 HOSTNAME kernel: [2323400.623107] general protection fault: 0000 [#1] SMP Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] Modules linked in: vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c pci_stub iosf_mbi kvm_intel kvm crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel cirrus ttm aes_x86_64 lrw drm_kms_helper gf128mul glue_helper ablk_helper cryptd drm serio_raw syscopyarea sysfillrect pvpanic sysimgblt parport_pc 8250_fintek parport mac_hid i2c_piix4 nls_utf8 isofs 8139too floppy psmouse 8139cp mii pata_acpi [last unloaded: vboxdrv] Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] CPU: 0 PID: 23258 Comm: EMT Tainted: G OE 3.19.0-33-generic #38~14.04.1-Ubuntu Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] task: ffff880036b49d70 ti: ffff88003fc98000 task.ti: ffff88003fc98000 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RIP: 0010:[<ffffffffc000b45e>] [<ffffffffc000b45e>] 0xffffffffc000b45e Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RSP: 0018:ffff88003fc9bd48 EFLAGS: 00010206 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RAX: 000000000000009b RBX: 00000000ffffffdb RCX: 000000000000009b Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88003fc9bca0 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RBP: ffff88003fc9bd88 R08: ffffffff81815108 R09: 000000008000000a Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] R10: 0000000000000009 R11: 0000000000000000 R12: 0000000001000020 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] R13: 0000000000000020 R14: ffff880014dbdf10 R15: 0000000000000000 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] FS: 00007fbb322bb700(0000) GS:ffff88007fc00000(0000) knlGS:0000000000000000 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] CR2: 00007fbb3205f000 CR3: 000000000a3d8000 CR4: 00000000000406f0 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] Stack: Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] 0000000000000000 000000000000003f ffff88003fc9bd88 ffffffff00000000 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] 0000000000000000 0000000000000000 0000000000000000 ffffc900008f1010 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] ffff88003fc9bda8 ffffffffc001fb3c 0000000000000000 ffffffffc07601c0 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] Call Trace: Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffffc0725600>] ? supdrvIOCtl+0x1fc0/0x3400 [vboxdrv] Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffffc071f541>] ? VBoxDrvLinuxIOCtl_5_0_12+0x121/0x210 [vboxdrv] Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffff811ffc58>] ? do_vfs_ioctl+0x2f8/0x510 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffff81062335>] ? trace_do_page_fault+0x45/0x100 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffff811ffef1>] ? SyS_ioctl+0x81/0xa0 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] [<ffffffff817b6dcd>] ? system_call_fastpath+0x16/0x1b Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] Code: 0e 00 00 00 01 00 89 c1 0f 32 48 c1 e2 20 89 c0 48 09 d0 48 89 05 a3 ac 0e 00 0f 20 e0 48 89 05 81 ac 0e 00 b8 9b 00 00 00 89 c1 <0f> 32 48 c1 e2 20 89 c0 48 09 d0 48 89 05 78 ac 0e 00 b8 80 00 Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RIP [<ffffffffc000b45e>] 0xffffffffc000b45e Dec 21 20:26:15 HOSTNAME kernel: [2323400.624017] RSP <ffff88003fc9bd48> Dec 21 20:26:15 HOSTNAME kernel: [2323400.849237] ---[ end trace 8dac6f21b9aec12d ]--- Here is VBox.log: VirtualBox VM 5.0.12 r104815 linux.amd64 (Dec 18 2015 18:20:39) release log 00:00:00.322506 Log opened 2015-12-21T20:26:14.864896000Z 00:00:00.322507 Build Type: release 00:00:00.322510 OS Product: Linux 00:00:00.322511 OS Release: 3.19.0-33-generic 00:00:00.322512 OS Version: #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28 UTC 2015 00:00:00.322584 DMI Product Name: Standard PC (i440FX + PIIX, 1996) 00:00:00.322599 DMI Product Version: pc-i440fx-trusty 00:00:00.322696 Host RAM: 2001MB total, 1458MB available 00:00:00.322700 Executable: /usr/lib/virtualbox/VBoxHeadless 00:00:00.322701 Process ID: 23249 00:00:00.322701 Package type: LINUX_64BITS_UBUNTU_12_04 00:00:00.495355 Installed Extension Packs: 00:00:00.495401 None installed! 00:00:00.497797 Console: Machine state changed to 'Starting' The problem appears to be related to running VirtualBox 5.0.12 inside a QEMU KVM virtual machine. Our use-case is to help parallelize automated tests by running multiple vagrant+Virtualbox instances, each isolated in their own QEMU KVM virtual machine. This prevents tests from conflicting with each other. WorkaroundVirtualBox 5.0.10 works perfectly, so we are currently working around this by downgrading to 5.0.10. |
|||
| #13254 | obsolete | CPU hot unplug crashes VBoxService on Linux guest | ||
| Description |
When
For illustration purpose, hot-remove for CPU 3 is shown here. The bug affects any non-zero CPU cores. Steps to reproduce:
VBoxManage.exe: error: Hot-Remove was aborted because the CPU may still be used by the guest VBoxManage.exe: error: Details: code VBOX_E_VM_ERROR (0x80bb0003), component Console, interface IConsole, callee IUnknown VBoxManage.exe: error: Context: "HotUnplugCPU(n)" at line 135 of file VBoxManageControlVM.cpp
When
Also note that no crash happens when However, it is still possible to do CPU hot-remove manually afterwards. Following the sysfs path printed in attached log, one can do CPU eject manually in Linux guest:
Path can differ a bit for various distro. After that. unplugcpu works fine on host: [C:\Program Files\Oracle\VirtualBox].\VBoxManage.exe controlvm [UUID] unplugcpu 3 [C:\Program Files\Oracle\VirtualBox].\VBoxManage.exe controlvm [UUID] unplugcpu 3 VBoxManage.exe: error: CPU 3 is not attached VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component SessionMachine, interface IMachine, callee IUnknown VBoxManage.exe: error: Context: "HotUnplugCPU(n)" at line 135 of file VBoxManageControlVM.cpp |
|||
| #15170 | wontfix | CPU is not identified correctly | ||
| Description |
Like the log of this ticket ( https://www.virtualbox.org/ticket/15155 ) shows my CPU is matched against an "AMD Phenom II X6 1100T" on the line "CPUM: Matched host CPU AMD 0x10/0xa/0x0 AMD_K10 with CPU DB entry 'AMD Phenom II X6 1100T' (AMD 0x10/0xa/0x0 AMD_K10)". But my host is actually running on an "AMD Phenom(tm) II X6 1045T Processor". |
|||

