xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Braunegg" <alex.braunegg@gmail.com>
To: 'Ian Campbell' <ian.campbell@citrix.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 11:51:05 +1100	[thread overview]
Message-ID: <56ba897e.010f620a.d7d7b.1cbc@mx.google.com> (raw)
In-Reply-To: <1455013705.19857.30.camel@citrix.com>

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?

If not - it appears that:

	xc_hvm_param_get(ctx->xch, domid, HVM_PARAM_CALLBACK_IRQ, &pvdriver);

would get a return value that would equate to if the PV drivers are loaded / PV is able to be communicated with.

In list_vm(void), something such as (as part of the cmd line 'xl vm-list':

	uint64_t pvdriver = 0;
	int pv_available;
	pv_available = xc_hvm_param_get(ctx, info[i].domid, HVM_PARAM_CALLBACK_IRQ, &pvdriver);

to extend:	

	printf(LIBXL_UUID_FMT "  %d    %-30s\t%d\n", LIBXL_UUID_BYTES(info[i].uuid),info[i].domid, domname, pv_available);

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

I am yet to test / try this but any suggestions is greatly appreciated.

Best regards,

Alex

  reply	other threads:[~2016-02-10  0:51 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 [this message]
2016-02-10  9:32         ` Ian Campbell
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=56ba897e.010f620a.d7d7b.1cbc@mx.google.com \
    --to=alex.braunegg@gmail.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).