View Issue Details

IDProjectCategoryView StatusLast Update
0000575Kali Linux[All Projects] General Bugpublic2014-01-09 15:44
Reporterluis.rato Assigned Torhertzog  
PriorityhighSeverityblockReproducibilityalways
Status resolvedResolutionfixed 
Product Version1.0.5 
Target VersionFixed in Version1.0.6 
Summary0000575: ext4 File Journaling not compatible with Hyper-V
DescriptionKali Linux 1.05 and below are not compatible with Hyper-V Hypervisor when installed on a ext4 File System Journaling due to a regression on the storvsc driver that is using the "WRITE_SAME" method on the ext4 File System Journaling.

The "WRITE_SAME" method has never been supported on any Hyper-V version.

For compability reasons the "WRITE_SAME" method has to be disabled and blacklisted on the storvsc driver, please see the appropriate patch and integrate it on a future version of Kali Linux as shared on the link of the Additional Information section.
Steps To ReproduceIssue:
Installing Kali Linux 1.05 and below on a Hyper-V Host with the ext4 file system journaling on the root "/" partition will hang the OS installation during the copy files process.


Issue occours when:
-You use Manual and Guided install and with or without LVM Encryption;
-You use ext4 File System Journalism for the root partition "/";
-You attempt to install Kali Linux 1.05 and below;
-You install Kali Linux on Hyper-V host 3.x (Windows 8/8.1 or Windows Server 2012/R2);

Issue does not occour when:
-You use Manual and Guided install and with or without LVM Encryption;
-You use ext3 File System Journalism for the root partition "/";
-You attempt to install Kali Linux 1.05 and below;
-You install Kali Linux on Hyper-V host 3.x (Windows 8/8.1 or Windows Server 2012/R2);



Additional InformationPlease integrate the new Storvsc driver patch from the following:

https://patchwork.kernel.org/patch/2172871/


Activities

rhertzog

2014-01-09 15:44

administrator   ~0001307

We have switched to linux 3.12 in Kali 1.0.6 and that version of the kernel has the patch that you mention. Thus I assume that this bug can be considered fixed.

Issue History

Date Modified Username Field Change
2013-09-10 10:13 luis.rato New Issue
2014-01-09 15:44 rhertzog Note Added: 0001307
2014-01-09 15:44 rhertzog Status new => resolved
2014-01-09 15:44 rhertzog Fixed in Version => 1.0.6
2014-01-09 15:44 rhertzog Resolution open => fixed
2014-01-09 15:44 rhertzog Assigned To => rhertzog