All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Alex Braunegg <alex.braunegg@gmail.com>, xen-devel@lists.xen.org
Cc: 'Ian Jackson' <Ian.Jackson@eu.citrix.com>,
	'Wei Liu' <wei.liu2@citrix.com>,
	'Jan Beulich' <JBeulich@suse.com>,
	'Andrew Cooper' <Andrew.Cooper3@citrix.com>
Subject: Re: [BUG} libxl.c:5947:libxl_send_trigger: Send trigger 'reset' failed: Function not implemented
Date: Wed, 10 Feb 2016 09:32:32 +0000	[thread overview]
Message-ID: <1455096752.19857.114.camel@citrix.com> (raw)
In-Reply-To: <56ba897e.010f620a.d7d7b.1cbc@mx.google.com>

On Wed, 2016-02-10 at 11:51 +1100, Alex Braunegg wrote:
> Many thanks for the detailed information and analysis - so potentially
> chasing something that cannot occur to a guest if the Windows PV Drivers
> are not installed.
> 
> > You might want to change this now. ;-)
> 
> No issue there - the guest was destroyed after grabbing the debug
> details. The full .cfg might be useful for someone else down the track.
> 
> > I'd strongly recommend installing some PV drivers into the guest, 
> 
> So this leads to another question. Is there a mechanism that exists today
> that allows via xl or some other Xen tool to 'probe' the guest as to if
> the PV drivers are loaded?

There is a function internal to libxl (libxl__domain_pvcontrol) which
answers this question (by looking at the callback IRQ).

I suppose it would be reasonable to expose that formally in the libxl
public API in some form, although it is also the case that any function
which uses PV control mechanisms performs (or at least should perform) this
check and return ERROR_NOPARAVIRT if pv control is not avaiable, so
application code can try PV and fallback to other methods (as xl does).

[...]
> Including ' xenctrl.h' in xl_cmdimpl.c would also be needed so that the
> function 'xc_hvm_param_get' could be used.

libxc (xenctrl.h) is not a stable interface and it is a design goal of
libxl that toolstacks should only need to use libxl interfaces for their
toolstack oriented operations. So this functionality would need to be
reflected in the stable libxl API for use by xl (and libvirt, and other
toolstacks people might write)

Ian.

  reply	other threads:[~2016-02-10  9:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-03 21:50 [BUG} libxl.c:5947:libxl_send_trigger: Send trigger 'reset' failed: Function not implemented Alex Braunegg
2016-02-04 10:57 ` Ian Campbell
2016-02-04 23:08   ` Alex Braunegg
2016-02-09 10:28     ` Ian Campbell
2016-02-10  0:51       ` Alex Braunegg
2016-02-10  9:32         ` Ian Campbell [this message]
2016-02-10 22:30           ` Alex Braunegg
2016-02-11  9:33             ` Ian Campbell
2016-02-08 21:48   ` Alex Braunegg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1455096752.19857.114.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=alex.braunegg@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.