Xen project Mailing List

Hi,

I tried to run script after pause the domain and unpause domain after run script. But I ended up with same error

Below I shared PV device log, and attached my FE and BE driver and script that i used,

root@hikey960:/debian#

[XEN_BUF]xen_vdevb_be_probe(): 124: Probe called. We are good to go.

[ 165.087419] [XEN_BUF]xen_vdevb_be_probe(): 125: ffffffc017fb7000 1

[ 165.093759] [XEN_BUF]xen_vdevb_be_probe(): 137: info->domid: 1

[ 165.099641] [XEN_BUF]xen_vdevb_be_probe(): 138: devicetype: vdevb, nodename: backend/vdevb/1/0, otherend: /local/domain/1/device/vdevb/0

[ 165.112939] [XEN_BUF]xen_vdevb_be_frontend_changed(): 177: dev->state: XenbusStateInitialising-1, frontend_state: XenbusStateInitialising-1

root@hikey960:/debian#

root@hikey960:/debian# xl console debian

[ 22.243570] [XEN_BUF]xen_vdevb_fe_probe(): 24: Probe called. We are good to go.

[ 22.243606] [XEN_BUF]xen_vdevb_fe_probe(): 25: ffffffc0160b4000 0

[ 22.243620] [XEN_BUF]xen_vdevb_fe_probe(): 38: info->domid: 0

[ 22.243633] [XEN_BUF]xen_vdevb_fe_probe(): 39: devicetype: vdevb, nodename: device/vdevb/0, otherend: /local/domain/0/backend/vdevb/1/0

[ 22.244669] [XEN_BUF]xen_vdevb_fe_backend_changed(): 64: dev->state: XenbusStateInitialising-1, backend_state: XenbusStateInitWait-2

[ 22.244701] [XEN_BUF]frontend_connect(): 53: Connecting the frontend now

[ 22.245866] vdevb vdevb-0: 13 writing new state

[ 22.246085] vdevb vdevb-0: failed to write error node for device/vdevb/0 (13 writing new state)

[ 22.250005] vdevb vdevb-0: 13 writing new state

[ 22.250220] vdevb vdevb-0: failed to write error node for device/vdevb/0 (13 writing new state)

root@hikey960:~#

Thanks,

Omkar B

On Thu, Sep 27, 2018 at 4:33 PM Juergen Gross <jgross@xxxxxxxx> wrote:

On 27/09/2018 12:35, Omkar Bolla wrote:
> Hi,
>
> Sorry, I forgot, I used code from github chapter [2] from that link, and
> I just changed name "mydevice" to "vdevb"

Okay.

>
>> Error 13 is EACCESS. I guess the access rights of the Xenstore nodes
>> are not sufficient to write the needed entries.
> Where I have to provide access rights, i.e from Kernel code or from from
> command line in domain-0 or modify in xen source?

I guess you have your frontend already loaded when running the
script creating the Xenstore entries?

This would explain the problem: as soon as the entries are written
the frontend will react. At this point the access rights are not setup
properly, this is done a little bit later in the script.

Possible solutions are to either load the frontend driver only after
setting up the Xenstore entries, or to pause the domain while doing
so and unpause it afterwards (or start the domain paused, create the
Xenstore entries, and unpause the domain).

The really correct way to do it would be to setup Xenstore in a single
transaction (write all the entries and set access rights).

> Any thing that I have to do/change in xenbits xen-4.8 sources code, to
> add new PV device?

Only if you want to include domain config file entries for your device.

>
>> Did you modify Xen tools (xl/libxl) for adding the new device type?
> No, is it needed to modify some thing in xl/libxl for adding new device
> type?

This was just a question to learn how Xenstore is being initialized
in your scenario.

>
>> If not you need to setup the Xenstore nodes manually.
> Setup manually Xenstore means, using commands?

Yes, like your script does.

Juergen

This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Re: [Xen-devel] Xen PV: Sample new PV driver for buffer sharing between domains