[gentoo-user-ru] Re[3]: [gentoo-user-ru] Сборка ядра 2.6.32.3 для гостевой системы под Hyper-V

[Konstantin Astafjev <konstantin@astafjev.com>]

Hi,

Sunday, January 17, 2010, 15:21:06, you wrote:
> Я уже пробовал заменить в файле .config параметры CONFIG_HYPERV,
> CONFIG_HYPERV_STORAGE, CONFIG_HYPERV_BLOCK, CONFIG_HYPERV_NET на "y", но
> обратил внимание что модули всё равно устанавливаются в
> /lib/modules/2.6.32.3/kernel/drivers/staging/hv/ и полученное ядро при
> загрузке дисков не обнаружило.

> Возможно это произошло потому что я вообще отключил "Serial ATA (prod) and
> Parallel ATA (experimental) drivers", побоявшись, что сначала диск определится
> каким-нибудь другим драйвером.

> Например, сейчас у меня диск определился с модулем "ata_piix" как /dev/sda, но
> подгрузив модули:

> # modprobe hv_vmbus
> # modprobe hv_blkvsc
> # ata_id[7372]: HDIO_GET_IDENTITY failed for '/dev/.tmp-block-3:0'

> обнаружилось старое устройство /dev/sda, как /dev/hda.

> Попытаюсь сейчас повторно изменить вышеуказанные параметры на "y" но вместе с
> CONFIG_ATA=y

Не получилось. Пробовал собрать initrd (mkinitrd с параметрами --with и/или
--preload) но ядро отказалось найти диск.

Пришлось использовать старый IDE CONFIG_BLK_DEV_PIIX=y.
Потом уже в запущеной системе подгружая первый модуль получаю:

[   14.179156] hv_vmbus: module is from the staging directory, the quality is unknown, you have been warned.
[   14.181793] VMBUS_DRV: Vmbus initializing.... current log level 0x1f1f0006 (1f1f,6)
[   14.181797] VMBUS: +++++++ Build Date=Jan 17 2010 17:11:15 +++++++
[   14.181799] VMBUS: +++++++ Build Description=Version 2.0 +++++++
[   14.181802] VMBUS: +++++++ Vmbus supported version = 13 +++++++
[   14.181804] VMBUS: +++++++ Vmbus using SINT 2 +++++++
[   14.181811] VMBUS: Windows hypervisor detected! Retrieving more info...
[   14.181816] VMBUS: Vendor ID: Microsoft Hv
[   14.181821] VMBUS: Interface ID: Hv#1
[   14.181826] VMBUS: OS Build:7600-6.1-16-0.16385
[   14.181962] VMBUS: Hypercall page VA=ffffc900011b3000, PA=0x105a37000
[   14.185559] VMBUS_DRV: irq 0x5 vector 0x35
[   14.185565] VMBUS: SynIC version: 1
[   14.200748] VMBUS: Vmbus connected!!
[   14.201014] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={c5295816-f63a-4d5f-8d1a4daf999ca185}
[   14.203033] VMBUS: Channel offer notification - child relid 1 monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5} instance {00000000-0000-8899-0000000000000000}
[   14.203560] VMBUS: Channel offer notification - child relid 2 monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a} instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[   14.203805] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[   14.203826] VMBUS_DRV: child device (ffff880105950a48) registered
[   14.204045] VMBUS: Channel offer notification - child relid 9 monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f} instance {5b5b2d95-0a3a-42c4-a31d2f47c685e1a6}
[   14.204112] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a}
[   14.204146] VMBUS_DRV: child device (ffff880105953a48) registered
[   14.204323] VMBUS: Channel offer notification - child relid 10 monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e} instance {a2b5dbfa-52c7-4d1e-b46678f5643b728f}
[   14.204380] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={ba6163d9-04a1-4d29-b60572e2ffb1dc7f}
[   14.204415] VMBUS_DRV: child device (ffff880105950648) registered
[   14.205965] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={f8615163-df3e-46c5-913ff2d2f965ed0e}
[   14.206170] VMBUS_DRV: child device (ffff880105950448) registered

подгружая второй:

[   14.238245] hv_storvsc: module is from the staging directory, the quality is unknown, you have been warned.
[   14.239590] STORVSC_DRV: Storvsc initializing....
[   14.239593] STORVSC: max io 107, currently 64
[   14.239594]
[   14.239595] STORVSC_DRV: request extension size 72, max outstanding reqs 107
[   14.239598] VMBUS_DRV: child driver (ffffffffa00175b0) registering - name storvsc
[   14.239613] VMBUS_DRV: device object (ffff880105950780) set to driver object (ffffffffa0017640)
[   14.240320] VMBUS: channel <ffff880105953400> open success!!
[   14.240322] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[   14.240629] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[   14.240731] STORVSC: QUERY_PROPERTIES_OPERATION...
[   14.240769] STORVSC: END_INITIALIZATION_OPERATION...
[   14.240807] STORVSC: **** storage channel up and running!! ****
[   14.240809] scsi0 : storvsc_host_t
[   14.241109] scsi scan: INQUIRY result too short (5), using 36
[   14.241906] VMBUS: Channel offer notification - child relid 1 monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5} instance {00000000-0000-8899-0000000000000000}
[   14.242124] VMBUS: Channel offer notification - child relid 2 monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a} instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[   14.242716] VMBUS: Channel offer notification - child relid 9 monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f} instance {5b5b2d95-0a3a-42c4-a31d2f47c685e1a6}
[   14.243774] VMBUS: Channel offer notification - child relid 10 monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e} instance {a2b5dbfa-52c7-4d1e-b46678f5643b728f}

