Cole Robinson a écrit :
On 10/01/2009 11:07 AM, Daniel Huhardeaux wrote:Hi, 3 VMs on a host, all in autostart: the both where <disk type='block' device='disk'> <source dev='/dev/vg0/DomU1'/> <target dev='vda' bus='virtio'/> </disk>are not started automagically on host startup. They start without problem from virsh. The one having<disk type='file' device='disk'> <source file='/media/vm2/vdisk.qcow2'/> <target dev='hda' bus='ide'/> </disk> has no problem. Any idea why?FYI, libvirt/virsh specific questions should go to libvirt-list@xxxxxxxxxxx CCing
Ok, sorry for that. Reply will go there
Try 'virsh dominfo <vmname>' for each VM to ensure autostart is actually enabled.
virsh # dominfo Domain3 Id: 3 Name: Domain3 UUID: 98318198-c595-327c-42e1-85be81269324 OS Type: hvm State: running CPU(s): 2 CPU time: 452,2s Max memory: 1048576 kB Used memory: 524288 kB Autostart: enable virsh # dominfo Domain1 Id: 1 Name: Domain1 UUID: 26e5de74-0841-c4b3-4cc4-e0df0f93cb39 OS Type: hvm State: running CPU(s): 2 CPU time: 60580,7s Max memory: 1048576 kB Used memory: 1048576 kB Autostart: enable virsh # dominfo Domain2 Id: 2 Name: Domain2 UUID: 98318198-c595-327c-42e1-85be81269323 OS Type: hvm State: running CPU(s): 2 CPU time: 1360,2s Max memory: 1048576 kB Used memory: 1048576 kB Autostart: enable
To see why autostart is failing, you want to launch libvirtd by hand. Stop all your VMs, do a service libvirtd stop, then (as root) run 'libvirtd'. Any VM startup error messages should be printed on the console.
I did it and still did'nt get the 2 VMs starting. So I activate again autostart, in that order:
virsh --connect qemu:///system net-autostart MyNetwork virsh --connect qemu:///system autostart Domain1 virsh --connect qemu:///system autostart Domain2 virsh --connect qemu:///system autostart Domain3 and now all is OK. Thanks for your support -- Daniel -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list