Mailing List Archive

Beaten to it by Dave.

While we're taking about api on cubie, trying to install xe-unikernel-upload wants me to downgrade an awful lot of packages. I really don't want to downgrade from mirage 2.5 to 2.1 - whats the best way of tackling this?

Cheers

Date: Thu, 4 Jun 2015 09:40:20 +0100
Subject: Re: [MirageOS-devel] cubie2 arm image loses mac
From: scott.dj@gmail.com
To: talex5@gmail.com
CC: buzzheavyyear@hotmail.com; mirageos-devel@lists.xenproject.org; xen-api@lists.xenproject.org



On Thu, Jun 4, 2015 at 9:31 AM, Thomas Leonard <talex5@gmail.com> wrote:
On 4 June 2015 at 09:22, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:

> Each time I fire up a '2 and leave it on overnight and then try and ssh into

> the board the following morning, I get a no route to host. Doing an arp on

> my machine will list the ip address but default to a 0:0:0:0:0:0 mac

> address. Incidentally, all of the running unikernels on the board are still

> functioning and accessible as expected - invincible :)

>

> Does anyone have any idea how I can tweak this beast to get it to keep it

> accessible?



Not sure if it's related, but when I tried customising my network

settings I had various network problems that were fixed by 'apt-get

purge xapi-xe xcp-networkd'. I didn't have time to look into the cause

properly, but I think xcp-networkd fights with the OS for control of

the network settings if you're not careful (try "xe pif-list

params=all"). Probably one of the xapi people can explain what it's up

to, if so.

I've not seen that myself, but perhaps someone on the xen-api list (cc:d) could come up with a theory?
Cheers,--
Dave Scott

> On 4 Jun 2015, at 09:49, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:
>
> Beaten to it by Dave.
>
> While we're taking about api on cubie, trying to install xe-unikernel-upload wants me to downgrade an awful lot of packages. I really don't want to downgrade from mirage 2.5 to 2.1 - whats the best way of tackling this?

Ah, the xe-unikernel-upload opam file has a version constraint on the old mirage-types (and so does one of its dependencies: mbr-format).

Try

opam pin add mbr-format git://github.com/djs55/ocaml-mbr#release.0.3
opam pin add xe-unikernel-upload git://github.com/djs55/xe-unikernel-upload#new-mirage-interfaces

I have built these but not tested them. Let me know if they work for you and I’ll try to release them into upstream opam.

Cheers,
Dave

>
> Cheers
>
> Date: Thu, 4 Jun 2015 09:40:20 +0100
> Subject: Re: [MirageOS-devel] cubie2 arm image loses mac
> From: scott.dj@gmail.com
> To: talex5@gmail.com
> CC: buzzheavyyear@hotmail.com; mirageos-devel@lists.xenproject.org; xen-api@lists.xenproject.org
>
>
>
> On Thu, Jun 4, 2015 at 9:31 AM, Thomas Leonard <talex5@gmail.com> wrote:
> On 4 June 2015 at 09:22, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:
> > Each time I fire up a '2 and leave it on overnight and then try and ssh into
> > the board the following morning, I get a no route to host. Doing an arp on
> > my machine will list the ip address but default to a 0:0:0:0:0:0 mac
> > address. Incidentally, all of the running unikernels on the board are still
> > functioning and accessible as expected - invincible :)
> >
> > Does anyone have any idea how I can tweak this beast to get it to keep it
> > accessible?
>
> Not sure if it's related, but when I tried customising my network
> settings I had various network problems that were fixed by 'apt-get
> purge xapi-xe xcp-networkd'. I didn't have time to look into the cause
> properly, but I think xcp-networkd fights with the OS for control of
> the network settings if you're not careful (try "xe pif-list
> params=all"). Probably one of the xapi people can explain what it's up
> to, if so.
>
> I've not seen that myself, but perhaps someone on the xen-api list (cc:d) could come up with a theory?
>
> Cheers,
> --
> Dave Scott
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

> Try
>
> opam pin add mbr-format git://github.com/djs55/ocaml-mbr#release.0.3
> opam pin add xe-unikernel-upload git://github.com/djs55/xe-unikernel-upload#new-mirage-interfaces
>
> I have built these but not tested them. Let me know if they work for you and I’ll try to release them into upstream opam.

