[ipxe-devel] SANBOOT/SANHOOK VMWARE Esxi 6.5 EFI

[tiroNET::Martin Lugger]

HI ipxe developers,
it seems, that the support of SANBOOT EFI on VMWARE ESXi 6.5 on a "x86_x64 VM" and a "i386 VM" is not working
ON the Bios based machines in VMWARE and on physical computers it is working well!

I get the error "COULD NOT DESCRIBE SAN DEVICES: Operation not supported (http://ipxe.org/3c222083)

I build the IPXE.EFI binaries via Rom-O-Matic website with the default settings.

Here is my IPXE script code snip and a attachment:
:WinISCSIBoot
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanboot --drive=0x80 ${root-path} ||
goto WinISCSIInst

:WinISCSIInst
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanhook --drive=0x80 ${root-path} ||
goto WimbootWK ||

Output in case of SANBOOT:
REGISTERED SAN DEVICE 0x80
COULD NOT DESCRIBE SAN DEVICE:OPERATION NOT SUPPORTED (http://ipxe.org/3c222083)

Output in case of SANHOOK:
COULD NOT OPEN SAN DEVICE: Error 0x0323209 (http://ipxe.org/03232094)

Thank you for your help

Mit freundlichen Grüßen
DI Martin Lugger
+++++++++++++++++++++++++++++++++
tiroNET
Dipl. Ing. Martin Lugger GmbH & Co KG
Schopenhauerstrasse 45/21
A-1180 Wien
FB:137132s
UID:ATU40176509
FG:Handelsgericht Wien
Tel.: [phone]
Fax: [phone]
e-mail:***@tironet.com
+++++++++++++++++++++++++++++++++

[Christian Nilsson]

Hi,
The error from sanhook suggests that you are hooking to a drive number
that is already in use.
It could be due to previous san commands in the same run..
I'm not sure why you are using --drive, I would start with removing
--drive part from you commands.

Your iscsi uri seems a bit weird as well, by mentioning EFI are you
saying that this works in PCBIOS mode but not EFI?



On Sun, Apr 16, 2017 at 6:12 PM, tiroNET::Martin Lugger

Post by tiroNET::Martin Lugger
HI ipxe developers,
it seems, that the support of SANBOOT EFI on VMWARE ESXi 6.5 on a “x86_x64
VM” and a “i386 VM” is not working
ON the Bios based machines in VMWARE and on physical computers it is working well!
I get the error “COULD NOT DESCRIBE SAN DEVICES: Operation not supported
(http://ipxe.org/3c222083)
I build the IPXE.EFI binaries via Rom-O-Matic website with the default settings.
:WinISCSIBoot
set root-path
iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanboot --drive=0x80 ${root-path}
||
goto WinISCSIInst
:WinISCSIInst
set root-path
iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanhook --drive=0x80 ${root-path}
||
goto WimbootWK
||
REGISTERED SAN DEVICE 0x80
COULD NOT DESCRIBE SAN DEVICE:OPERATION NOT SUPPORTED
(http://ipxe.org/3c222083)
COULD NOT OPEN SAN DEVICE: Error 0x0323209 (http://ipxe.org/03232094)
Thank you for your help
Mit freundlichen Grüßen
DI Martin Lugger
+++++++++++++++++++++++++++++++++
tiroNET
Dipl. Ing. Martin Lugger GmbH & Co KG
Schopenhauerstrasse 45/21
A-1180 Wien
FB:137132s
UID:ATU40176509
FG:Handelsgericht Wien
Tel.: [phone]
Fax: [phone]
+++++++++++++++++++++++++++++++++
_______________________________________________
ipxe-devel mailing list
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel

[Michael Brown]

The first error suggests that your UEFI firmware does not provide the EFI_ACPI_TABLE_PROTOCOL and so provides no way for iPXE to describe the iSCSI target. You can work around this firmware problem by using --no-describe. Note that the booted OS will not be able to automatically locate the iSCSI target, since there will be no iBFT.

The second error is simply because you have attempted to hook two SAN targets using the same drive number.

Michael

Post by tiroNET::Martin Lugger
HI ipxe developers,
it seems, that the support of SANBOOT EFI on VMWARE ESXi 6.5 on a
"x86_x64 VM" and a "i386 VM" is not working
ON the Bios based machines in VMWARE and on physical computers it is working well!
I get the error "COULD NOT DESCRIBE SAN DEVICES: Operation not
supported (http://ipxe.org/3c222083)
I build the IPXE.EFI binaries via Rom-O-Matic website with the default settings.
:WinISCSIBoot
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target}
||
sanboot --drive=0x80 ${root-path}
||
goto WinISCSIInst
:WinISCSIInst
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target}
||
sanhook --drive=0x80 ${root-path}
||
goto WimbootWK
||
REGISTERED SAN DEVICE 0x80
COULD NOT DESCRIBE SAN DEVICE:OPERATION NOT SUPPORTED
(http://ipxe.org/3c222083)
COULD NOT OPEN SAN DEVICE: Error 0x0323209 (http://ipxe.org/03232094)
Thank you for your help
Mit freundlichen GrÌßen
DI Martin Lugger
+++++++++++++++++++++++++++++++++
tiroNET
Dipl. Ing. Martin Lugger GmbH & Co KG
Schopenhauerstrasse 45/21
A-1180 Wien
FB:137132s
UID:ATU40176509
FG:Handelsgericht Wien
Tel.: [phone]
Fax: [phone]
+++++++++++++++++++++++++++++++++

[tiroNET::Martin Lugger]

Hello Michael,Christian

ad ERROR:SANBOOT
It seems, that the VMWARE ESXi 6.5 does not provide the EFI_ACPI_TABLE_PROTOCOL and therefor the
command “sanboot --drive=0x80 ${root-path}“ on the “virtual Computer”.
The workaround to create no iBFT with the command “sanboot --no-describe --drive=0x80 ${root-path}” would boot.
But for my OS on the iSCSI-Target (Windows 10) it will fail, because in the default Iscsi-target-installation windows needs the iBFT.
For example Ubuntu will boot fine, because it takes no notice of the iBFT.

ad ERROR:SANHOOK
yes, you are right, but if you do only the SANHOOK, then you have the same issues like with the “SANBOOT” command
I case of Windows installing to the iscsi-target the command
“sanhook --no-describe” will create no iBFT and if you boot then a WINPE system, the WINPE system is unable to mount automatically the iscsi-target as local disk for installing windows

THANK YOU VERY MUCH,
Now I understand the process totally



Mit freundlichen GrÌßen
DI Martin Lugger
+++++++++++++++++++++++++++++++++
tiroNET
Dipl. Ing. Martin Lugger GmbH & Co KG
Schopenhauerstrasse 45/21
A-1180 Wien
FB:137132s
UID:ATU40176509
FG:Handelsgericht Wien
Tel.: [phone]
Fax: [phone]
e-mail:***@tironet.com
+++++++++++++++++++++++++++++++++

Von: Michael Brown [mailto:***@fensystems.co.uk]
Gesendet: Sonntag, 16. April 2017 20:05
An: ipxe-***@lists.ipxe.org; tiroNET::Martin Lugger <***@tironet.com>; ipxe-***@lists.ipxe.org
Betreff: Re: [ipxe-devel] SANBOOT/SANHOOK VMWARE Esxi 6.5 EFI

The first error suggests that your UEFI firmware does not provide the EFI_ACPI_TABLE_PROTOCOL and so provides no way for iPXE to describe the iSCSI target. You can work around this firmware problem by using --no-describe. Note that the booted OS will not be able to automatically locate the iSCSI target, since there will be no iBFT.

The second error is simply because you have attempted to hook two SAN targets using the same drive number.

Michael
On 16 April 2017 17:12:29 BST, "tiroNET::Martin Lugger" <***@tironet.com<mailto:***@tironet.com>> wrote:
HI ipxe developers,
it seems, that the support of SANBOOT EFI on VMWARE ESXi 6.5 on a “x86_x64 VM” and a “i386 VM” is not working
ON the Bios based machines in VMWARE and on physical computers it is working well!


I get the error “COULD NOT DESCRIBE SAN DEVICES: Operation not supported (http://ipxe.org/3c222083)


I build the IPXE.EFI binaries via Rom-O-Matic website with the default settings.


Here is my IPXE script code snip and a attachment:
:WinISCSIBoot
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanboot --drive=0x80 ${root-path} ||
goto WinISCSIInst


:WinISCSIInst
set root-path iscsi:${iscsi-srv}:tcp:3260:0:${iscsi-target} ||
sanhook --drive=0x80 ${root-path} ||
goto WimbootWK ||


Output in case of SANBOOT:
REGISTERED SAN DEVICE 0x80
COULD NOT DESCRIBE SAN DEVICE:OPERATION NOT SUPPORTED (http://ipxe.org/3c222083)


Output in case of SANHOOK:
COULD NOT OPEN SAN DEVICE: Error 0x0323209 (http://ipxe.org/03232094)


Thank you for your help


Mit freundlichen GrÌßen
DI Martin Lugger
+++++++++++++++++++++++++++++++++
tiroNET
Dipl. Ing. Martin Lugger GmbH & Co KG
Schopenhauerstrasse 45/21
A-1180 Wien
FB:137132s
UID:ATU40176509
FG:Handelsgericht Wien
Tel.: [phone]
Fax: [phone]
e-mail:***@tironet.com
+++++++++++++++++++++++++++++++++