Omer et all, I had uploaded the logs to:
https://www.dropbox.com/s/yziky6f9nk3e8aw/engine.log.xz?dl=0 https://www.dropbox.com/s/qsweiizwxk37qzg/vdsm.log.4.xz?dl=0 Do you have any recommendations for me or need me to provide more info? I will be able to re-run and experiment with this in the evening, so I can collect specific logs with times, etc if you have something in particular you want me to try. Diego On Thu, Jul 16, 2015 at 8:20 AM, Diego Remolina <dijur...@gmail.com> wrote: > These are the links to the files, if there is other better/preffered > way to post them, let me know: > > https://www.dropbox.com/s/yziky6f9nk3e8aw/engine.log.xz?dl=0 > https://www.dropbox.com/s/qsweiizwxk37qzg/vdsm.log.4.xz?dl=0 > > A bit more of an explanation on the infrastructure: > > I have two virtualization/storage servers, ysmha01 and ysmha02 running > Ovirt hosted engine on top of glusterfs storage. I have two Windows > server vms called ysmad01 and ysmad02. The current problem is that > ysmad02 will *not* start on ysmha02 any more. > > > Timeline > > My problems started at around 8:30PM 7/15/2015 when migrating > everything to ysmha01 after having patched and rebooted the server. > > I got things back up at around 10:30PM after rebooting servers, etc. > The hosted engine running on ysmha02. I got ysmad01 running on > ysmha01, but ysmad02 just would not start at all on ysmha02. I did a > run once and set ysmad02 to start on ysmha01 and that works. > > When attempting to start or migrate ysmad02 on ysmha02, if I do a > virsh -r list on ysmha02, I just see the state as: "Shut off" and the > VM just does not run on that hypervisor. > > Diego > > > > On Thu, Jul 16, 2015 at 3:01 AM, Omer Frenkel <ofren...@redhat.com> wrote: >> >> >> ----- Original Message ----- >>> From: "Diego Remolina" <dijur...@gmail.com> >>> To: Users@ovirt.org >>> Sent: Thursday, July 16, 2015 7:45:43 AM >>> Subject: [ovirt-users] Cannot run specific VM in one node >>> >>> Hi, >>> >>> Was wondering if I can get some help with this particular situation. I >>> have two ovirt cluster nodes. I had a VM running in node2 and tried to >>> move it to node1. The move failed and the machine was created and >>> paused in both nodes. I tried stopping migration, shutting down the >>> machine, etc but none of that worked. >>> >>> So I decided to simply look for the process number and I killed it for >>> that VM. After that, I was not able to get the VM to run in any of the >>> nodes, so I rebooted them both. >>> >>> At this point, the vm will *not* start in node2 at all. When I try to >>> start it, it just sits there and if I do: >>> >>> virsh -r list >>> >>> from the command line, the output says the vm state is "shut off". >>> >>> I am able to user Run Once to fire up the VM in node 1, but I cannot >>> migrate it to node2. >>> >>> How can I clear this problematic state for node 2? >> >> please attach engine + vdsm logs for the time of the failure >> >>> >>> Thanks, >>> >>> Diego >>> _______________________________________________ >>> Users mailing list >>> Users@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users