On Mon, Feb 16, 2015 at 03:50:41PM +0100, Jiri Denemark wrote: > When libvirt is starting a domain, it reports the state as SHUTOFF until > it's RUNNING. This is not ideal because domain startup may take a long > time (usually because of some configuration issues, firewalls blocking > access to network disks, etc.) and domain lists provided by libvirt look > awkward. One can see weird shutoff domains with IDs in a list of active > domains or even shutoff transient domains. In any case, it looks more > like a bug in libvirt than a normal state a domain goes through. > > I'm not quite sure what the best way to fix this is. In this patch, I > tried to use PAUSED state with STARTING_UP reason. Alternatively, we > could keep using SHUTOFF state and just set STARTING_UP reason instead > of UNKNOWN but it just feels wrong and wouldn't really solve the > confusion when looking at virsh list. > > I made the change to qemu driver only in this RFC patch, I will update > all drivers once we agree on the best approach. So, yeah, I think this proposal is the least-worst option I see. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list