Search

Language:  
Search for:

Available article translations:

Virtual machine stuck on boot

APPLIES TO:
  • Parallels Server for Mac
  • Parallels Server Bare Metal

Symptoms

The virtual machine is stuck on boot. The following panic output is displayed in the console:
------------[ cut here ]------------
kernel BUG at arch/x86/kernel/alternative.c:227!
invalid opcode: 0000 [#1] SMP 
last sysfs file: /sys/devices/virtual/block/dm-0/dev
CPU 0 
Modules linked in: ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom pata_acpi ata_generic ata_piix ahci virtio_pci virtio_ring virtio dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]

Modules linked in: ext4 mbcache jbd2 sd_mod crc_t10dif sr_mod cdrom pata_acpi ata_generic ata_piix ahci virtio_pci virtio_ring virtio dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan]
Pid: 622, comm: modprobe Tainted: P           ----------------   2.6.32-131.0.15.el6.x86_64 #1 Parallels Virtual Platform
RIP: 0010:[<ffffffff81011f46>]  [<ffffffff81011f46>] apply_alternatives+0x236/0x270
RSP: 0018:ffff88001ac3dc48  EFLAGS: 00010206
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000010
RDX: ffffffffa0149fcf RSI: ffffffffa014b294 RDI: ffffffffa014b1a8
RBP: ffff88001ac3dda8 R08: 0000000000000000 R09: ffffffff817764b7
R10: ffffffff817764bd R11: ffffffff817764ce R12: ffffffffa014b1a8
R13: ffffc90000be3938 R14: ffffffff817764d9 R15: 0000000000000006
FS:  00007f81015c0700(0000) GS:ffff880002000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f810153700f CR3: 000000001d59f000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 622, threadinfo ffff88001ac3c000, task ffff88001d843540)
Stack:
 ffffffff81b9e080 000000000000000c ffffffffa014b294 ffffffffa0149fcf
<0> ffffffffa000dce0 ffff88001ac3ddd8 ffff88001ac3dcc8 ffffffff810a9c65
<0> ffff88001ac3dcb8 0000000381093e7f ffff88001ac3dcb8 ffffffffa000dce8
Call Trace:
 [<ffffffff810a9c65>] ? each_symbol_in_section.clone.0+0x65/0xa0
 [<ffffffff810a8800>] ? find_symbol_in_section+0x0/0xe0
 [<ffffffff810a9e3c>] ? each_symbol+0x19c/0x1e0
 [<ffffffff81032787>] module_finalize+0xe7/0x160
 [<ffffffff8126ea20>] ? generic_swap+0x0/0x30
 [<ffffffff810ac4a2>] load_module+0x17c2/0x1ca0
 [<ffffffff810a93e0>] ? setup_modinfo_srcversion+0x0/0x30
 [<ffffffff810ac9f9>] sys_init_module+0x79/0x250
 [<ffffffff8100b172>] system_call_fastpath+0x16/0x1b
Code: b8 fe ff ff 0f 84 bc fe ff ff 48 89 d1 49 8b 14 24 48 c7 c6 b0 10 60 81 48 c7 c7 a8 84 77 81 31 c0 e8 b2 8d 4c 00 e9 9b fe ff ff <0f> 0b eb fe 0f 0b 0f 1f 40 00 eb fa 48 89 f1 48 89 fa 48 c7 c6 
RIP  [<ffffffff81011f46>] apply_alternatives+0x236/0x270
 RSP <ffff88001ac3dc48>
---[ end trace 6b0936c83a8478d7 ]---
Kernel panic - not syncing: Fatal exception
Pid: 622, comm: modprobe Tainted: P      D    ----------------   2.6.32-131.0.15.el6.x86_64 #1
Call Trace:
 [<ffffffff814dac28>] ? panic+0x78/0x143
 [<ffffffff814dec74>] ? oops_end+0xe4/0x100
 [<ffffffff8100f2fb>] ? die+0x5b/0x90
 [<ffffffff814de544>] ? do_trap+0xc4/0x160
 [<ffffffff8100ceb5>] ? do_invalid_op+0x95/0xb0
 [<ffffffff81011f46>] ? apply_alternatives+0x236/0x270
 [<ffffffff812a92d9>] ? vga_set_mem_top+0x59/0x60
 [<ffffffff8126d65a>] ? delay_tsc+0x4a/0x80
 [<ffffffff8100bf5b>] ? invalid_op+0x1b/0x20
 [<ffffffff81011f46>] ? apply_alternatives+0x236/0x270
 [<ffffffff810a9c65>] ? each_symbol_in_section.clone.0+0x65/0xa0
 [<ffffffff810a8800>] ? find_symbol_in_section+0x0/0xe0
 [<ffffffff810a9e3c>] ? each_symbol+0x19c/0x1e0
 [<ffffffff81032787>] ? module_finalize+0xe7/0x160
 [<ffffffff8126ea20>] ? generic_swap+0x0/0x30
 [<ffffffff810ac4a2>] ? load_module+0x17c2/0x1ca0
 [<ffffffff810a93e0>] ? setup_modinfo_srcversion+0x0/0x30
 [<ffffffff810ac9f9>] ? sys_init_module+0x79/0x250
 [<ffffffff8100b172>] ? system_call_fastpath+0x16/0x1b

Cause

The issue is caused by a Red Hat kernel bug, #799834, in 2.6.32-220 kernels.

Resolution

Use one of these workarounds to resolve the issue:
  1. Plug USB device into virtual machine
  2. Add/remove CPU to/from virtual machine



2897d76d56d2010f4e3a28f864d69223 38b350a8e16219ab065862b865a4acb0 ca05eaf5b843fbd53589c90d7228a6df f5fb5ece659efa734e6246bdcb55fa2c

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No
 
 
 
 
 
 
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0
- Parallels Virtuozzo Containers
Automation
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification