Moving to a Quest VM
Hi folks.
I was going to buy an appliance to replace the current K1100 we use but came to understand that they are no longer available and a virtual appliance or SaaS would be the ways we could continue using the Quest systems management appliance which is FreeBSD. Our preferred manner of moving forward with Quest would be to use a virtual appliance. Here is where the challenge lays:
We don't use vmware or hyper-v. We use a hyper-convergence environment, Scale Computing, which is based off the KVM tools and RedHat's tools.
I keep seeing a boot error pointing at /dev/da0p3 and according to my review of which disks and partitions are available in the command line, /dev/da0p3 does even exist.
Hopefully that is something someone else has worked through before. Would anyone have any idea how to get the Quest FreeBSD-based vm to boot?
Thanks in advance,
James
Answers (2)
Even if you get that to work with Scale Computing hypervisor, it wouldn't be supported. if you called into Quest support and had some problem with performance, boot up problem, etc, they would tell you that you need to move to a supported setup.
There are still physical servers for sale:
Hope that helps
For VMware® installations:
VMware ESX®/ESXiTM 6.7 or later Open Virtualization Format (OVF) 1.0
For Microsoft® Hyper-V® installations:
Windows Server® 2019 with Hyper-V Windows Server 2016 with Hyper-V Windows Server 2012 R2 with Hyper-V
There are hosted options.
Azure Marketplace or KaaS