Had problems with this, installing:-

opam pin add mbr-format git://github.com/djs55/ocaml-mbr#release.0.3
mbr-format is now git-pinned to git://github.com/djs55/ocaml-mbr#release.0.3

[ERROR] Command "git fetch -q origin +release.0.3:refs/remotes/opam-ref" failed:
# opam-version 1.2.1
# os linux
# command git fetch -q origin +release.0.3:refs/remotes/opam-ref
# path /home/nick/.opam/system/packages.dev/mbr-format
# exit-code 128
# env-file /home/nick/.opam/log/log-14616-1872ec.env
# stdout-file /home/nick/.opam/log/log-14616-1872ec.out
# stderr-file /home/nick/.opam/log/log-14616-1872ec.err
### stderr ###
# fatal: Couldn't find remote ref release.0.3

.... and then
#=== ERROR while installing xe-unikernel-upload.0.4 ===========================#
# opam-version 1.2.1
# os linux
# command make
# path /home/nick/.opam/system/build/xe-unikernel-upload.0.4
# compiler system (4.01.0)
# exit-code 2
# env-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.env
# stdout-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.out
# stderr-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.err
### stdout ###
# [...]
# ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o common.cmx common.ml
# ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o filesystem.cmx filesystem.ml
# ocamlfind ocamldep -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -modules disk_upload.ml > disk_upload.ml.depends
# ocamlfind ocamldep -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -modules ramdisk.ml > ramdisk.ml.depends
# ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o bootable_disk.cmx bootable_disk.ml
# + ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o bootable_disk.cmx bootable_disk.ml
# File "bootable_disk.ml", line 40, characters 4-21:
# Error: Unbound value Partition.connect
# Did you mean disconnect?

.... incidentally, mirage-http 2.3.0 also fails with the latest install of cohttp 0.18.0

> On 4 Jun 2015, at 17:16, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:
>
>
> > Try
> >
> > opam pin add mbr-format git://github.com/djs55/ocaml-mbr#release.0.3
> > opam pin add xe-unikernel-upload git://github.com/djs55/xe-unikernel-upload#new-mirage-interfaces
> >
> > I have built these but not tested them. Let me know if they work for you and I’ll try to release them into upstream opam.
>
> Had problems with this, installing:-
>
> opam pin add mbr-format git://github.com/djs55/ocaml-mbr#release.0.3
> mbr-format is now git-pinned to git://github.com/djs55/ocaml-mbr#release.0.3
>
> [ERROR] Command "git fetch -q origin +release.0.3:refs/remotes/opam-ref" failed:
> # opam-version 1.2.1
> # os linux
> # command git fetch -q origin +release.0.3:refs/remotes/opam-ref
> # path /home/nick/.opam/system/packages.dev/mbr-format
> # exit-code 128
> # env-file /home/nick/.opam/log/log-14616-1872ec.env
> # stdout-file /home/nick/.opam/log/log-14616-1872ec.out
> # stderr-file /home/nick/.opam/log/log-14616-1872ec.err
> ### stderr ###
> # fatal: Couldn't find remote ref release.0.3

oops, my fault — I deleted the branch after I merged it. Try both commands again— the xe-unikernel-upload changes need the ocaml-mbr changes to be built.

Sorry about that,
Dave

>
> .... and then
> #=== ERROR while installing xe-unikernel-upload.0.4 ===========================#
> # opam-version 1.2.1
> # os linux
> # command make
> # path /home/nick/.opam/system/build/xe-unikernel-upload.0.4
> # compiler system (4.01.0)
> # exit-code 2
> # env-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.env
> # stdout-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.out
> # stderr-file /home/nick/.opam/system/build/xe-unikernel-upload.0.4/xe-unikernel-upload-3140-d6d332.err
> ### stdout ###
> # [...]
> # ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o common.cmx common.ml
> # ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o filesystem.cmx filesystem.ml
> # ocamlfind ocamldep -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -modules disk_upload.ml > disk_upload.ml.depends
> # ocamlfind ocamldep -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -modules ramdisk.ml > ramdisk.ml.depends
> # ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o bootable_disk.cmx bootable_disk.ml
> # + ocamlfind ocamlopt -c -g -package xen-api-client.lwt -package xen-api-client -package mbr-format.mirage -package mbr-format.lwt -package mbr-format -package lwt -package io-page.unix -package io-page -package fat-filesystem -package cstruct -package cmdliner -o bootable_disk.cmx bootable_disk.ml
> # File "bootable_disk.ml", line 40, characters 4-21:
> # Error: Unbound value Partition.connect
> # Did you mean disconnect?
>
> .... incidentally, mirage-http 2.3.0 also fails with the latest install of cohttp 0.18.0
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

