#Importing the OVA for the NAbox Appliance into Nutanix.
1 messages · Page 1 of 1 (latest)
I have not done this with Nutanix yet, but will do some work this weekend to see what I can. If anyone else has an idea beforehand please chime in. I've only done alternate deployments to Azure
@unkempt tulip
Interesting. Any way that you can record a video of the whole boot ?
Ok nevermind, it won't work, flatcar customization validates that's the VM is a VMware VM. Let me think about it
not sure if Nutanix allows you to import disks the same way Azure does or if that is feasible.
I plan on doing some work with it this weekend and I'll report back on anything I find.
I screenshot the entire journalctl. Is it OK to paste them here, or upload a file with them somewhere
Ty, I got the method of importing the disks. I think the settings of the VM is the issue. In the Nutanix doc, they are saying to get the settings from the OVF file and create the VM matching them. From the NAbox ovf I got 4GB of RAM and 2 vCPUs and 1 socket and this is only settings I can supply for the VM creation in Nutanix. However in the NAbox OVF there are more NAbox-oriented settings I am not sure how would be translated or are they important to start the VM.
There are 21 screenshots.
You will notice an error from ignite config that it’s bailing when seeing the environment isn’t VMware. That’s probably the reason for failure. I spent some time with a buddy at nutanix earlier today, I don’t think there is an easy way.
But I do think alternative hosts for NAbox is important
I’ll see if I can change a few things and make a qcow2 image, that should solve it and bring more hypervisors to the table.
If it works, then it shouldn’t be too hard to apply the same to any of the available flatcar images (azure, AWS, etc)
OK. Thank you. Please let me know how it went.
Here is the error you're getting not running on VMWare CPU
aye. tried multiple things and couldn't get it to kick in.
maybe exporting the ova to raw disks/etc and then converting it to qcow or such but i didnt have time to get into that aspect
working on a qcow2 image currently
one of the issue is the oem_id=vmware in grub.cfg. Then there is the data disk that typically isn't distributed with a cloud image, working around this
Can't do much testing yet but with luck, that should boot : https://upload.nabox.org/voca-kecu-kazo
Don't forget to attach an additional disk, it should get a DHCP IP
the OVA has two disks. do I attach both of them?
yes
What I did is: created a Nutanix image disk out of the qcow2 file and added an additional 200GB disk to the VM. Haven't used any of the vmdk files from the OVA image. I am assuming that the qcow2 file is the same as the first vmdk file and then there is a second file to hold the data. In general is the second VMDK file empty in the OVA image?
And I was able to boot the NAbox and logged in. I have to yet configure it with a static IP. Was that a correct approach of building the Nutanix VM out of the QCOW2 image?
yes pretty much.
Note that I'm still adjusting stuff in the qemu image, reusing the same share as you got the qcow2 from
technically it's not the same qcow2 as the vmdk, the flatcar image is the qemu one
well... it's ALIVE !
https://nabox.org/downloads/
I decided to release both qcow2 and vhdx as experimental and get some feedback
here are the notes i made for azure Yann, this was based on v3, i'm going to build out a v4 system this weekend and update anything that is necessary
I just did a vhdx actually 😄
and the serial console would be awesome indeed
though I'll assume flatcar image for azure already has the serial set
Thank you, Yann. I will download the new image and give it a go next week after Wednesday. I will post how it went.
So does the new zip file have the second drive in it, or this is the drive with the image and I have to again add the second drive as before?
You will have to add the drive, it seems to be the standard procedure for that kind of deployments.
Use the image from the NAbox downloads
Yann, for some reason I can't change the IP to the static IP in the web configuration. Is the su admin with the default password or something else?
actually, the network information I entered in the GUI created the 10-nabox-network file with the right format. However, the website is still available on the DHCP IP the VM got when it was created.
I am not able to openup the GUI on the IP specified in the file below. The IPs are not real but this is how the network file format is:/etc/systemd/network
10-nabox.network
[Match]
Name=ens192
[Network]
LinkLocalAddressing=no
IPv6AcceptRA=no
Address=10.10.10.10/21
Gateway=10.10.10.1
Domains=domain1 domain2 domain3
DNS=192.62.2.1
DNS=192.62.1.1
Mmm, I don't think ens192 is correct. Is that the latest qcow2 ?
Yes, I checked the hash as well.
I don't understant. ens192 is only ever mentioned in VMware builds
Unless your ethernet interface actually is ens192 ?
OK. eth0 is the network interface on the VM in Nutanix, which is a DHCP assigned IP. I used that IP to login to the GUI and then in the Network configuration of the web site I entered my static configuration, which shows up in the 10-nabox.network file and the interface is "ens192" and the static configuration I want. So, for some reason the configuration in 10-nabox.network file doesn't translate to the VM networking, eth0. I executed commands to change the eth0 with the static IP and was able to access the website using the static IP, but this is a temp solution. rebooting of the VM is going back to DHCP. How do I make this change permanently? What is the best approach of fixing it? Can I specify eth0 in the 10-nabox.network file? Thanks!
can you confirm the build number in About box ? And maybe collect a support bundle and upload it here ? https://upload.nabox.org/pire-viwe-tuku
I don't think it's complete. See, when you download the support bundle from NAbox, there is no progress bar as the content is streamed, I think you may not have waited for the download to finish
I'm redeploying a fresh image on nutanix, this is so weird
Indeed I'm able to reproduce
Not sure what happened. A new build seems to work fine now https://upload.nabox.org/pire-viwe-tuku
again using qcow2 file? what is the *.nbx file?
update file for nabox i believe
It is 🙂
OK. thanks.
4.0.6b1 will be on the web site in a few minutes
cool. I haven't done an update using the nbx file. How do you do it?
OK. don't see the 4.0.6b1 version, though.
Really ? https://nabox.org/downloads/ in the beta versions section
didn't look in the beta versions.😞