VMs cannot be set to autostart

Bug #1357420 reported by Robie Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
uvtool
Triaged
Wishlist
Unassigned

Bug Description

An --autostart option to the create function would be useful (or consider making this the default).

Revision history for this message
Robie Basak (racb) wrote :

Note the workaround is "virsh autostart <name>" after VM creation.

Revision history for this message
Robie Basak (racb) wrote :

4:29 <rbasak> uvtool users: do you expect a VM created with uvtool to automatically start after a host reboot? Or do you expect it to require starting manually so you can control that?
14:29 <rbasak> danwest: ^^ any thoughts please?
14:29 <rbasak> (this is by default of course - we can change behaviour with an option on "uvt-kvm create")
14:38 <danwest> rbasak, well we should probably have an option for either
14:38 <danwest> bur for default, tough call
14:39 <danwest> maybe not for default but a cmdline option/flag to make it automatic on reboot
14:39 <rbasak> OK
14:39 <rbasak> I'm in agreement I think.
14:39 <rbasak> Having the VM "vanish" could surprise the user but so could an autostart.
14:40 <rbasak> I'll add an --autostart option (or --auto-start?) but default to not autostarting, and then document that in the manpage.

summary: - VMs do not autostart
+ VMs cannot be set to autostart
Ian Watt (ian.watt)
Changed in uvtool:
status: Triaged → Fix Committed
Robie Basak (racb)
Changed in uvtool:
status: Fix Committed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.