On Fri, 2016-02-05 at 10:08 +1100, Alex Braunegg wrote:
I'm copying the other tools maintainers as well as the x86 guys.
> Hi Ian,
>
> Below is the output requested:
>
> Guest Configuration:
>
> -------------------------------------------------------------
>
> builder='hvm'
> memory = 2048
> shadow_memory = 8
> uuid = '27f4787c-89b2-46ab-a797-96ea6e84c511'
> name = 'Windows_2008_R2'
> vif = [ 'bridge=br0, mac=00:16:3e:96:49:10' ]
> disk = [
> '/dev/zvol/storage0/xen/Windows_2008_R2/disk_sda,,hda','/storage0/data-
> shares/iso/en_windows_server_2008_r2_standard_enterprise_datacenter_and_w
> eb_x64_dvd_x15-59754.iso,,hdc,cdrom' ]
> # boot on floppy (a), hard disk (c) or CD-ROM (d)
> # default: hard disk, cd-rom, floppy
> boot='dc'
> sdl=0
> vnc=1
> vncconsole=1
> vnclisten='0.0.0.0'
> stdvga=1
> serial='pty'
> usbdevice='tablet'
> vncpasswd='bpC7fKtsDy'
You might want to change this now. ;-)
> vncdisplay=2
> localtime=1
> audio='1'
> soundhw='ac97'
>
> -------------------------------------------------------------
>
> Reboot Log:
> ===========
>
> [root@mynas-s5000xvn /]# /usr/sbin/xl -vvv reboot -F Windows_2008_R2
> Rebooting domain 9
> PV control interface not available: sending ACPI reset button event.
> libxl: error: libxl.c:5947:libxl_send_trigger: Send trigger 'reset'
> failed: Function not implemented
> reboot failed (rc=-3)
-3 here is libxl's ERROR_FAIL, which is a bit non-informative (and not to
be confused, as I just did, with an ESRCH error from the hypervisor in this
context).
However the "Function not implemented" tells us, I think, that the
hypervisor has returned ENOSYS.
The xl reboot command results in
libxl_send_trigger(ctx, dom, LIBXL_TRIGGER_RESET, 0)
which becomes a XEN_DOMCTL_sendtrigger hypercall with the
XEN_DOMCTL_SENDTRIGGER_RESET option.
However the hypervisor doesn't do anything with this event, and just
returns ENOSYS.
The only triggers which Xen supports injecting are NMI, ACPI POWER and ACPI
SLEEP. I don't know if this is due to ACPI only having those as a concept,
or that Xen just doesn't implement ACPI RESET for some reason.
In any case it seems like a bug in the toolstack to me that it offers the
tantalising -F option to xl reboot when there appears to be no possibility
of it working. In particular the man page says:
If PV drivers are not present but you have configured the guest OS
to behave appropriately you may be able to use the I<-F> option
trigger a reset button press.
Which AFAICT is all lies, I can only apologise for this :-/
> xc: debug: hypercall buffer: total allocations:18 total releases:18
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:12 misses:2 toobig:4
> [root@mynas-s5000xvn /]#
>
>
> Shutdown Log:
> =============
>
> [root@mynas-s5000xvn /]# /usr/sbin/xl -vvv shutdown -F
> Windows_2008_R2
> Shutting down domain 9
> PV control interface not available: sending ACPI power button event.
> xc: debug: hypercall buffer: total allocations:18 total releases:18
> xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> xc: debug: hypercall buffer: cache current size:2
> xc: debug: hypercall buffer: cache hits:12 misses:2 toobig:4
> [root@mynas-s5000xvn /]#
>
>
> During this test, the shutdown of the guest system occurred - so
> potentially the shutdown command is working.
Yes, it seems that it is and should.
Irrespective of all the stuff above about reboot I think that without PV
drivers the only thing Xen can do to the guest is send it an ACPI power
button event, which it is up to the guest to interpret as reboot, power
off, hibernate, etc, I presume this can be configured somewhere in the
depths of the Windows control centre somewhere.
I'd strongly recommend installing some PV drivers into the guest, not only
will you gain reboot control etc but the I/O performance will be much
better.
Ian
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
