View Issue Details

IDProjectCategoryView StatusLast Update
0003613Kali LinuxGeneral Bugpublic2018-01-29 12:51
Reporterbrokeit Assigned Tog0tmi1k  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionsuspended 
Product Version2016.2 
Summary0003613: Hyper-V i386 Partitioning/Installing Kernel Panic
Description

Installing Kali.2016.i386 from .iso on to any variation of VM setting will cause a hard locked kernel panic.

Windows 2012 Server - Hyper-V
Gen1 VM
512-4096MB
1-2 CPU
IDE or SCSI
Legacy or Modern Network Adapter

Steps To Reproduce
  1. Enable Hyper-V Role on Windows 10/Server 2012
  2. Configure VM Settings
  3. Attempt Install
  4. After confirming partition details, system kernel panics and locks up.
    4b. If drive is already partitioned via liveboot, proceed to Installing system, and receive kernel panic.
Additional Information

http://unix.stackexchange.com/questions/46060/debian-stucks-at-formatting-33

Attached Files
panic.png (253,069 bytes)   
panic.png (253,069 bytes)   
dmesg.log (30,149 bytes)
lspci.log (2,509 bytes)
lsmod.log (2,107 bytes)

Activities

g0tmi1k

g0tmi1k

2018-01-29 12:51

administrator   ~0008217

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2016-09-22 21:22 brokeit New Issue
2016-09-22 21:22 brokeit File Added: panic.png
2016-09-22 21:22 brokeit File Added: dmesg.log
2016-09-22 21:22 brokeit File Added: lspci.log
2016-09-23 00:01 brokeit File Added: lsmod.log
2018-01-29 12:51 g0tmi1k Assigned To => g0tmi1k
2018-01-29 12:51 g0tmi1k Status new => closed
2018-01-29 12:51 g0tmi1k Resolution open => suspended
2018-01-29 12:51 g0tmi1k Note Added: 0008217