xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* help: /dev/xen/gntdev
@ 2010-02-12  4:11 Mukesh Rathor
  2010-02-12  9:50 ` Jan Beulich
  0 siblings, 1 reply; 3+ messages in thread
From: Mukesh Rathor @ 2010-02-12  4:11 UTC (permalink / raw)
  To: Xen-devel@lists.xensource.com

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: help: /dev/xen/gntdev
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Beulich @ 2010-02-12  9:50 UTC (permalink / raw)
  To: Mukesh Rathor; +Cc: Xen-devel@lists.xensource.com

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: help: /dev/xen/gntdev
  2010-02-12  9:50 ` Jan Beulich
@ 2010-02-16 22:14   ` Mukesh Rathor
  0 siblings, 0 replies; 3+ messages in thread
From: Mukesh Rathor @ 2010-02-16 22:14 UTC (permalink / raw)
  To: Jan Beulich; +Cc: Xen-devel@lists.xensource.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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-02-16 22:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).