и третий, я так понимаю самый интересный для меня ругается:

[   14.268475] hv_blkvsc: module is from the staging directory, the quality is unknown, you have been warned.
[   14.270132] BLKVSC_DRV: Blkvsc initializing....
[   14.270140] BLKVSC: max io outstd 226
[   14.270144] VMBUS_DRV: child driver (ffffffffa0023fb0) registering - name blkvsc
[   14.270174] VMBUS_DRV: device object (ffff880105950b80) set to driver object (ffffffffa0024040)
[   14.271124] VMBUS: channel <ffff880105953c00> open success!!
[   14.271127] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[   14.271381] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[   14.271463] STORVSC: QUERY_PROPERTIES_OPERATION...
[   14.271523] STORVSC: END_INITIALIZATION_OPERATION...
[   14.271582] STORVSC: **** storage channel up and running!! ****
[   14.271593] register_blkdev: cannot get major 3 for ide
[   14.271596] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
[   14.271600] STORVSC: disabling storage device (ffff880107031a40)...
[   14.271602] STORVSC: removing storage device (ffff880107031a40)...
[   14.271605] STORVSC: storage device (ffff880107031a40) safe to remove
[   14.271844] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for device vmbus_0_1 (ffff880105950a48) on driver blkvsc (-16)...
[   14.271874] blkvsc: probe of vmbus_0_1 failed with error -16
[   14.272344] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[   14.273096] VMBUS: Channel offer notification - child relid 1 monitor id 0 allocated 1, type {32412632-86cb-44a2-9b5c50d1417354f5} instance {00000000-0000-8899-0000000000000000}
[   14.273585] VMBUS: Channel offer notification - child relid 2 monitor id 255 allocated 0, type {cfa8b69e-5b4a-4cc0-b98b8ba1a1f3f95a} instance {58f75a6d-d949-4320-99e1a2a2576d581c}
[   14.273828] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}
[   14.273861] VMBUS_DRV: device object (ffff880105953180) set to driver object (ffffffffa0024040)
[   14.274129] VMBUS: Channel offer notification - child relid 9 monitor id 1 allocated 1, type {ba6163d9-04a1-4d29-b60572e2ffb1dc7f} instance {5b5b2d95-0a3a-42c4-a31d2f47c685e1a6}
[   14.274331] VMBUS: Channel offer notification - child relid 10 monitor id 2 allocated 1, type {f8615163-df3e-46c5-913ff2d2f965ed0e} instance {a2b5dbfa-52c7-4d1e-b46678f5643b728f}
[   14.282116] VMBUS: channel <ffff880105953c00> open success!!
[   14.282120] STORVSC: BEGIN_INITIALIZATION_OPERATION...
[   14.282196] STORVSC: QUERY_PROTOCOL_VERSION_OPERATION...
[   14.282268] STORVSC: QUERY_PROPERTIES_OPERATION...
[   14.282322] STORVSC: END_INITIALIZATION_OPERATION...
[   14.282376] STORVSC: **** storage channel up and running!! ****
[   14.282381] register_blkdev: cannot get major 3 for ide
[   14.282383] BLKVSC_DRV: blkvsc_probe() ERROR!! register_blkdev() failed! ret -16
[   14.282387] STORVSC: disabling storage device (ffff880107031e00)...
[   14.282389] STORVSC: removing storage device (ffff880107031e00)...
[   14.282392] STORVSC: storage device (ffff880107031e00) safe to remove
[   14.284682] VMBUS_DRV: vmbus_probe() ERROR!! probe() failed for device vmbus_0_5 (ffff880105953048) on driver blkvsc (-16)...
[   14.284703] blkvsc: probe of vmbus_0_5 failed with error -16
[   14.284709] VMBUS_DRV: vmbus_child_device_register() ERROR!! unable to register child device (ffff880105953048)
[   14.284712] VMBUS: VmbusChannelProcessOffer() ERROR!! unable to add child device object (relid 1)
[   14.284830] VMBUS_DRV: generating uevent - VMBUS_DEVICE_CLASS_GUID={32412632-86cb-44a2-9b5c50d1417354f5}

Насколько я понял третий модуль hv_blkvsc подгрузился но не смог нормально
начать работу, так как диск уже используется старым piix'ом. Поправьте меня
если я неправильно интерпретировал dmesg.

Кому-нибудь из присутствующих доводилось устанавливать Gentoo под Hyper-V?
Кто-нибудь делал какие-либо замеры производительности систем используя разные
модули block devices? Поверхностный поиск в Google результатов мне пока не
дал.

-- 
Konstantin