xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: help: /dev/xen/gntdev
Date: Tue, 16 Feb 2010 14:14:12 -0800	[thread overview]
Message-ID: <20100216141412.2e9f4782@mantra.us.oracle.com> (raw)
In-Reply-To: <4B753293020000780002F379@vpn.id2.novell.com>

Forgot to mention, rebuilding dom0 with gntdev (CONFIG_XEN_GRANT_DEV)
resolved the issue. Thanks Jan. 

Mukesh


On Fri, 12 Feb 2010 09:50:59 +0000
"Jan Beulich" <JBeulich@novell.com> wrote:

> Do you have the gntdev driver loaded (or built into your kernel)?
> 
> Jan
> 
> >>> Mukesh Rathor <mukesh.rathor@oracle.com> 12.02.10 05:11 >>>
> Hi
> 
> I'm trying to upgrade my environment from xen 3.4.0 to xen 4.0 via
> rpm that fits in our product. I installed new tools and xen, and it
> looks like I am missing a step.
> 
> In 4.0 qemu DEVOPS_FLAG_NEED_GNTDEV was added to xen_console_ops. This
> results in xc_gnttab_open() being called which calls
> xc_find_device_number() to get device nums for /dev/xen/gntdev so it
> can mknod. xc_find_device_number() is failing because there is no
> entry in the the sysfs.
> 
> So, can someone please advise how the entry is created in the sysfs?
> The exact path it's looking: /sys/class/misc/gntdev/dev
> 
> 
> thanks,
> Mukesh
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com 
> http://lists.xensource.com/xen-devel

      reply	other threads:[~2010-02-16 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  4:11 help: /dev/xen/gntdev Mukesh Rathor
2010-02-12  9:50 ` Jan Beulich
2010-02-16 22:14   ` Mukesh Rathor [this message]

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=20100216141412.2e9f4782@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@novell.com \
    --cc=Xen-devel@lists.xensource.com \
    /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).