Hyperbox - Discussion and Support

[noteirak]

This topic is dedicated to Hyperbox, a tool written in Java, entierly free and open source to manage VirtualBox accross multiple servers. Main use case is managing dedicated hosts running headless VMs in VirtualBox.
It is aimed to offer more than the VirtualBox features in later versions, aiming to be an equivalent to VMware vCenter.
This topic is provided if you don't want to use the dedicated communication channels available.

Official Website
User Manual

Download latest version

[mribichich]

Hi there, I'm trying to create a windows machine, for example xp, from my client. the thing is that i need to connect to the vm to set up windows.
is there a way or is not supported?

And on the other hand, i created a vm from the client with an X.iso and then i created a vm from the server with the same X.iso, and when I try to register the second vm in the client, it gives me an error saying that the X.iso image is already registered.

Is not supported to have to vms created from the same iso file?

thanks!!

[noteirak]

About connecting to the VM, you can do it yes. You still need to install the official extension pack directly using VirtualBox binaries, either via the GUI or via the CLI (vboxmanage). Once you installed it, restart hyperbox.
You will then be able to configure the Remote info in the VM settings directly.
From the client side, the Hyperbox client will auto-configure RDP clients (mstsc for Windows, rdesktop for Linux) on first install and you can then use the "Connect" button in the VM details next to the Console field.

About the ISO, this is directly related to VirtualBox. Each time you use a new ISO (or any storage file), an internal UUID is assigned to it. UUID are unique per VirtualBox user profile, but are kept inside the VM config file.
This means that a UUID was assigned to the ISO when you used it under the server account. Then another UUID was assigned when you used it from the client.
So when trying to import your VM config, there is a UUID conflict for the same ISO.
The way to fix it is to remove the ISO from the config of either VM, then try importing again.

[mribichich]

Ok great thanks for the info. Just to check, can I connect to the vm, before installing the OS? just to set it up, like windows does, that you have to choose the the language, partition, and then install windows.
In that case also I can connect?
Because I understand rdp, but since windows is not installed yet, that can not be use.

thanks!!

[noteirak]

Yes you can connect before installing the OS. The RDP server is not the one from the guest OS, but the one from the VirtualBox process that runs the VM, so you can see the BIOS splashscreen and everything.
It's like a real console!

[Laca]

Hi,
First of all, thanks for creating Hyperbox, it helps a lot managing multiple VMs!

My question is related to the configuration possibilities of the Kryonet client.
So in my environment there are multiple (actually 4) physical CentOS servers with multiple VirtualBox VMs (CentOS again) running on all of them.
I can only access one of the servers directly, so for everything else I have to use tunneling.
And here is my problem:
For the Hyperbox client the only visible host is the one I can directly access. I can nicely manage the VMs running on that host.
For other servers I can create tunnels, so that another server's Kryonet server port is tunneled to e.g. 45613, the next to 45614, etc.
However, as far as I can see, there is no way in the Hyperbox client to specify a non-default Kryonet port for a server!

Is this really the case? If yes, then do you plan to add such configurability to the client?

Thanks a lot!

Laca

[noteirak]

You can specify another port in the host field using the regular URI/URL format, so if you want to connect to localhist with port 45613, put this in host field:

Code: Select all   Expand viewCollapse view

127.0.0.1:45613

[Laca]

Ah, thanks a lot, I should have thought of that !