Problem (latent)
In src/components/ConfigPanel.vue, handleVmAction computes vmtype ('lxc' vs 'qemu') and passes it to useProxmoxTasks.launch, but the apiCall closure always routes through proxmoxApi.vm[method](...), which hits the v1 status endpoint defaulting to vmtype='qemu'. For an LXC guest the lifecycle action would target the wrong Proxmox type.
Currently unreachable: the lifecycle action row only renders for node.type === 'vm' && node.data?.deployed, so deployed-LXC lifecycle UI doesn't exist yet. A code NOTE comment marks the spot.
Fix (when deployed-LXC lifecycle UI lands)
Route LXC lifecycle through proxmoxApi.lxc.* (or thread vmtype into vmStatusAction). Also note proxmoxApi.lxc currently only exposes start/stop, not pause/resume/stopForce — the LXC lifecycle API surface needs extending to match.
Surfaced in the 2026-06-08 "Proxmox Action Tracking" review.
Problem (latent)
In
src/components/ConfigPanel.vue,handleVmActioncomputesvmtype('lxc'vs'qemu') and passes it touseProxmoxTasks.launch, but theapiCallclosure always routes throughproxmoxApi.vm[method](...), which hits the v1 status endpoint defaulting tovmtype='qemu'. For an LXC guest the lifecycle action would target the wrong Proxmox type.Currently unreachable: the lifecycle action row only renders for
node.type === 'vm' && node.data?.deployed, so deployed-LXC lifecycle UI doesn't exist yet. A code NOTE comment marks the spot.Fix (when deployed-LXC lifecycle UI lands)
Route LXC lifecycle through
proxmoxApi.lxc.*(or threadvmtypeintovmStatusAction). Also noteproxmoxApi.lxccurrently only exposesstart/stop, notpause/resume/stopForce— the LXC lifecycle API surface needs extending to match.Surfaced in the 2026-06-08 "Proxmox Action Tracking" review.