CONFIG_XEN_PHYSDEV_ACCESS in domainU

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

CONFIG_XEN_PHYSDEV_ACCESS in domainU

Patrice-2
Hi,

We have been using Xen for several months now and it works real great (we
have it running on Intel SR1300, Intel SR2300 and PowerEdge 1850).

Now we need one unpriviledged host to be able to access directly 2 PCI cards
(RocketPort and modem on PowerEdge 1850):
As soon as I set CONFIG_XEN_PHYSDEV_ACCESS=y for a domainU, I can no longer
start the virtual host, there is nothing on the console but I get the
following from the xend log:

[2005-06-09 15:13:34 xend] DEBUG (XendDomainInfo:720) init_domain> Created
domain=6 name=debian-test memory=256
[2005-06-09 15:13:34 xend] INFO (console:94) Created console id=16 domain=6
port=9606
[2005-06-09 15:13:34 xend] DEBUG (XendDomainInfo:1130) Creating vbd dom=6
uname=file:/var/lib/xen/vfs/debian-test
[2005-06-09 15:13:34 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 6 0>
[2005-06-09 15:13:34 xend] DEBUG (XendDomainInfo:1178) Creating pci device
dom=6 bus=3 dev=b func=0
[2005-06-09 15:13:34 xend] DEBUG (XendDomainInfo:1107) Creating vif dom=6
vif=0 mac=aa:00:00:2b:bd:41
[2005-06-09 15:13:34 xend] INFO (XendRoot:113) EVENT> xend.console.create
[16, 6, 9606]
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.domain.create
['debian-test', '6']
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.domain.unpause
['debian-test', '6']
[2005-06-09 15:13:35 xend] INFO (console:44) Console connected 16 127.0.0.1
2970
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.console.connect
[16, '127.0.0.1', 2970]
[2005-06-09 15:13:35 xend] DEBUG (XendDomain:244) XendDomain>reap> domain
died name=debian-test id=6
[2005-06-09 15:13:35 xend] INFO (XendDomain:564) Destroying domain:
name=debian-test
[2005-06-09 15:13:35 xend] DEBUG (XendDomainInfo:665) Destroying vifs for
domain 6
[2005-06-09 15:13:35 xend] DEBUG (netif:305) Destroying vif domain=6 vif=0
[2005-06-09 15:13:35 xend] DEBUG (XendDomainInfo:674) Destroying vbds for
domain 6
[2005-06-09 15:13:35 xend] DEBUG (blkif:552) Destroying blkif domain=6
[2005-06-09 15:13:35 xend] DEBUG (blkif:408) Destroying vbd domain=6 idx=0
[2005-06-09 15:13:35 xend] DEBUG (XendDomainInfo:634) Closing console,
domain 6
[2005-06-09 15:13:35 xend] DEBUG (XendDomainInfo:622) Closing channel to
domain 6
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.virq 4
[2005-06-09 15:13:35 xend] DEBUG (blkif:363) Unbinding vbd (type file) from
/dev/loop0
[2005-06-09 15:13:35 xend] INFO (console:58) Console disconnected 16
127.0.0.1 2970
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.domain.exit
['debian-test', '6', 'crash']
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT> xend.domain.destroy
['debian-test', '6']
[2005-06-09 15:13:35 xend] INFO (XendRoot:113) EVENT>
xend.console.disconnect [16, '127.0.0.1', 2970]
[2005-06-09 15:13:36 xend] INFO (XendRoot:113) EVENT> xend.domain.died
['debian-test', '6']

How can I get more clues to what's going on ? Anybody able to get a similar
configuration to work ?

Thanks for any help.

Patrice


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: CONFIG_XEN_PHYSDEV_ACCESS in domainU

Maurice-4
> --- Urspr?ngliche Nachricht ---
> Von: "Patrice" <[hidden email]>
>
> Now we need one unpriviledged host to be able to access directly 2 PCI
> cards
> (RocketPort and modem on PowerEdge 1850):
> As soon as I set CONFIG_XEN_PHYSDEV_ACCESS=y for a domainU, I can no
> longer
> start the virtual host, there is nothing on the console but I get the
> following from the xend log:

Same here, tried with several different combinations of kernel-configs.. Ive
also asked (about 4 month ago) if anybody has a working kernel-config with
CONFIG_XEN_PHYSDEV_ACCESS enabled, but no response :-(

Greetings Maurice

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: CONFIG_XEN_PHYSDEV_ACCESS in domainU

David Muench
In reply to this post by Patrice-2
I think I ran into a similar problem. I had to also enable the domain
0 config option to get the kernel to work at all. I'm not sure if
that's expected or if this is a bug as I'm relatively new to Xen.

Once I did that however, my PCI cards worked great in a domU.

Dave

On 6/9/05, Patrice <[hidden email]> wrote:

> Hi,
>
> We have been using Xen for several months now and it works real great (we
> have it running on Intel SR1300, Intel SR2300 and PowerEdge 1850).
>
> Now we need one unpriviledged host to be able to access directly 2 PCI cards
> (RocketPort and modem on PowerEdge 1850):
> As soon as I set CONFIG_XEN_PHYSDEV_ACCESS=y for a domainU, I can no longer
> start the virtual host, there is nothing on the console but I get the
> following from the xend log:

--
David Muench - [hidden email]
Jabber ID: [hidden email]

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users