02-17-2022 06:32 AM
Hi Ruckus Forums,
I'm trying to simulate the HTTP API v5.2 from a Ruckus Virtual SmartZone device version 126.96.36.199.317 in QEMU with KVM accelerator, and I can not set the device up because it keeps forever in the Certificate and Root Key created part with an error traceback.
It's important to notice that I tried first the version 3.0.3, and it worked just fine.
I tried the set-up from both CLI and Web, none succeeded. I also tried different combinations of options in the set-up, like Manual and DHCP network configuration, different and same password for admin and CLI, again none worked.
However, I can give a hint about what's going on. The following images show that during the Certificate and Root Key created part, the web server suddenly goes down:
Then, when trying to list the interfaces in the CLI, Tomcat shows up:
Another information: I also tried Ruckus Virtual SmartZone 188.8.131.52.515, and it fails exactly the same.
Tools and versioning:
I would appreciate help with this issue.
02-22-2022 08:48 AM
I don't think QEMU is a supported platform for vSZ product. This is why it might be failing.
02-22-2022 12:10 PM
Thanks for your reply.
I do think QEMU is supported, by the following facts:
1. they have the image for QEMU https://support.ruckuswireless.com/software/2829-vsz-5-2-2-0-317-gd-software-release-kvm-qcow2-image
2. The version 3.0.3 worked just fine, in the same machine just hours earlier.
3. I suppose if QEMU was not supported, the machine would not even start, or at least throw a considered amount of errors.
However, you could be right.
In the case QEMU is really supported, do you know if upgrading Ruckus Virtual SmartZone is straight forward? If yes, I could get a working version and upgrade all the way to the version I want.
If QEMU is not really supported, do you know an officially supported hypervisor I could give it a shot?
02-25-2022 11:31 AM
I was looking into the release notes but there is no mention of QEMU being supported.
Also recent release 6.0 and 6.1 also has not mention of it under supported hypervisors.
I am still checking if this is officially support or not.