Zabbix 4 appliance hyper v - no IP on boot - fresh copy

[CDBDF]

Folks, Title is the tl:dr..
Hyper V 2012 R2
Zabbix VHDX appliance - Fresh copy
upon boot, get the ubuntu planet horizon follow by black screen
Ctrl+Alt+F2 get prompt > ifconfig -a
Output
according to the Zabbix doc I'm supposed to open an interface file and edit it to set a static IP. I have no idea how to do this. I'm unable to install an editor like nano because i can't connect to the internets. Also it appears my googlefu isn't strong enough to find a solution either.
Exasperated groan
How do i make this appliance fetch an IP so i can setup this bad boi?

[DeltaCentral]

Hi CDBDF,

Appliance Setup

https://www.deltacentral.co.uk/zabbix-appliance/

I am still in the process of adding more information. Also ensure your HyperV is on bridge mode for network and SSH in using Putty as I had the same outcome as you with a blank screen.

Kind Regards, Jags

[CDBDF]

I had another look at this. I'm still completely lost as to how to get this Zabbix appliance to get a dhcp address.

[DASM]

I'm in a similar boat with this, but CTRL-ALT-F2 doesn't bring up a prompt. The screen remains black. I've tried this on a 2016 Hyper-v cluster and a 2012 R2 Hyper-v cluster, I see the Ubuntu planet horizon and a black screen. I built a DHCP server and placed it on the same Lan, hoping I could SSH to the server if it had an IP address. It never picks up an IP address either. Is the 2012 R2 appliance tested before being setup for download? Any other suggestions to troubleshoot this issue, or particular settings for the Hyper-v virtual machine before attaching the hard drive such as generation (1 or 2)?

[DASM]

To reply to myself, what I ended up doing was downloading the appliance .iso. I created a VM in Hyper-v with the .iso as the boot and a blank drive. Booting off the .iso, I could see the screen while the install was taking place, but as soon as the server rebooted, black screen and no response with CTRL-ALT-F2. The difference this time is that the server did pick up an IP address from DHCP. I was able to SSH to it (the Zabbix web interface was also up), and performed this fix here: https://superuser.com/questions/1241...e-black-window

After rebooting, I could see output at the Hyper-v console. Granted I could have configured Zabbix via SSH and the web interface without console access, but if there were a networking issue then you couldn't get to the server.

So the moral of the story is this: The downloadable Hyper-v appliance drives, at the time I write this, did not work on two different versions of Hyper-V, with different enterprise hardware, on different Hyper-v clusters (2016 and 2012 R2). Download the appliance .iso and add a blank drive to your VM, you will need DHCP for this to work, and do the install. Hopefully this will save someone the two days I spent getting this up and running.