|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Device driver domains
Hi,
I am interested in running device drivers on dedicated drivers domains
(non dom0).
My understanding is that this was possible in 2.0 but it is still not
available in 3.0
I tried running Xen 2.0.7 to see if I could create a driver domain,
but that was not successful. If I set CONFIG_XEN_PHYSDEV_ACCESS for
domU, the domain dies very early in the boot process. Nothing gets
printed in the domU console after the " ** REMOTE CONSOLE: CTRL-] TO
QUIT **" message. And Xen prints the following messages:
(XEN) (file=extable.c, line=71) Pre-exception: fc52d69d -> fc52d724
(XEN) (file=traps.c, line=464) Page fault: fc52d739 -> fc505a60
I was wondering if anyone used driver domains successfully in 2.0.7?
Could device access in domU be broken in 2.0.7 ?
What was the latest version of Xen for which someone have reported
device drivers were used successfully?
In fact, I am interested in having this functionality in Xen 3.0. Can
someone explain why the code that existed in 2.0 is not available in
3.0? I would like to understand what are the issues and how hard would
be to have this functionality available in Xen 3.0. I would appreciate
any comment or explanation
Thanks
Renato
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-devel] Device driver domains,
Santos, Jose Renato G <=
|
|
|
|
|