Excellent, they both compile, but I'm getting an error with the upload:

./dns.xe
Uploading VDI containing unikernel
result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value>OpaqueRef:da16d417-e6d1-c55f-1957-5f2e169d44ff</value></member></struct></value></param></params></methodResponse>]
result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value><array><data><value>OpaqueRef:02d446ef-7760-6096-09cd-909e82b9d706</value></data></array></value></member></struct></value></param></params></methodResponse>]
result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value>OpaqueRef:NULL</value></member></struct></value></param></params></methodResponse>]
result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Failure</value></member><member><name>ErrorDescription</name><value><array><data><value>HANDLE_INVALID</value><value>SR</value><value>OpaqueRef:NULL</value></data></array></value></member></struct></value></param></params></methodResponse>]
result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value></value></member></struct></value></param></params></methodResponse>]
xe-unikernel-upload: internal error, uncaught exception:
Api_errors.Server_error("HANDLE_INVALID", _)

I'm on the sudo's list - is this just a permissions thing or a xapi configuration issue?

Cheers
Nick

> On 4 Jun 2015, at 18:00, Nick Betteridge <buzzheavyyear@hotmail.com> wrote:
>
> Excellent, they both compile, but I'm getting an error with the upload:
>
> ./dns.xe
> Uploading VDI containing unikernel
> result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value>OpaqueRef:da16d417-e6d1-c55f-1957-5f2e169d44ff</value></member></struct></value></param></params></methodResponse>]
> result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value><array><data><value>OpaqueRef:02d446ef-7760-6096-09cd-909e82b9d706</value></data></array></value></member></struct></value></param></params></methodResponse>]
> result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value>OpaqueRef:NULL</value></member></struct></value></param></params></methodResponse>]
> result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Failure</value></member><member><name>ErrorDescription</name><value><array><data><value>HANDLE_INVALID</value><value>SR</value><value>OpaqueRef:NULL</value></data></array></value></member></struct></value></param></params></methodResponse>]
> result = [<?xml version="1.0"?><methodResponse><params><param><value><struct><member><name>Status</name><value>Success</value></member><member><name>Value</name><value></value></member></struct></value></param></params></methodResponse>]
> xe-unikernel-upload: internal error, uncaught exception:
> Api_errors.Server_error("HANDLE_INVALID", _)
>
> I'm on the sudo's list - is this just a permissions thing or a xapi configuration issue?

I think it’s a xapi configuration thing: I think this XMLRPC is saying “the SR with reference ‘NULL’ doesn’t exist. Looking at the code, it gets the SR reference from the Pool.default_SR, so I think this is not set on the server side.

Try running

xe sr-list

# look for a good SR to upload files too — I think the one called “Local storage” or “ffs” should do

xe pool-param-set uuid=<tab> default-SR=<uuid of the SR>

and then it should get further.

Cheers,
Dave


>
> Cheers
> Nick


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

> Try running
>
> xe sr-list
>

This is what I got:

sudo xe sr-list
uuid ( RO) : a0ceb329-83cb-d074-50d9-53846aa40ff7
name-label ( RW): XenServer Tools
name-description ( RW): XenServer Tools ISOs
host ( RO): cubieboard2
type ( RO): iso
content-type ( RO): iso

No SR: I think I need to read through the doc :) - what I wanted to do tomorrow was attempt a full xapi buildroot on a cubieboard4, looks like I'll have to skip that and clear this first.

> # look for a good SR to upload files too — I think the one called “Local storage” or “ffs” should do
>
> xe pool-param-set uuid=<tab> default-SR=<uuid of the SR>
>
> and then it should get further.

Thanks for your help so far!

Very best
Nick