-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log applicable 'virt-install' command #1736
Comments
@paul-hammant : Cockpit-machines actually does call out to virt-install: https://github.com/cockpit-project/cockpit-machines/blob/main/src/scripts/install_machine.py. With |
Thanks. I type |
@paul-hammant (Sorry, missed your reply); yes, that goes into the browser inspector. But as I said, this isn't quite sufficient, as it doesn't show the virt-install invocation. This is a hard problem, as there just is no single virt-install command which would reproduce the VM -- it needs the additional XML preparation/modification logic. |
No worries about having more valuable things to do, sir. I think Proxmox is in the same place - some of the more advanced network stuff has to be done in other config files however simple pct-create is at the outset. Circling back to KVM ecosystem, I played with Zig and AI for making some of the config in an article - https://paulhammant.com/2024/04/12/playing-with-zig - and of course that is too buggy to use real work and ended up being more about Zig. |
Discussed in cockpit-project/cockpit#20793
Originally posted by paul-hammant July 20, 2024
Page: Create VM
Cockpit would be even better if each UI-creation of a VM logged the equivalent
virt-install
command used. This would serve as education for users, such that they could transition to scripted creation of VMs. There logs are created for "New machine qemu-NUMBER-NAME
" but none of the command used. I realize that cockpit does not shell out tovirt-install
specifically, but the equivalent command with arg would be great.Same would be true for podman containers :)
The text was updated successfully, but these errors were encountered: