RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

vdsm does not catch reboot event sent by libvirt hence there is no indication in rhev-m that vm is rebooting. 
event looks as follows: 

libvirtEventLoop::DEBUG::2010-06-07 04:29:14,246::vm::1208::vds.vmlog.d9d4ddad-c8a0-4177-88c9-a38e17771a15::reboot event

scenario goes as follows: 

1) start linux vm 
2) make sure status changes to up 
3) login to vm (ssh) and initiate the following command: init 6/reboot

logs shows that libvirt aware that machine is rebooting.

vdsm 4.9-8 
libvirt-0.8.1-7.el6.x86_64

haven't tried on windows.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

actually, the log shows that the reboot event was caught. For some reason, however, this was not reflected in the state of the VM which did not change to RebootInProgress.

Haim, I currently see RebootInProgress just fine. Would you verify that?

yep, I see RebootInProgress event after initiating reboot from within the guest.

one question though and excuse me from being nudge; the reboot appears only after 
grub finish to load, is it on purpose or a question of timing for event to catch by vdsm ? 

libvirt-0.8.1-19.el6.x86_64
qemu-kvm-0.12.1.2-2.97.el6.x86_64
vdsm-4.9-11.el6.x86_64
2.6.32-52.el6.x86_64

anyway, move to verified.