Kernel v3.2 used in SlackWare 14.00 please, backport all needed patches Re: [PATCH net, 1/2] hyperv: Fix a kernel warning from netvsc_linkstatus_callback()

From: Victor Miasnikov
Date: Thu May 23 2013 - 09:15:15 EST


(the 3.2 version is different,
and it's instaging. (at not used by distros anyway))

No: used

Linux Kernel v3.2 used in:
-- SlackWare 14.00

This is actual stable version SlackWare

Please, backport all(!) needed patches

I'm download

File ata_piix.c ( SHA1 ceaf441142ad3f6768ff71f023e73d0695458e2c ) from
not contain:
( even not contain sub-string "Hyper-V")
== ( VVM: symbol TAB replaced by Space+Space -- special for users of MS IE, MS OutLook [Express] )
static int prefer_ms_hyperv = 1;
module_param(prefer_ms_hyperv, int, 0);
"Prefer Hyper-V paravirtualization drivers instead of ATA, "
"0 - Use ATA drivers, "
"1 (Default) - Use the paravirtualization drivers.");

static void piix_ignore_devices_quirk(struct ata_host *host)
static const struct dmi_system_id ignore_hyperv[] = {
/* On Hyper-V hypervisors the disks are exposed on
* both the emulated SATA controller and on the
* paravirtualised drivers. The CD/DVD devices
* are only exposed on the emulated controller.
* Request we ignore ATA devices on this host.
.ident = "Hyper-V Virtual Machine",
.matches = {
"Microsoft Corporation"),
{ } /* terminate list */
static const struct dmi_system_id allow_virtual_pc[] = {
/* In MS Virtual PC guests the DMI ident is nearly
* identical to a Hyper-V guest. One difference is the
* product version which is used here to identify
* a Virtual PC guest. This entry allows ata_piix to
* drive the emulated hardware.
.ident = "MS Virtual PC 2007",
.matches = {
"Microsoft Corporation"),
{ } /* terminate list */
const struct dmi_system_id *ignore = dmi_first_match(ignore_hyperv);
const struct dmi_system_id *allow = dmi_first_match(allow_virtual_pc);

if (ignore && !allow && prefer_ms_hyperv) {
host->flags |= ATA_HOST_IGNORE_ATA;
dev_info(host->dev, "%s detected, ATA device ignore set\n",

_Absolutly_ ( as _minimum_ for SlackWare 14.00 ) need backport requested at 2012-06-08(!) :
( look on sub-string "3.2")
----- Original Message ----- From: "Victor Miasnikov"
To: "Greg KH" ; "Jonathan Nieder" ; "Andy Whitcroft"
Cc: <stable@xxxxxxxxxxxxxxx>; <linux-kernel@xxxxxxxxxxxxxxx>; "KY Srinivasan"; "Mike Sterling"
Sent: Friday, June 08, 2012 1:36 PM
Subject: Re: Re: ToDo: backport to v3.4 , v3.3 , v3.2 patches 1b) db63a4c8115a libata 1) cd006086fa5d ata_piix: defer
disks to the Hyper-V drivers by default Fw: use hv_storvsc instead of ata_piix for IDE disks ( but not for the CD-ROM)

. . .

> > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X
> > Please, _fix_ errors related "use hv_storvsc instead of ata_piix to
> > handle the IDE disks devices ( but not for the CD-ROM)"

i.e. need backport to all actual version after 3.1

cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default

and its prerequisite

db63a4c8115a libata: add a host flag to ignore detected ATA devices

and not forget patch related Bug 52821 :

== ==
----- Original Message ----- From: vvm
To: Andreas
Sent: Wednesday, January 30, 2013 4:20 PM
Subject: FIXed: ef773e1..bec35f4 Re: ata_piix.prefer_ms_hyperv=0 works Fw: Bug 52821 - ata_piix ATA_HOST_IGNORE_ATA for
Hyper-V also affects Virtual PC 7 Or



Still, if there is a way to cleanly identify Hyper-V but not Virtual PC 7, this would be great!

FIXed: ef773e1..bec35f4

Write in

"please, backport to 3.4 . . . 3.6 . . . 3.7"

. . .


. . .

Still, if there is a way to cleanly identify Hyper-V but not Virtual PC 7, this would be great!

FIXed: ef773e1..bec35f4

----- Original Message ----- From: "Jeff Garzik"
To: "Olaf Hering"
Cc: . . . ; "KY Srinivasan"
Sent: Wednesday, November 28, 2012 8:44 PM
Subject: Re: [PATCH] ata_piix: reenable MS Virtual PC guests

On 09/18/2012 11:48 AM, Olaf Hering wrote:
An earlier commit cd006086fa5d91414d8ff9ff2b78fbb593878e3c ("ata_piix:
defer disks to the Hyper-V drivers by default") broke MS Virtual PC
guests. Hyper-V guests and Virtual PC guests have nearly identical DMI
info. As a result the driver does currently ignore the emulated hardware
in Virtual PC guests and defers the handling to hv_blkvsc [ VVM: in current ver kernel -- hv_storvsc ] . Since Virtual
PC does not offer paravirtualized drivers no disks will be found in the

One difference in the DMI info is the product version. This patch adds a
match for MS Virtual PC 2007 and "unignores" the emulated hardware.

This was reported for openSuSE 12.1 in bugzilla:
. . .

Signed-off-by: Olaf Hering

applied. Apologies for missing this one. It was accidentally shifting
into the low-priority pile.

== ==

Andreas 2013-01-30 22:19:21
First appearance:



This should also go to the stable tree, shouldn't it ?
At least 3.8, 3.7 and 3.4

In kernel 3.2 used in

-- Ubuntu 12.4.0 LTS ( after 12.4.2 -- 3.5.X)
-- Debian 7.0

source code related Hyper-V backported from "vanila" Kernel v3.5 ( and someone from hi versions)

Please, ask Support Teams of Debian and Ubuntu for backport

Best regards, Victor Miasnikov


to To Microsoft Hyper-V for Linux Team:

what are mint phrase:
"LIS (Linux Integration Services) 4.0"

If need details -- ask me by e-mail . . .


Again to To Microsoft Hyper-V for Linux Team:

See on MS Forum topic
"Linux VM literally crashes Hyper-V host server with STOP 0x00020001"
and (or)
please, remember, CVE number


To SUSE Hyper-V for Linux Team:

Olaf, I'm received Yours e-mail msg ( answer on my earler msg)

Thanks for answer

Unfortunately Yours ( SUSE/Novel) Bug-Tracker not opened by IE from Win Srv Edtions
I'm try do it from OpenSUSE v12.3 LiveCD but can not boot from it in Hyper-V VM when "Dynamic memory" turn on

See details on

Or ask SUSE Support Team write me by e-mail for detail



I am not found sub-string "Fiber Channel"

As I undestand Linux Kernel roadmap/timeline traditions
need ask by backport needed patches to v3.10

To Microsoft Hyper-V for Linux Team:

Who must do it?

Again Hypev-V sysadmin[s] ?


Sorry, if my msg not full "political correct"

I preffered solve problem as possibily earler, what wait big problems

Sorry, again . . .

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at