You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edit a VM's boot order from its Hardware tab: the Boot Order row shows the order as
chips (or "No boot device") and a pencil opens a dialog listing every bootable device
(disks, CD/DVD drives, network devices) with an "enabled" checkbox and Up/Down buttons.
Legacy boot: cdn + bootdisk configs are read and rewritten as order=.... Session
sign-in only, gated on VM.Config.Options; containers have no boot order.
Add, detach and remove disks from a guest's Hardware tab. "Add disk" (VM) / "Add mount
point" (container) creates a new volume on an image-capable storage of the node -- bus,
size, a format limited to what the storage supports, cache / discard / SSD / IO thread and
backup for a VM; path, backup, read-only and ACL for a container -- and shows each
storage's free space. "Detach" keeps the volume as an unused disk; "Remove" on an unused
disk destroys the volume and needs its slot name typed to confirm. Session sign-in only;
adding needs VM.Config.Disk on the guest plus Datastore.AllocateSpace on the storage,
detaching and removing need VM.Config.Disk.
Add, edit and remove network devices from a guest's Hardware tab: an "Add network
device" button and an edit/remove action on each NIC row. A VM picks model, bridge
(from the node's bridges), VLAN tag, firewall, rate limit, disconnect and MTU; a
container picks its interface name, bridge, IPv4 (DHCP / static + gateway /
manual), IPv6 (SLAAC / DHCP / static + gateway / manual), VLAN tag, firewall, rate
limit and MTU (1 = the bridge MTU on a VM). A new device gets a Proxmox-generated MAC
(or an override); editing never changes an existing MAC and keeps options the dialog
doesn't show (queues, trunks, ...). Session sign-in only, gated on VM.Config.Network
-- the shared service token stays read-only here too.
Changed
Web test suite: 30 s test/hook timeouts, 10 s element-wait budgets in the heavy
route-level tests, and an opt-in PROXION_VITEST_WORKERS=<n> cap so parallel suites
on a busy machine stop timing out.