¶ Hive VM
The Hive VM is a prebuilt virtual machine image for running Hive on customer infrastructure. It is delivered as an amd64 qcow2 image and is intended for Proxmox VE deployments, with QEMU/KVM support for Linux-based lab testing.
¶ Download
Download the latest Hive VM image from the public Hive VM page.
Open Hive VM download page- Image:
hive.qcow2 - Architecture:
amd64 - Disk format:
qcow2 - Virtual disk size:
100 GB - Disk behavior: grows as data is written
¶ Interactive Deployment Guide
Use the interactive Hive VM deployment guide to generate commands and walk through setup:
Coming Soon¶ Supported Platforms
¶ Recommended
- Proxmox VE
¶ Supported for lab testing
- QEMU/KVM on Linux
¶ Operator workstation for Proxmox deployment
- Windows with OpenSSH
- macOS with OpenSSH
- Linux with OpenSSH
¶ Not currently covered by this guide
- Hyper-V
- VMware
- VirtualBox
¶ VM Requirements
- CPU:
amd64, 2+ vCPU - RAM: 4 GB minimum recommended
- Disk: 100 GB virtual disk
- Network: bridged NIC recommended
DHCP is used by default. Manual IPv4 setup is possible from the VM console using:
sudo nmtuiGateway and DNS are optional unless the VM must reach other networks or resolve hostnames.
¶ Default Credentials
¶ VM console
User: meshmerize
Password: youmoveweconnect¶ Hive web login
User: admin
Password: youmoveweconnectChange default credentials after deployment if required by your environment.
¶ Network and Ports
Hive web UI:
http://<hive-vm-ip>/Device MQTT broker:
<hive-vm-ip>:1883| Service | Port | Notes |
|---|---|---|
| Hive web UI | 80 |
Open in browser as http://<hive-vm-ip>/ |
| MQTT broker | 1883 |
Used by devices to connect to Hive |
For device onboarding, devices must be able to reach the Hive VM over the LAN. Bridged networking is recommended.
¶ Proxmox VE Summary
The interactive guide should be used for the full flow. The short Proxmox import flow is:
scp hive.qcow2 root@<proxmox-host>:/root/hive.qcow2
qm create <vmid> \
--name hive \
--memory 4096 \
--cores 2 \
--machine q35 \
--scsihw virtio-scsi-pci \
--net0 virtio,bridge=vmbr0 \
--agent enabled=1
qm importdisk <vmid> /root/hive.qcow2 local-lvm
qm set <vmid> --scsi0 local-lvm:vm-<vmid>-disk-0
qm set <vmid> --boot order=scsi0
qm start <vmid>- Machine type:
q35 - Disk bus:
scsi - SCSI controller:
virtio-scsi-pci - Network device:
virtio - Network bridge: usually
vmbr0 - Storage target: usually
local-lvm
Adjust storage and bridge names to match the Proxmox host.
¶ QEMU/KVM Summary
QEMU/KVM direct usage is intended for Linux-host lab testing.
Use bridged networking when devices need to connect to the Hive VM. NAT mode is useful only for local browser checks.
¶ Device Configuration
When connecting devices to Hive, use the Hive VM IP address.
MQTT Host: <hive-vm-ip>
Hive Host: http://<hive-vm-ip>
MQTT Port: 1883For the full device onboarding guide, see:
Guide to connect devices to Hive¶ Troubleshooting
¶ VM Has No IP Address
Check that the VM NIC is attached to the correct bridged network. For Proxmox, this is usually vmbr0.
If DHCP is not available, log in to the VM console and configure a manual IPv4 address:
sudo nmtui¶ Hive UI Does Not Load
Use the VM address directly:
http://<hive-vm-ip>/- Confirm the VM has an IPv4 address.
- Confirm your browser can reach the VM network.
- Confirm port
80is reachable.
¶ Devices Cannot Connect
- Confirm the device uses the Hive VM IP as MQTT host.
- Confirm MQTT port is
1883. - Confirm the device and VM can reach each other over the network.
- Confirm firewall rules allow TCP
1883.
¶ Proxmox Import Fails
- Check that the storage target exists.
- Check that the storage target has enough free space.
- Check that the VM ID is unused.
- Check that the qcow2 file exists at the path used in
qm importdisk.
Useful Proxmox command:
pvesm status¶ Support
If you remain blocked after the troubleshooting steps, contact:
support@meshmerize.netInclude:
- VM platform, for example Proxmox VE or QEMU/KVM
- Step name
- Command output
- Hive VM IP address
- Screenshots where useful