xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Pete Delaney <pdelaney@silver-peak.com>
Cc: "piet.delaney@gmail.com" <piet.delaney@gmail.com>,
	Elaine Huang <ehuang@silver-peak.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: gdbsx - xg_attach:Unable to pause domain:1; failed to attach to domain:1 errno:13
Date: Wed, 27 Aug 2014 11:25:21 -0700	[thread overview]
Message-ID: <20140827112521.6ce2cea3@mantra.us.oracle.com> (raw)
In-Reply-To: <c4cde849a69549aaac4e04dfcadf569f@BY2PR04MB173.namprd04.prod.outlook.com>

On Wed, 27 Aug 2014 03:02:54 +0000
Pete Delaney <pdelaney@silver-peak.com> wrote:

> Hi Mukesh:
> 
>     > Hmm... I just tried and it worked for me, so things are ok it
>     > seems on latest xen/linux. The errno EPERM indicates something
>     > might not be properly setup. Are you able to run other xen
>     > commands like xl list, etc? I see you are running as root, are
>     > you running gdbsx on dom0? 
>  
> Gdbsx runs on dom0, which I believe is the same as running on the
> host when it's booting for Xen support in the grub selection. On the
> host the Xen commands are available as I showed in my initial email,
> I used the "xl list" and "xl pause" commands:
> 
>     >  root@piet-openxen:~# xl list
>     > 	Name                                        ID   Mem
>     > VCPUs  State   Time(s)
>     >	 Domain-0                                     0 14734
>     >	12     r-----    8562.9
>     >	New_PV_Driver                                1  1023
>     >	4     -b----      50.3
>    >  root@piet-openxen:~#
> 
>     > root@piet-openxen-blade:~# xl pause 1
> 
> 
> I was running as root on the host/dom0.

Hmm... that all seems ok then. Can you check your permissions on :

/proc/xen/privcmd


Other possibilites:
  - do you have xsm enabled?

  - can you put a printk in xen file common/domctl.c:

    case XEN_DOMCTL_pausedomain:
        ret = -EINVAL;
+       printk(">>>>>>>>> Pause domain:%d current:%d\n", d->domain_id, 
+              current->domain->domain_id);
        if ( d != current->domain )
            ret = domain_pause_by_systemcontroller(d);
        break;

if you don't see this printk then the problem is in dom0 linux, prob
some permissions either on the privcmd file or somewhere in FS path.

> Wondering if the host kernel has to be configured to support gdb
> attaching with gdbsx.

Nop, at this point you are just not able to establish connection with
xen. gdb is not involved.

-Mukesh

  reply	other threads:[~2014-08-27 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  2:14 gdbsx - xg_attach:Unable to pause domain:1; failed to attach to domain:1 errno:13 Pete Delaney
2014-08-26 22:47 ` Mukesh Rathor
2014-08-27  3:02   ` Pete Delaney
2014-08-27 18:25     ` Mukesh Rathor [this message]
2014-09-16 22:58       ` Pete Delaney
2014-09-17  2:15         ` Mukesh Rathor
2014-09-17  3:21           ` Pete Delaney
2014-09-18  2:11           ` Pete Delaney
2014-09-23  0:10             ` Mukesh Rathor

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=20140827112521.6ce2cea3@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=ehuang@silver-peak.com \
    --cc=pdelaney@silver-peak.com \
    --cc=piet.delaney@gmail.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).