https://worldofeuc.com logo
Join Slack
Powered by
All of our App Layering images were built on VMwar...
# citrix-app-layering
n
All of our App Layering images were built on VMware. So, to test the packaging VMs out in Nutanix, I created a new Platform layer (for creating/updating layers, not publishing), and chose the Nutanix Acropolis hypervisor option and selected my Nutanix AHV connector. The packaging VM is built in AHV, but the VM BSODs each time with an "INACCESSIBLE BOOT DEVICE" error. Anyone ever move hypervisors and go through this process before (@Jarian Gibson or @Rob Zylowski)? I have to be missing something obvious here.
The template used in that AHV connector is just a shell VM with the CPU/RAM/NIC configured, nothing else. Legacy BIOS with the default boot order.
j
Was the VM built using UEFI or Legacy? Template VM boot has to match.
Was the original VM from AHV or VMware?
n
Everything should be legacy BIOS. Original was VMware.
j
So new version was created on VMware and virtio installed before trying to deploy on AHV?
n
So that's probably what I'm missing. I assume we need to create an OS layer version, install VirtIO, then use that as the target OS layer version when building this new Platform layer?
j
Correct
n
Okay, that refreshed my memory. Completely missed the obvious. Thank you!
We're working on this now. Built an OS layer version and installed the VirtIO drivers in it, then finalized the layer. Tried building a new Platform layer using that OS layer version in VMware, and it failed to load the NIC drivers. Any chance you've seen this behavior before? I expected to be able to send the packaging VM to either VMware or Nutanix with both drivers installed.
r
When you say in vmware whats that mean
do you mean you tried to create a vmware vm wiht the same plTFOR LAYER
or just the same os layer
n
Sorry, we used the VMware connector in App Layering to have the packaging VM stood up in VMware
The Platform layer used the new OS layer that has the VirtIO drivers installed (and the VMware drivers/tools).
r
ok so your just trying to create anew vmware layer and your saying the packaging vm is not booring wiht nework drivers working
n
Yep, boots fine, but no NIC. Waiting on somebody to login and troubleshoot what they see.
r
hmm does seem weird let me ask the engineers. I would expect it would work like other hypervisors where if the hardware was not found it would ignore the virtio drivers. have you also tried a normal app layer
n
No, but that's next.
r
let me know if you have the same issue. BTW in the platform layer settings you def picked vmware as the hypervisor
n
I could also have him try and use the Nutanix connector for the Platform layer build. Honestly, not even sure why I told him to use the VMware connector.. that doesn't make sense now that I'm re-reading my documentation.
r
is the platform, layer for nutanix
or vmware
n
Nutanix
r
for nutanix you have to do it on nutanix
⤴️ 1
not app layers but the platform layer
n
But it's a publishing Platform layer, not the packaging kind. FIgured it didn't matter where we built it since the OS layer had the drivers in it.
r
otherwis we remove all the other hypervisor software
n
Okay, will correct this then.
r
we do this thig called recipes where we remove drivers form other hypervisors for the platform alyer
thats why you arent seeing nic drivers
yea let me know if you still have an issue when you create the pltform layer n nutanix
n
It's just weird, because he used the VMware connector for the layer. We lost access to the Elements console, so we'll have to wait to test again.
r
yes but we remove vmware drivers when you say its for nutanix
⤴️ 1
n
Ahhh, I remember the field you're referring to now
👍 1
Totally forgot that there was a hypervisor field, was just thinking of the connector config field.
This is what happens when you're 1.5 years removed from daily App Layering access.
r
I know its hard to keep up wiht it all
Open in Slack
PreviousNext
Powered by