Can't deploy/register/debug with parallels
I’m running parallels with bridged networking on an intel iMac, i’m attempting to deploy a windows image to it (successful on other machines and VM’s on the same LAN) but i’m getting the following error:
Not sure why this behaves so differently as it shouldn’t be ARM and is EFI like my vmware vm’s, I assume this is an issue with init.xz not being pulled across, but I’m not really sure why
@Tauric I have doubts that bzImage is getting transferred to this computer. I can tell you that bzImage will boot even if init.xz is not sent to the target computer. You will get a vfs not syncing error. In the fog configuration->fog settings page. Press the expand all button then search for “log” change the default log level from 1 to 7. Save the setting then try to pxe boot the target computer again. Logging level of 7 will cause the linux kernel “bzImage” to print out a lot of debugging information. That will tell us if the kernel is booting.
At the ipxe prompt you can download the init.xz file (as a test) by keying in
initrd=init.xzand press enter. Lets see if we get any useful error messages.
@george1421 There’s the other possibility the system is running 32 bit os and only attempting to load a 64 bit kernel (or vice versa)
At least that’s the first thing that comes to my mind.
Hi George, thanks for the response,
Apologies if I’m doing things wrong here, the log level was set as 4 in the fog settings, changing it to 7 doesnt seem to have done much here. Also for the
initrd=init.xzit returns ‘command not found’ unless i’m entering this in the wrong place or something?
As a sidenote, the http transfers are far slower than normal in this parallels environment, I’m testing the Hirens BootCD image I have on the server and its moved the boot.wim 3% in the time I’ve typed this out.
I have found a workaround for this as parallels does let you import .VMX files from VMware, I have to assume its some kernel incompatability or something.
Thanks for the suggestions
@Tauric This “parallels” is from a M series mac?
Just a question.
The M1/M2/M3 chipsets are ARM based if I recall correctly.
Also for the initrd=init.xz
That is precisely why you should not trust my memory. For a little clarity this is what boot.php file creates for the auto reg function.
kernel bzImage loglevel=7 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://192.168.50.23/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.50.23:/images/ storageip=192.168.50.23 nvme_core.default_ps_max_latency_us=0 loglevel=7 mode=autoreg imgfetch init.xz
So the command at the IPXE> prompt would be
imgfetch init.xzThere is no equals
=sign in the command.
And just to tag along with what Tom said, when I first read your post I was confused if your target computers are ARM or Intel? You menitoned Intel iMac, and then a little later ARM. But I took the ARM reference as it should work because its not ARM based.
OK by setting the logging to 7 and you don’t see a bunch of text on the screen then the kernel (bzImage) is not starting up. So at the IPXE prompt I would try
kernel bzImageto see if it is really transferring it. The
bootcommand at the IPXE> should try to run the kernel.