Hard Disk not found after Deployment
-
@vanopy Its there under the esxi web ui too.
-
@george1421 I’m using the vSphere Client, and it’s not there for me unfortunately:…
-
@vanopy Oh so you are using the C# (retired) application or is it the (retired) flash based management? If its the C# application I can understand why its not working.
-
@george1421 The flash based… Just tried to login directly on the client and now I see the option…
Was always used to work this way and didn’t even realize I was lacking quite some options by doing so.
Seems that it was an ID10T error, sorry about that
I’ll give it another try now, thank you! -
@vanopy If you have vCenter the flash based ui that part of that is close to the standalone C# vsphere application. But that too is being retired. You will need to get use to the html5 web ui sooner or later. I finally gave up about a year ago and started using the vCenter html5 web ui even though the flash based ui was nicer to use.
-
@george1421 May I ask for your assistance one more time please?
I believe I have everything ready, but now I would need to know how to get my UEFI VM to PXE boot.
I’ve tried the boot option EFI Network, but it just sits as this screen and nothing happens:
-
@vanopy So the next question is have you ever pxe booted a uefi machine in your environment? If not then you need to change dhcp option 67 to ipxe.efi. And/or setup the dynamic pxe boot options on your dhcp server.
-
@george1421 Yes, several times. Never a VM though… dhcp option 67 is already ipxe.efi
-
@vanopy This is interesting since it just works for me on esxi
-
@george1421 It’s like this:
-
@vanopy So just for grins if you switch it back to bios mode it pxe boots correctly?
Also I noticed you only have 1 uefi filter. There are two (three) types you should define. 006 007 and 009.
-
@george1421 Yes, I’ve done it earlier today in BIOS mode and that worked fine.
Ok, I see, I will also add those. -
@vanopy If you only define to you need efi-64 and efi-bc to cover all of your x64 bases.
-
@george1421 So I’m looking into this again…
I’ve adjusted everything on the DHCP as I believe it should be.
I also found an article saying that I should use vmxnet3 as the network adapter instead of the E1000, which could have difficulties with PXE Booting.I’m now getting a different error message when I’m trying the UEFI PXE Boot, I’m getting the following:
succeed to download nbp file unsuccessfulAny idea what else could be going wrong for me?
Thanks again.
-
@vanopy said in Hard Disk not found after Deployment:
succeed to download nbp file unsuccessful
Well this tells me the file name asked for was not delivered to the uefi firmware (NBP would indicate uefi firmware). If tftp is logging to syslog or its own log file (in /var/log directory) you might be able to see what file name is being requested. If not you can setup tcpdump to capture the entire dhcp/pxe booting process that will give us an idea what is going wrong. I have a tutorial for that: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
But now you know that the pxe booting client is at least getting the information needed to pxe boot. It might not be getting the right information, but at least its getting something.
-
This post is deleted! -
@vanopy You were too quick to request, I just posted a link to it in the previous post
-
@george1421 Already removed it when I saw it, thank you!
I will give it a try and get back to you. -
@george1421 Ok, I think this may have been helpful, George.
What I’m seeing is the following:
But shouldn’t it be referring to ipxe.efi instead of undionly.kpxe?
-
@vanopy said in Hard Disk not found after Deployment:
@george1421 Ok, I think this may have been helpful, George.
What I’m seeing is the following:But shouldn’t it be referring to ipxe.efi instead of undionly.kpxe?
Maybe this isn’t making any sense what I’m saying…
Anyway, this is the output I get when I perform tcpdump -i any port 67 or port 68 or port 69 or port 4011
When I enter the command which is in your tutorial, I’m getting the following error:
NFLOG link-layer type filtering not implemented.
