Створення та керування VM
Main console workflow starts with planned topology node. Provisioning later turns that node into libvirt domain using selected build or enabled catalog image.
Add a planned node
- Open project or completed build topology.
- Add VM node.
- Give safe name: 1–63 characters, beginning with letter or digit and containing only letters, digits, hyphens, or underscores.
- Set memory, vCPUs, and root-disk size. Current defaults 4,096 MiB, 2 vCPUs, and 20 GiB; account entitlements can clamp lower.
- Choose boot variant and connect one or more topology networks.
- Save graph, then deploy or start node.
Adding card alone does not reserve compute or create VM. Confirm node changes from planned to runtime state and has libvirt identifier before opening console or running tests.
Image sources
Boot-variant picker can expose completed builds and public catalog targets enabled by operator. Backend resolves catalog targets to trusted artifact rather than accepting browser-supplied path as authority.
There is also lower-level authenticated create-from-iso API for internal test and deployment workflows. Its iso_path is server-side image path, not general browser upload or arbitrary remote-URL downloader.
Changing boot variant of existing domain replaces CD-ROM image, sets CD-ROM first, and cold-restarts VM. VM disk retained. Not same as installing selected image onto that disk.
Lifecycle actions
| Console action | Runtime behavior | Risk |
|---|---|---|
| Start | Starts stopped domain | Guest boot can still fail |
| Shutdown | Requests ACPI guest shutdown | Requires guest cooperation |
| Reboot | Requests graceful guest reboot | Requires guest cooperation |
| Reset | Hard-resets running domain | Can corrupt in-flight writes |
| Power off | Forces domain off | Equivalent to pulling power; data loss possible |
| Delete | Removes domain and managed disk/metadata | Destructive; retain needed evidence first |
No reliable universal boot-time estimate. Watch runtime state and console, use test-run timeouts sized for selected image.
Install-to-disk acceptance
For image claiming installer:
- Provision with writable root disk.
- Boot from ISO and complete installer through VNC or supported automated installer path.
- Eject or deprioritize CD-ROM.
- Reboot and confirm disk, not ISO, is active boot source.
- Verify users, desktop, packages, services, and installer cleanup.
Installer icon appearing in live session is not sufficient evidence.
Persistent overlay and snapshots
Some images can attach Zone 2 persistence disk. Zone controls expose snapshot, rollback, export, import, and reset operations for governed overlay. They do not snapshot VM memory, base image, or unrelated disks. VM must be running and in-guest Zone support healthy for these operations.
Troubleshooting
- If planned node never provisions, inspect deployment error and current entitlement response before retrying.
- If console cannot connect, confirm domain running and has resolvable runtime ID.
- If graceful action stalls, inspect guest before using reset or power off.
- If networking fails, compare authored edge, attached libvirt interface, active network, DHCP/static address, route, and DNS configuration.
- If installer repeatedly boots, check boot order and eject ISO.
See Network topology and VNC console.