Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error in Hyper-V modules hv_vmbus

2,972 views
Skip to first unread message

root

unread,
Apr 30, 2011, 10:50:02 AM4/30/11
to
Hello

I have compiled and installed the new 2.6.39-rc5 linux kernel with
Microsoft Hyper-V modules enabled on my Debian Squeeze system. After a
reboot I get these errors (sorry can post only screenshots because I
can't copy the log):

http://docs.homelinux.org/hv

and system doesn't boot. What's wrong? I think modprobe can't load
hv_vmbus?!?

Regards
Juan Dos Santos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

KY Srinivasan

unread,
Apr 30, 2011, 4:30:03 PM4/30/11
to

> -----Original Message-----
> From: root [mailto:ro...@docs.homelinux.org]
> Sent: Saturday, April 30, 2011 10:40 AM
> To: linux-...@vger.kernel.org; KY Srinivasan
> Subject: Error in Hyper-V modules hv_vmbus
>
> Hello
>
> I have compiled and installed the new 2.6.39-rc5 linux kernel with
> Microsoft Hyper-V modules enabled on my Debian Squeeze system. After a
> reboot I get these errors (sorry can post only screenshots because I
> can't copy the log):

What is the version of the Windows host. I have seen some issues with
older hosts, where the vmbus driver does not get the correct irq. I have
submitted a patch for this (this is yet to be applied by Greg).

Regards,

K. Y

root

unread,
May 1, 2011, 8:40:02 AM5/1/11
to

>
>> -----Original Message-----
>> From: root [mailto:ro...@docs.homelinux.org]
>> Sent: Saturday, April 30, 2011 10:40 AM
>> To: linux-...@vger.kernel.org; KY Srinivasan
>> Subject: Error in Hyper-V modules hv_vmbus
>>
>> Hello
>>
>> I have compiled and installed the new 2.6.39-rc5 linux kernel with
>> Microsoft Hyper-V modules enabled on my Debian Squeeze system. After a
>> reboot I get these errors (sorry can post only screenshots because I
>> can't copy the log):
> What is the version of the Windows host. I have seen some issues with
> older hosts, where the vmbus driver does not get the correct irq. I have
> submitted a patch for this (this is yet to be applied by Greg).
>
> Regards,
>
> K. Y
>

Windows Server Core 2008 R2 with SP2

Regards
Juan Dos Santos

KY Srinivasan

unread,
May 1, 2011, 11:30:02 AM5/1/11
to

> -----Original Message-----
> From: root [mailto:ro...@docs.homelinux.org]
> Sent: Sunday, May 01, 2011 8:37 AM
> To: KY Srinivasan
> Cc: linux-...@vger.kernel.org
> Subject: Re: Error in Hyper-V modules hv_vmbus
>
>
> >
> >> -----Original Message-----
> >> From: root [mailto:ro...@docs.homelinux.org]
> >> Sent: Saturday, April 30, 2011 10:40 AM
> >> To: linux-...@vger.kernel.org; KY Srinivasan
> >> Subject: Error in Hyper-V modules hv_vmbus
> >>
> >> Hello
> >>
> >> I have compiled and installed the new 2.6.39-rc5 linux kernel with
> >> Microsoft Hyper-V modules enabled on my Debian Squeeze system. After a
> >> reboot I get these errors (sorry can post only screenshots because I
> >> can't copy the log):
> > What is the version of the Windows host. I have seen some issues with
> > older hosts, where the vmbus driver does not get the correct irq. I have
> > submitted a patch for this (this is yet to be applied by Greg).
> >
> > Regards,
> >
> > K. Y
> >
>
> Windows Server Core 2008 R2 with SP2

Thank you. I will get back to you after some testing locally.
I have already submitted a patch for dealing with irq allocation
on some windows hosts (yet to be applied). I will verify if this patch fixes your problem.

Regards,

K. Y

KY Srinivasan

unread,
May 3, 2011, 9:50:02 AM5/3/11
to

> -----Original Message-----
> From: root [mailto:ro...@docs.homelinux.org]

> Sent: Sunday, May 01, 2011 8:37 AM
> To: KY Srinivasan
> Cc: linux-...@vger.kernel.org

> Subject: Re: Error in Hyper-V modules hv_vmbus
>
>
> >
> >> -----Original Message-----
> >> From: root [mailto:ro...@docs.homelinux.org]
> >> Sent: Saturday, April 30, 2011 10:40 AM
> >> To: linux-...@vger.kernel.org; KY Srinivasan
> >> Subject: Error in Hyper-V modules hv_vmbus
> >>
> >> Hello
> >>
> >> I have compiled and installed the new 2.6.39-rc5 linux kernel with
> >> Microsoft Hyper-V modules enabled on my Debian Squeeze system. After a
> >> reboot I get these errors (sorry can post only screenshots because I
> >> can't copy the log):
> > What is the version of the Windows host. I have seen some issues with
> > older hosts, where the vmbus driver does not get the correct irq. I have
> > submitted a patch for this (this is yet to be applied by Greg).
> >
> > Regards,
> >
> > K. Y
> >
>
> Windows Server Core 2008 R2 with SP2

This is a known problem and a fix has been submitted - the patch is yet to be applied
though. Once the hv patches that are in the queue are applied, this problem
will be fixed. In the interim, if you want an immediate fix, I could send you the patch
that will apply against the tree you have.

Regards,

K. Y

ro...@docs.homelinux.org

unread,
May 3, 2011, 11:00:02 AM5/3/11
to

Could You send me the patch? So I can test it, I am using the kernel
source from
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc5.tar.bz2,
is the patch compatible with this kernel source?

Hank Janssen

unread,
May 3, 2011, 2:40:02 PM5/3/11
to
> > -----Original Message-----
> > From: ro...@docs.homelinux.org [mailto:ro...@docs.homelinux.org]
> > Sent: Tuesday, May 03, 2011 10:52 AM
> > To: KY Srinivasan
> > Cc: linux-...@vger.kernel.org
> > Subject: RE: Error in Hyper-V modules hv_vmbus
> >
> > On Tue, 3 May 2011 13:42:43 +0000, KY Srinivasan wrote:
> > >> -----Original Message-----
> > >> From: root [mailto:ro...@docs.homelinux.org]
> > >> Sent: Sunday, May 01, 2011 8:37 AM
> > >> To: KY Srinivasan
> > >> Cc: linux-...@vger.kernel.org
> > >> Subject: Re: Error in Hyper-V modules hv_vmbus
> > >>
> > >> Windows Server Core 2008 R2 with SP2
> > >
> > > This is a known problem and a fix has been submitted - the patch is
> > > yet to be applied though. Once the hv patches that are in the queue
> > > are applied, this problem will be fixed. In the interim, if you want
> > > an immediate fix, I could send you the patch that will apply against
> > > the tree you have.
> > >
> > > Regards,
> > >
> > > K. Y
> > >>
> > >> Regards
> > >> Juan Dos Santos
> >
> > Could You send me the patch? So I can test it, I am using the kernel
> > source from
> > http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc5.t
> > ar.bz2, is the patch compatible with this kernel source?
>
> This is a very old version of the hyper-V driver code compared to what is in
> Greg's tree and looking at the code It does not look like the problem you are
> seeing is the problem my patch fixes. We will do some additional testing and
> get back to you. It would be very useful if you can post the dmesg or stack
> trace that can shed additional light on the problem.

Juan,

I just fixed a few issues in Ubuntu 10.10 that might be similar.

I will spin up a debian system and see if I can reproduce the problem and submit a patch
To fix it.

Hank.


Hank Janssen

unread,
May 3, 2011, 2:50:02 PM5/3/11
to

>
> > > -----Original Message-----
> > > From: ro...@docs.homelinux.org [mailto:ro...@docs.homelinux.org]
> > > Sent: Tuesday, May 03, 2011 10:52 AM
> > > To: KY Srinivasan
> > > Cc: linux-...@vger.kernel.org
> > > Subject: RE: Error in Hyper-V modules hv_vmbus
> > >
> > > On Tue, 3 May 2011 13:42:43 +0000, KY Srinivasan wrote:
> > > >> -----Original Message-----
> > > >> From: root [mailto:ro...@docs.homelinux.org]
> > > >> Sent: Sunday, May 01, 2011 8:37 AM
> > > >> To: KY Srinivasan
> > > >> Cc: linux-...@vger.kernel.org
> > > >> Subject: Re: Error in Hyper-V modules hv_vmbus
> > > >>
> > > >> Windows Server Core 2008 R2 with SP2
> > > >
> > > > This is a known problem and a fix has been submitted - the patch
> > > > is yet to be applied though. Once the hv patches that are in the
> > > > queue are applied, this problem will be fixed. In the interim, if
> > > > you want an immediate fix, I could send you the patch that will
> > > > apply against the tree you have.
> > > >
> > > > Regards,
> > > >
> > > > K. Y
> > > >>
> > > >> Regards
> > > >> Juan Dos Santos
> > >
> > > Could You send me the patch? So I can test it, I am using the
> > > kernel source from
> > > http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc5

Juan Dos Santos

unread,
May 3, 2011, 5:40:02 PM5/3/11
to
Hi Hank

Ok thanks, tomorrow I will post dmesg and more debuging stuff about this
problem...

jdoss...@docs.homelinux.org

unread,
May 4, 2011, 5:50:02 AM5/4/11
to

Here is my step by step protocol:

VM configuration:
Host: Windows Server 2008 Core R2 with SP1
Networkcard: Old emulated card
Integratedservices: Shutdown, Timesync, Heartbeat
CPU: 4
Memory: 512 MB
Harddisk: IDE 10 GB

OS Installation:
Debian Squeeze 6.0.1a (2.6.32-5-amd64)
Standard installation without any installation packages

Kernel installation:
aptitude install kernel-package libncurses-dev
cd /usr/src
wget
http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc6.tar.bz2
tar xfvj linux-2.6.39-rc6.tar.bz2
cd linux-2.6.39-rc6/
make clean
make mrproper
cp /boot/config-2.6.32-5-amd64 .config
make menuconfig

{Divice Drivers -> Stagin Drivers -> <M> Microsoft Hyper-V client
drivers}
Here You can find the .config file http://docs.homelinux.org/hv/.config


export CUNCURRENCY_LEVEL=4
make-kpkg --append-to-version "-hyperv" --revision "1" --us --uc
--initrd kernel_image kernel_headers
cd ..
dpkg -i linux-image-2.6.39-rc6-hyperv_1_amd64.deb
linux-headers-2.6.39-rc6-hyperv_1_amd64.deb
ls -l /boot/
total 27640
-rw-r--r-- 1 root root 106088 Mar 8 01:18 config-2.6.32-5-amd64
-rw-r--r-- 1 root root 125214 May 4 11:31 config-2.6.39-rc6-hyperv
drwxr-xr-x 3 root root 4096 May 4 12:56 grub
-rw-r--r-- 1 root root 9095609 May 4 09:10 initrd.img-2.6.32-5-amd64
-rw-r--r-- 1 root root 10388314 May 4 12:56
initrd.img-2.6.39-rc6-hyperv
-rw-r--r-- 1 root root 1662514 Mar 8 01:18 System.map-2.6.32-5-amd64
-rw-r--r-- 1 root root 1839410 May 4 12:52
System.map-2.6.39-rc6-hyperv
-rw-r--r-- 1 root root 2418720 Mar 8 01:12 vmlinuz-2.6.32-5-amd64
-rw-r--r-- 1 root root 2590800 May 4 12:52 vmlinuz-2.6.39-rc6-hyperv
reboot

After the reboot I get the "INFO: task modprobe:307 blocked for more
than 120 seconds." message
and boot is haning for 170 seconds, here are the logs:
http://docs.homelinux.org/hv/syslog
http://docs.homelinux.org/hv/messages
http://docs.homelinux.org/hv/dmesg

lsmod | grep hv_
hv_timesource 1055 0 [permanent]
hv_vmbus 48554 1

In the logs and with lsmod i see the timesource module running, but the
time is not in sync with the windows host.
Shutdown function also dosn't work, seems that nothing of the
integrated components are working..hv_netvsc,hv_blkvsc,hv_storvsc are
not
loaded?! But modinfo provides information:

modinfo hv_vmbus
filename:
/lib/modules/2.6.39-rc6-hyperv/kernel/drivers/staging/hv/hv_vmbus.ko
version: 3.1
license: GPL
srcversion: 334F59AED9605F8C3B7696F
alias: pci:v00001414d00005353sv*sd*bc*sc*i*
alias:
dmi*:svn*MicrosoftCorporation*:pn*VirtualMachine*:rn*VirtualMachine*:
depends:
staging: Y
vermagic: 2.6.39-rc6-hyperv SMP mod_unload modversions
parm: vmbus_irq:int
parm: vmbus_loglevel:int

modinfo hv_timesource
filename:
/lib/modules/2.6.39-rc6-hyperv/kernel/drivers/staging/hv/hv_timesource.ko
license: GPL
author: K. Y. Srinivasan <ksrin...@novell.com>
description: HyperV based clocksource
alias: pci:v00001414d00005353sv*sd*bc*sc*i*
alias:
dmi*:svn*MicrosoftCorporation*:pn*VirtualMachine*:rn*VirtualMachine*:
depends:
staging: Y
vermagic: 2.6.39-rc6-hyperv SMP mod_unload modversions

modinfo hv_netvsc
filename:
/lib/modules/2.6.39-rc6-hyperv/kernel/drivers/staging/hv/hv_netvsc.ko
description: Microsoft Hyper-V network driver
version: 3.1
license: GPL
srcversion: EA7C82EAB799B90B4F6BFA6
alias: pci:v00001414d00005353sv*sd*bc*sc*i*
alias:
dmi*:svn*MicrosoftCorporation*:pn*VirtualMachine*:rn*VirtualMachine*:
depends: hv_vmbus
staging: Y
vermagic: 2.6.39-rc6-hyperv SMP mod_unload modversions
parm: ring_size:Ring buffer size (# of pages) (int)

modinfo hv_storvsc
filename:
/lib/modules/2.6.39-rc6-hyperv/kernel/drivers/staging/hv/hv_storvsc.ko
description: Microsoft Hyper-V virtual storage driver
version: 3.1
license: GPL
srcversion: 23688D30D5A66982D2BB67F
depends: scsi_mod,hv_vmbus
staging: Y
vermagic: 2.6.39-rc6-hyperv SMP mod_unload modversions
parm: storvsc_ringbuffer_size:Ring buffer size (bytes) (int)

modinfo hv_blkvsc
filename:
/lib/modules/2.6.39-rc6-hyperv/kernel/drivers/staging/hv/hv_blkvsc.ko
description: Microsoft Hyper-V virtual block driver
version: 3.1
license: GPL
srcversion: 5B375CF1D6F5581A05B1026
depends: scsi_mod,hv_vmbus
staging: Y
vermagic: 2.6.39-rc6-hyperv SMP mod_unload modversions
parm: blkvsc_ringbuffer_size:int
parm: ring_size:Ring buffer size (in bytes)


After that I enabled the synthetic network card, but also here..it
doesn't work and I don't see any hv_netvsc
module loaded, so I tried to load it "by hand" with modprobe
hv_netvsc..but I get a modprobe timeout and nothing happens..

Can someone repruduce it? Is there a patch for kernel linux-2.6.39-rc6?

Hank Janssen

unread,
May 4, 2011, 12:10:01 PM5/4/11
to



> -----Original Message-----
> From: jdoss...@docs.homelinux.org
> [mailto:jdoss...@docs.homelinux.org]
> Sent: Wednesday, May 04, 2011 2:48 AM
> To: Hank Janssen
> Cc: KY Srinivasan; linux-...@vger.kernel.org
> Subject: Re: Error in Hyper-V modules hv_vmbus
> > Hank.
>
> Here is my step by step protocol:

Thanks for the detailed setup. I will be trying it with this.

> lsmod | grep hv_
> hv_timesource 1055 0 [permanent]
> hv_vmbus 48554 1
>
> In the logs and with lsmod i see the timesource module running, but
> the
> time is not in sync with the windows host.
> Shutdown function also dosn't work, seems that nothing of the
> integrated components are working..hv_netvsc,hv_blkvsc,hv_storvsc are
> not
> loaded?! But modinfo provides information:

Timesource makes sure that the clock does not drift and uses Hyper-V for
Its stable time source.

The setting of the clock equal to the host is provided by the hv_utils.ko
Module. This module also provides heartbeat, shutdown and KVP functionality.


> After that I enabled the synthetic network card, but also here..it
> doesn't work and I don't see any hv_netvsc
> module loaded, so I tried to load it "by hand" with modprobe
> hv_netvsc..but I get a modprobe timeout and nothing happens..

I should know more in the next day or so when I get a VM up and running.

It works fine on Ubuntu, I submitted a few patches to them a few weeks ago
To fix some other problems (these patches are already in mainline)

Hank.

jdoss...@docs.homelinux.org

unread,
May 5, 2011, 8:10:02 AM5/5/11
to
Hi Hank

Yes in ubuntu server (i tested the newest version 11.04) there is no
problem, the hyper-v modules are compiled and activated
as default in the released kernel (2.6.38-8), network, timesync and all
others integrated components are working fine. This is the lsmod
output:
lsmod | grep hv_
hv_utils 12850 0
hv_netvsc 36467 0
hv_timesource 12423 0 [permanent]
hv_vmbus 50431 2 hv_utils,hv_netvsc

Now I have downloaded the newest rc kernel and done the same steps like
in the debian installation, after a reboot I get same errors and
integrated components failed to works...Now I check the hyper-v modules
source from 2.6.38-8 ubuntu kernel and the new one

jdoss...@docs.homelinux.org

unread,
May 5, 2011, 2:10:02 PM5/5/11
to
On Thu, 05 May 2011 14:05:11 +0200, jdoss...@docs.homelinux.org
wrote:

Ok, now I have setup again debian 6.0.1a and compiled the 2.6.39-rc6
kernel but with the hyper-v staging drivers from ubuntu kernel 2.6.38-8
source (just replaced the hv directory, I know maybe it's dirty :) ).
But now all is working fine! I have now a debian system with kernel
2.6.39-rc6 with all integrated components running..looks that the
hyper-v modules in the ubuntu kernel are more stable that in the newest
official rc kernel?!

Regards
Juan

Hank Janssen

unread,
May 5, 2011, 2:50:01 PM5/5/11
to
Juan,

I just spun up the debian VM and I downloaded the latest staging and the rc5 that
failed for you and I was about to compile it.

Let me see what happened between rc5 and rc6 to see what might have solved the
problem you were seeing.

I would say that in general the older kernels (certainly 35 and 36) are more stable
than mainline for our drivers. We are making so many changes to mainline right now
and that sometimes there are a few bugs that creep in that we have not caught yet.

They are not so much functional as structural changes.

But I would not recommend running it in production unless you like to live
dangerously. :)

Hank.



jdoss...@docs.homelinux.org

unread,
May 9, 2011, 11:50:03 AM5/9/11
to
Hello

I am using the stable 2.6.38.5 kernel with hyper-v modules enabled. I
get always this error on boot and if I enable hv_blkvsc with modprobe:

[ 7.117924] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[ 7.118592] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[ 7.119247] STORVSC: QUERY_PROPERTIES_OPERATION...
[ 7.120065] STORVSC: END_INITIALIZATION_OPERATION...
[ 7.121033] STORVSC: **** storage channel up and running!! ****
[ 7.121382] register_blkdev: cannot get major 3 for ide
[ 7.121697] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev()
failed! ret -16
[ 7.122034] STORVSC: disabling storage device (ffff88003c6c2540)...
[ 7.122360] STORVSC: removing storage device (ffff88003c6c2540)...
[ 7.122676] STORVSC: storage device (ffff88003c6c2540) safe to
remove
[ 7.123343] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for
device vmbus_0_9 (ffff88003bd620c0) on driver blkvsc (-16)...
[ 7.124070] blkvsc: probe of vmbus_0_9 failed with error -16
[ 7.124412] VMBUS_DRV: vmbus_child_device_register() ERROR!! unable
to register child device (ffff88003bd620c0)
[ 7.124750] VMBUS: vmbus_process_offer() ERROR!! unable to add child
device object (relid 1)
[ 7.125112] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}

here is the complete log:

[ 3.516112] hv_vmbus: module is from the staging directory, the
quality is unknown, you have been warned.
[ 3.518627] VMBUS_DRV: Vmbus initializing.... current log level
0x1f1f0006 (1f1f,6)
[ 3.519330] VMBUS: +++++++ HV Driver version = 3.1 +++++++
[ 3.519968] VMBUS: +++++++ Vmbus supported version = 13 +++++++
[ 3.520598] VMBUS: +++++++ Vmbus using SINT 2 +++++++
[ 3.521220] VMBUS: Windows hypervisor detected! Retrieving more
info...
[ 3.521827] VMBUS: Vendor ID: Microsoft Hv
[ 3.522427] VMBUS: Interface ID: Hv#1
[ 3.523054] VMBUS: OS Build:7601-6.1-17-0.17514
[ 3.523952] hv_vmbus: module is from the staging directory, the
quality is unknown, you have been warned.
[ 3.562837] VMBUS: Hypercall page VA=ffffc90000698000, PA=0x3cc02000
[ 3.564736] VMBUS_DRV: irq 0x5 vector 0x35
[ 3.565484] VMBUS: SynIC version: 1
[ 3.566578] VMBUS: Vmbus connected!!
[ 3.567613] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={c5295816-f63a-4d5f-8d1a4daf999ca185}
[ 3.568640] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={c5295816-f63a-4d5f-8d1a4daf999ca185}
[ 3.569484] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={c5295816-f63a-4d5f-8d1a4daf999ca185}
[ 3.570576] VMBUS: Channel offer notification - child relid 1
monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5}
instance {00000000-0000-8899-0000000000000000}
[ 3.599128] hv_timesource: module is from the staging directory, the
quality is unknown, you have been warned.
[ 3.600004] Registering HyperV clock source
[ 3.600670] Switching to clocksource hyperv_clocksource
[ 3.614612] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 3.615370] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 3.616158] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 3.616852] VMBUS_DRV: child device (ffff880030360cc0) registered
[ 3.617736] VMBUS: Channel offer notification - child relid 2
monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[ 3.619418] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 3.620284] ACPI: Power Button [PWRF]
[ 3.625003] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
[ 3.625767] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
[ 3.626525] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
[ 3.627238] VMBUS_DRV: child device (ffff8800303654c0) registered
[ 3.627866] VMBUS: Channel offer notification - child relid 4
monitor id 255 allocated 0, type {57164f39-9115-4e78-ab55382f3bd5422d}
instance {fd149e91-82e0-4a7d-afa62a4166cbd7c0}
[ 3.629192] piix4_smbus 0000:00:07.3: SMBus base address
uninitialized - upgrade BIOS or use force_addr=0xaddr
[ 3.630097] ACPI: acpi_idle registered with cpuidle
[ 3.637139] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={57164f39-9115-4e78-ab55382f3bd5422d}
[ 3.644455] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={57164f39-9115-4e78-ab55382f3bd5422d}
[ 3.645335] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={57164f39-9115-4e78-ab55382f3bd5422d}
[ 3.646819] VMBUS_DRV: child device (ffff880030364cc0) registered
[ 3.647487] VMBUS: Channel offer notification - child relid 5
monitor id 255 allocated 0, type {0e0b6031-5213-4934-818b38d90ced39db}
instance {b6650ff7-33bc-4840-8048e0676786f393}
[ 3.648834] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={0e0b6031-5213-4934-818b38d90ced39db}
[ 3.649577] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={0e0b6031-5213-4934-818b38d90ced39db}
[ 3.650332] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={0e0b6031-5213-4934-818b38d90ced39db}
[ 3.651058] VMBUS_DRV: child device (ffff8800303650c0) registered
[ 3.651468] VMBUS: Channel offer notification - child relid 6
monitor id 255 allocated 0, type {9527e630-d0ae-497b-adcee80ab0175caf}
instance {2dd1ce17-079e-403c-b352a1921ee207ee}
[ 3.652687] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={9527e630-d0ae-497b-adcee80ab0175caf}
[ 3.654270] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={9527e630-d0ae-497b-adcee80ab0175caf}
[ 3.655900] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={9527e630-d0ae-497b-adcee80ab0175caf}
[ 3.658037] VMBUS_DRV: child device (ffff8800303644c0) registered
[ 3.658733] VMBUS: Channel offer notification - child relid 7
monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
instance {4fb6d35f-f9d0-49e7-9d9917cfb16ab18e}
[ 3.659676] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
[ 3.660485] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
[ 3.661416] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
[ 3.662278] VMBUS_DRV: child device (ffff880030365cc0) registered
[ 3.663303] VMBUS: Channel offer notification - child relid 8
monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e}
instance {4e4aafbd-b96c-4b7a-932ac50a9082637a}
[ 3.664149] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={f8615163-df3e-46c5-913ff2d2f965ed0e}
[ 3.664542] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={f8615163-df3e-46c5-913ff2d2f965ed0e}
[ 3.664986] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={f8615163-df3e-46c5-913ff2d2f965ed0e}
[ 3.665505] VMBUS_DRV: child device (ffff8800303660c0) registered
[ 3.665968] VMBUS: channel <ffff88003bbf3e00> open success!!
[ 3.666894] VMBUS: Heartbeat channel functionality initialized
[ 3.667694] VMBUS: channel <ffff88003bbf3a00> open success!!
[ 3.668650] VMBUS: Shutdown channel functionality initialized
[ 3.669341] VMBUS: channel <ffff88003babae00> open success!!
[ 3.670032] VMBUS: Timesync channel functionality initialized
[ 3.672252] hv_netvsc: module is from the staging directory, the
quality is unknown, you have been warned.
[ 3.674566] NETVSC_DRV: Netvsc initializing....
[ 3.675285] VMBUS_DRV: child driver (ffffffffa020a2b0) registering -
name netvsc
[ 3.676064] VMBUS_DRV: device object (ffff880030366048) set to
driver object (ffffffffa020a340)
[ 3.677052] VMBUS: channel <ffff88003bab9600> open success!!
[ 3.677812] NETVSC: *** NetVSC channel opened successfully! ***
[ 3.678541] NETVSC: Sending NvspMessageTypeInit...
[ 3.679260] NETVSC: NvspMessageTypeInit status(1) max mdl chain (34)
[ 3.679939] NETVSC: Sending NvspMessage1TypeSendNdisVersion...
[ 3.680761] NETVSC: Establishing receive buffer's GPADL...
[ 3.681291] NETVSC: Sending NvspMessage1TypeSendReceiveBuffer...
[ 3.682497] NETVSC: Receive sections info (count 1, offset 0,
endoffset 1048000, suballoc size 1600, num suballocs 655)
[ 3.683131] NETVSC: Establishing send buffer's GPADL...
[ 3.689950] NETVSC: Sending NvspMessage1TypeSendSendBuffer...
[ 3.690549] NETVSC: *** NetVSC channel handshake result - 0 ***
[ 3.691235] NETVSC: Device 0xffff88003bde5c40 mac addr
00:15:5d:21:87:84
[ 3.691602] NETVSC: Device 0xffff88003bde5c40 link state up
[ 3.692293] eth0: Dropping NETIF_F_SG since no checksum feature.
[ 3.694538] VMBUS: Channel offer notification - child relid 1
monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5}
instance {00000000-0000-8899-0000000000000000}
[ 3.694976] hv_utils: module is from the staging directory, the
quality is unknown, you have been warned.
[ 3.695862] Registering HyperV Utility Driver
[ 3.697312] VMBUS: Channel offer notification - child relid 2
monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[ 3.698144] VMBUS: Channel offer notification - child relid 4
monitor id 255 allocated 0, type {57164f39-9115-4e78-ab55382f3bd5422d}
instance {fd149e91-82e0-4a7d-afa62a4166cbd7c0}
[ 3.699521] VMBUS: Channel offer notification - child relid 5
monitor id 255 allocated 0, type {0e0b6031-5213-4934-818b38d90ced39db}
instance {b6650ff7-33bc-4840-8048e0676786f393}
[ 3.700426] VMBUS: Channel offer notification - child relid 6
monitor id 255 allocated 0, type {9527e630-d0ae-497b-adcee80ab0175caf}
instance {2dd1ce17-079e-403c-b352a1921ee207ee}
[ 3.701038] VMBUS: Channel offer notification - child relid 7
monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
instance {4fb6d35f-f9d0-49e7-9d9917cfb16ab18e}
[ 3.701672] VMBUS: Channel offer notification - child relid 8
monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e}
instance {4e4aafbd-b96c-4b7a-932ac50a9082637a}
[ 6.906633] Adding 901116k swap on /dev/hda5. Priority:-1 extents:1
across:901116k
[ 6.973454] EXT3-fs (hda1): using internal journal
[ 7.005687] loop: module loaded
[ 7.020226] hv_blkvsc: module is from the staging directory, the
quality is unknown, you have been warned.
[ 7.029329] BLKVSC_DRV: Blkvsc initializing....
[ 7.030109] BLKVSC: max io outstd 226
[ 7.030759] VMBUS_DRV: child driver (ffffffffa0225880) registering -
name blkvsc
[ 7.031504] VMBUS_DRV: device object (ffff880030360c48) set to
driver object (ffffffffa0225910)
[ 7.033657] VMBUS: channel <ffff88002fb23400> open success!!
[ 7.034560] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[ 7.036307] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[ 7.037643] STORVSC: QUERY_PROPERTIES_OPERATION...
[ 7.038987] STORVSC: END_INITIALIZATION_OPERATION...
[ 7.041889] STORVSC: **** storage channel up and running!! ****
[ 7.042579] register_blkdev: cannot get major 3 for ide
[ 7.043261] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev()
failed! ret -16
[ 7.044324] STORVSC: disabling storage device (ffff88003c6c3ec0)...
[ 7.044661] STORVSC: removing storage device (ffff88003c6c3ec0)...
[ 7.044982] STORVSC: storage device (ffff88003c6c3ec0) safe to
remove
[ 7.046878] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for
device vmbus_0_1 (ffff880030360cc0) on driver blkvsc (-16)...
[ 7.047634] blkvsc: probe of vmbus_0_1 failed with error -16
[ 7.048311] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.049321] VMBUS: Channel offer notification - child relid 1
monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5}
instance {00000000-0000-8899-0000000000000000}
[ 7.050647] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.051399] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.052206] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.052925] VMBUS_DRV: device object (ffff88003bd61048) set to
driver object (ffffffffa0225910)
[ 7.053736] VMBUS: Channel offer notification - child relid 2
monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[ 7.061518] hv_storvsc: module is from the staging directory, the
quality is unknown, you have been warned.
[ 7.064960] STORVSC_DRV: Storvsc initializing....
[ 7.066013] STORVSC: max io 226, currently 128
[ 7.066028]
[ 7.066921] STORVSC_DRV: request extension size 72, max outstanding
reqs 226
[ 7.067654] VMBUS_DRV: child driver (ffffffffa022f3f0) registering -
name storvsc
[ 7.068391] VMBUS: Channel offer notification - child relid 4
monitor id 255 allocated 0, type {57164f39-9115-4e78-ab55382f3bd5422d}
instance {fd149e91-82e0-4a7d-afa62a4166cbd7c0}
[ 7.069853] VMBUS: Channel offer notification - child relid 5
monitor id 255 allocated 0, type {0e0b6031-5213-4934-818b38d90ced39db}
instance {b6650ff7-33bc-4840-8048e0676786f393}
[ 7.070352] VMBUS: Channel offer notification - child relid 6
monitor id 255 allocated 0, type {9527e630-d0ae-497b-adcee80ab0175caf}
instance {2dd1ce17-079e-403c-b352a1921ee207ee}
[ 7.071337] VMBUS_DRV: device object (ffff880030365c48) set to
driver object (ffffffffa022f480)
[ 7.072086] VMBUS: Channel offer notification - child relid 7
monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
instance {4fb6d35f-f9d0-49e7-9d9917cfb16ab18e}
[ 7.072936] VMBUS: Channel offer notification - child relid 8
monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e}
instance {4e4aafbd-b96c-4b7a-932ac50a9082637a}
[ 7.074734] VMBUS: channel <ffff88003c69e800> open success!!
[ 7.075433] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[ 7.076154] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[ 7.076494] VMBUS: channel <ffff88003baba000> open success!!
[ 7.076823] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[ 7.077157] STORVSC: QUERY_PROPERTIES_OPERATION...
[ 7.077482] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[ 7.077809] STORVSC: END_INITIALIZATION_OPERATION...
[ 7.078149] STORVSC: QUERY_PROPERTIES_OPERATION...
[ 7.078476] STORVSC: **** storage channel up and running!! ****
[ 7.078806] register_blkdev: cannot get major 3 for ide
[ 7.079279] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev()
failed! ret -16
[ 7.079619] STORVSC: disabling storage device (ffff88002f979740)...
[ 7.079946] STORVSC: removing storage device (ffff88002f979740)...
[ 7.080298] STORVSC: storage device (ffff88002f979740) safe to
remove
[ 7.080627] STORVSC: END_INITIALIZATION_OPERATION...
[ 7.081382] STORVSC: **** storage channel up and running!! ****
[ 7.082057] scsi0 : storvsc_host_t
[ 7.083016] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for
device vmbus_0_8 (ffff88003bd610c0) on driver blkvsc (-16)...
[ 7.083673] blkvsc: probe of vmbus_0_8 failed with error -16
[ 7.084374] VMBUS_DRV: vmbus_child_device_register() ERROR!! unable
to register child device (ffff88003bd610c0)
[ 7.085073] VMBUS: vmbus_process_offer() ERROR!! unable to add child
device object (relid 1)
[ 7.093085] scsi scan: INQUIRY result too short (5), using 36
[ 7.094476] scsi scan: INQUIRY result too short (5), using 36
[ 7.099863] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.102080] VMBUS: Channel offer notification - child relid 1
monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5}
instance {00000000-0000-8899-0000000000000000}
[ 7.106701] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.107779] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.108693] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 7.109429] VMBUS_DRV: device object (ffff88003bd62048) set to
driver object (ffffffffa0225910)
[ 7.110190] VMBUS: Channel offer notification - child relid 2
monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[ 7.111430] VMBUS: Channel offer notification - child relid 4
monitor id 255 allocated 0, type {57164f39-9115-4e78-ab55382f3bd5422d}
instance {fd149e91-82e0-4a7d-afa62a4166cbd7c0}
[ 7.112965] VMBUS: Channel offer notification - child relid 5
monitor id 255 allocated 0, type {0e0b6031-5213-4934-818b38d90ced39db}
instance {b6650ff7-33bc-4840-8048e0676786f393}
[ 7.113727] VMBUS: Channel offer notification - child relid 6
monitor id 255 allocated 0, type {9527e630-d0ae-497b-adcee80ab0175caf}
instance {2dd1ce17-079e-403c-b352a1921ee207ee}
[ 7.114877] VMBUS: Channel offer notification - child relid 7
monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
instance {4fb6d35f-f9d0-49e7-9d9917cfb16ab18e}
[ 7.116315] VMBUS: Channel offer notification - child relid 8
monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e}
instance {4e4aafbd-b96c-4b7a-932ac50a9082637a}
[ 7.117276] VMBUS: channel <ffff88002fb21200> open success!!
[ 7.117924] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[ 7.118592] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[ 7.119247] STORVSC: QUERY_PROPERTIES_OPERATION...
[ 7.120065] STORVSC: END_INITIALIZATION_OPERATION...
[ 7.121033] STORVSC: **** storage channel up and running!! ****
[ 7.121382] register_blkdev: cannot get major 3 for ide
[ 7.121697] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev()
failed! ret -16
[ 7.122034] STORVSC: disabling storage device (ffff88003c6c2540)...
[ 7.122360] STORVSC: removing storage device (ffff88003c6c2540)...
[ 7.122676] STORVSC: storage device (ffff88003c6c2540) safe to
remove
[ 7.123343] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for
device vmbus_0_9 (ffff88003bd620c0) on driver blkvsc (-16)...
[ 7.124070] blkvsc: probe of vmbus_0_9 failed with error -16
[ 7.124412] VMBUS_DRV: vmbus_child_device_register() ERROR!! unable
to register child device (ffff88003bd620c0)
[ 7.124750] VMBUS: vmbus_process_offer() ERROR!! unable to add child
device object (relid 1)
[ 7.125112] VMBUS_DRV: generating uevent -
VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[ 10.125751] sshd (803): /proc/803/oom_adj is deprecated, please use
/proc/803/oom_score_adj instead.
[ 20.240021] eth0: no IPv6 routers present

I am using debian squeeze as OS and one virtual disk (hda). What's the
problem here? I tried also with boot parameter noprobe but without
success.

Is the problem that the blkvsc module is loaded at last?? How I can fix
that?

0 new messages