Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Pry Mar]

[-- Attachment #1.1: Type: text/plain, Size: 501 bytes --]

Hello,

<quote>

Credit2 scheduler rocks

still start up Problem with xenstored/oxenstored - I have to start it manually

must be in Correlation with systemd

</quote>
xen 4.8-rc2 configure
http://paste.ubuntu.net/23366138/

Above is a link to my `./configure` call in Xenial when building xen
4.8-rc2.
It is easier to use xen when you do a proper configure of the build. The
xenstored service should start with no trouble too.

I tested:
pvgrub
OVMF with portable bios

and they work fine.

PryMar56

[-- Attachment #1.2: Type: text/html, Size: 748 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Juergen Schinker]

 
> 
> still start up Problem with xenstored/oxenstored - I have to start it manually
> 
> must be in Correlation with systemd
> </quote>
> xen 4.8-rc2 configure
> [ http://paste.ubuntu.net/23366138/ | http://paste.ubuntu.net/23366138/ ]
> 
> Above is a link to my `./configure` call in Xenial when building xen 4.8-rc2.
> It is easier to use xen when you do a proper configure of the build. The
> xenstored service should start with no trouble too.
> 
> I tested:
> pvgrub
 
Then why don't you write an Tes Report ?

and I tested "your" Flags they set mostly Feature which are defaults and you didn't test or report

so what is the Point?

Xen should compile cleanly with none or all Flags set...

I don't know which systemd service starts xentored coz it refuses intentionally the restart and is not supposed to be an service on its own

maybe the devs can shed some light


J 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Wei Liu]

On Mon, Oct 24, 2016 at 02:14:26PM +0100, Juergen Schinker wrote:
>  
> > 
> > still start up Problem with xenstored/oxenstored - I have to start it manually
> > 
> > must be in Correlation with systemd
> > </quote>
> > xen 4.8-rc2 configure
> > [ http://paste.ubuntu.net/23366138/ | http://paste.ubuntu.net/23366138/ ]
> > 
> > Above is a link to my `./configure` call in Xenial when building xen 4.8-rc2.
> > It is easier to use xen when you do a proper configure of the build. The
> > xenstored service should start with no trouble too.
> > 
> > I tested:
> > pvgrub
>  
> Then why don't you write an Tes Report ?

Juergen, please be courteous to fellow users. :-)

There could be many reasons why Pry didn't send out a report. I think we
should be grateful that he took the time to response to the issue you
discovered.

> 
> and I tested "your" Flags they set mostly Feature which are defaults
> and you didn't test or report
> 
> so what is the Point?
> 
> Xen should compile cleanly with none or all Flags set...
> 

I bet to differ.

Those flags exist for a reason -- so that users can configure Xen as
they see fit.

It is quite often downstream packagers need to tune the paths to fit
into the file system hierarchy of his or her distro.


> I don't know which systemd service starts xentored coz it refuses
> intentionally the restart and is not supposed to be an service on its
> own
> 
> maybe the devs can shed some light

There are a bunch of systemd service files under
tools/hotplug/Linux/systemd. I think you should build and install all of
them. The logic in those scripts should sort out all the dependencies
all by themselves.


Wei.


> 
> 
> J 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Juergen Schinker]

  
>> Then why don't you write an Tes Report ?
> 
> Juergen, please be courteous to fellow users. :-)
> 
sorry

> There could be many reasons why Pry didn't send out a report. I think we
> should be grateful that he took the time to response to the issue you
> discovered.
> 
>> 
>> and I tested "your" Flags they set mostly Feature which are defaults
>> and you didn't test or report
>> 
>> so what is the Point?
>> 
>> Xen should compile cleanly with none or all Flags set...
>> 
> 
> I bet to differ.
> 
> Those flags exist for a reason -- so that users can configure Xen as
> they see fit.
> 
> It is quite often downstream packagers need to tune the paths to fit
> into the file system hierarchy of his or her distro.
> 

but you will not say that you have to have a minimum set of Flags and without them it will not compile?
> 

>> I don't know which systemd service starts xentored coz it refuses
>> intentionally the restart and is not supposed to be an service on its
>> own
>> 
>> maybe the devs can shed some light
> 
> There are a bunch of systemd service files under
> tools/hotplug/Linux/systemd. I think you should build and install all of
> them. The logic in those scripts should sort out all the dependencies
> all by themselves.

hm but none of the others services calls xenstored so

is xenstore supposed to start just because it is systemd enabled?

J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Wei Liu]

On Mon, Oct 24, 2016 at 06:57:50PM +0100, Juergen Schinker wrote:
>   
> >> Then why don't you write an Tes Report ?
> > 
> > Juergen, please be courteous to fellow users. :-)
> > 
> sorry
> 
> > There could be many reasons why Pry didn't send out a report. I think we
> > should be grateful that he took the time to response to the issue you
> > discovered.
> > 
> >> 
> >> and I tested "your" Flags they set mostly Feature which are defaults
> >> and you didn't test or report
> >> 
> >> so what is the Point?
> >> 
> >> Xen should compile cleanly with none or all Flags set...
> >> 
> > 
> > I bet to differ.
> > 
> > Those flags exist for a reason -- so that users can configure Xen as
> > they see fit.
> > 
> > It is quite often downstream packagers need to tune the paths to fit
> > into the file system hierarchy of his or her distro.
> > 
> 
> but you will not say that you have to have a minimum set of Flags and without them it will not compile?

I think the expectation is that ./configure will do necessary probing.
If it discovers something is missing, it stops.

So I guess the "minimum set of flags" should be "none".

But, there is a caveat: Xen's configure can't cover completely what is
needed by other software we need, so there could be some fallouts.

In any case, fixing the build is probably the easier ones of all the
bugs we face.

> > 
> 
> >> I don't know which systemd service starts xentored coz it refuses
> >> intentionally the restart and is not supposed to be an service on its
> >> own
> >> 
> >> maybe the devs can shed some light
> > 
> > There are a bunch of systemd service files under
> > tools/hotplug/Linux/systemd. I think you should build and install all of
> > them. The logic in those scripts should sort out all the dependencies
> > all by themselves.
> 
> hm but none of the others services calls xenstored so
> 

There is one called xenstored.service.

> is xenstore supposed to start just because it is systemd enabled?
> 

I think so -- when you configure it properly when building Xen, those
files will be properly installed to the desired location of your test
host.  Make sure you have systemd development package(s) installed on
your build host.

My limited experience with those script shows that they work just fine.
I don't remember making any special adjustment to them.

Wei.

> J

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Juergen Schinker]

 
> There is one called xenstored.service.
> 
>> is xenstore supposed to start just because it is systemd enabled?
>> 
> 
> I think so -- when you configure it properly when building Xen, those
> files will be properly installed to the desired location of your test
> host.  Make sure you have systemd development package(s) installed on
> your build host.
> 
> My limited experience with those script shows that they work just fine.
> I don't remember making any special adjustment to them.
> 
> Wei.
 
well this is what I get

root@xen:~# systemctl enable xenstored
Created symlink /etc/systemd/system/multi-user.target.wants/xenstored.service → /usr/local/lib/systemd/system/xenstored.service.
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.
root@xen:~# systemctl status xenstored
● xenstored.service - The Xen xenstore
   Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 5h ago
 Main PID: 1141 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/xenstored.service

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Wei Liu]

On Mon, Oct 24, 2016 at 07:49:40PM +0100, Juergen Schinker wrote:
> 
>  
> > There is one called xenstored.service.
> > 
> >> is xenstore supposed to start just because it is systemd enabled?
> >> 
> > 
> > I think so -- when you configure it properly when building Xen, those
> > files will be properly installed to the desired location of your test
> > host.  Make sure you have systemd development package(s) installed on
> > your build host.
> > 
> > My limited experience with those script shows that they work just fine.
> > I don't remember making any special adjustment to them.
> > 
> > Wei.
>  
> well this is what I get
> 
> root@xen:~# systemctl enable xenstored
> Created symlink /etc/systemd/system/multi-user.target.wants/xenstored.service → /usr/local/lib/systemd/system/xenstored.service.
> The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
> settings in the [Install] section, and DefaultInstance for template units).
> This means they are not meant to be enabled using systemctl.

I don't follow.

Doesn't xenstored.service have "WantedBy=multi-user.target"?

> Possible reasons for having this kind of units are:
> 1) A unit may be statically enabled by being symlinked from another unit's
>    .wants/ or .requires/ directory.
> 2) A unit's purpose may be to act as a helper for some other unit which has
>    a requirement dependency on it.
> 3) A unit may be started when needed via activation (socket, path, timer,
>    D-Bus, udev, scripted systemctl call, ...).
> 4) In case of template units, the unit is meant to be enabled with some
>    instance name specified.
> root@xen:~# systemctl status xenstored
> ● xenstored.service - The Xen xenstore
>    Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled)
>    Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 5h ago
>  Main PID: 1141 (code=exited, status=0/SUCCESS)
>    CGroup: /system.slice/xenstored.service

            ^ no more output after this?

I have:

 Main PID: 908 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/xenstored.service
           └─972 /usr/local/sbin/xenstored --pid-file /var/run/xen/xenstored.pid


Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Juergen Schinker]

 
> 
> Doesn't xenstored.service have "WantedBy=multi-user.target"?
> 

/usr/local/lib/systemd/system/xenstored.service

[Unit]
Description=The Xen xenstore
Requires=proc-xen.mount var-lib-xenstored.mount
After=proc-xen.mount var-lib-xenstored.mount
Before=libvirtd.service libvirt-guests.service
RefuseManualStop=true
ConditionPathExists=/proc/xen/capabilities

[Service]
Type=notify
NotifyAccess=all
RemainAfterExit=true
ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities
ExecStart=/etc/xen/scripts/launch-xenstore

[Install]
WantedBy=multi-user.target
Also=proc-xen.mount
Also=var-lib-xenstored.mount


>> Possible reasons for having this kind of units are:
>> 1) A unit may be statically enabled by being symlinked from another unit's
>>    .wants/ or .requires/ directory.
>> 2) A unit's purpose may be to act as a helper for some other unit which has
>>    a requirement dependency on it.
>> 3) A unit may be started when needed via activation (socket, path, timer,
>>    D-Bus, udev, scripted systemctl call, ...).
>> 4) In case of template units, the unit is meant to be enabled with some
>>    instance name specified.
>> root@xen:~# systemctl status xenstored
>> ● xenstored.service - The Xen xenstore
>>    Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor
>>    preset: enabled)
>>    Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 5h ago
>>  Main PID: 1141 (code=exited, status=0/SUCCESS)
>>    CGroup: /system.slice/xenstored.service
> 
>            ^ no more output after this?
> 
> I have:
> 
> Main PID: 908 (code=exited, status=0/SUCCESS)
>   CGroup: /system.slice/xenstored.service
>           └─972 /usr/local/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
 
No more thats it

 
hm this is status today and I haven;t rebootet but remember I started the service by hand

root@xen:~# systemctl status xenstored
● xenstored.service - The Xen xenstore
   Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 23h ago
 Main PID: 1141 (code=exited, status=0/SUCCESS)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/xenstored.service

Oct 23 14:41:15 xen systemd[1]: Starting The Xen xenstore...
Oct 23 14:41:15 xen systemd[1]: Started The Xen xenstore.
root@xen:~# 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Wei Liu]

On Tue, Oct 25, 2016 at 01:55:14PM +0100, Juergen Schinker wrote:
>  
> > 
> > Doesn't xenstored.service have "WantedBy=multi-user.target"?
> > 
> 
> /usr/local/lib/systemd/system/xenstored.service
> 
> [Unit]
> Description=The Xen xenstore
> Requires=proc-xen.mount var-lib-xenstored.mount
> After=proc-xen.mount var-lib-xenstored.mount
> Before=libvirtd.service libvirt-guests.service
> RefuseManualStop=true
> ConditionPathExists=/proc/xen/capabilities
> 
> [Service]
> Type=notify
> NotifyAccess=all
> RemainAfterExit=true
> ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities
> ExecStart=/etc/xen/scripts/launch-xenstore
> 
> [Install]
> WantedBy=multi-user.target
> Also=proc-xen.mount
> Also=var-lib-xenstored.mount

This looks right.

> 
> 
> >> Possible reasons for having this kind of units are:
> >> 1) A unit may be statically enabled by being symlinked from another unit's
> >>    .wants/ or .requires/ directory.
> >> 2) A unit's purpose may be to act as a helper for some other unit which has
> >>    a requirement dependency on it.
> >> 3) A unit may be started when needed via activation (socket, path, timer,
> >>    D-Bus, udev, scripted systemctl call, ...).
> >> 4) In case of template units, the unit is meant to be enabled with some
> >>    instance name specified.
> >> root@xen:~# systemctl status xenstored
> >> ● xenstored.service - The Xen xenstore
> >>    Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor
> >>    preset: enabled)
> >>    Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 5h ago
> >>  Main PID: 1141 (code=exited, status=0/SUCCESS)
> >>    CGroup: /system.slice/xenstored.service
> > 
> >            ^ no more output after this?
> > 
> > I have:
> > 
> > Main PID: 908 (code=exited, status=0/SUCCESS)
> >   CGroup: /system.slice/xenstored.service
> >           └─972 /usr/local/sbin/xenstored --pid-file /var/run/xen/xenstored.pid
>  
> No more thats it
> 
>  
> hm this is status today and I haven;t rebootet but remember I started the service by hand
> 
> root@xen:~# systemctl status xenstored
> ● xenstored.service - The Xen xenstore
>    Loaded: loaded (/usr/local/lib/systemd/system/xenstored.service; enabled; vendor preset: enabled)
>    Active: active (exited) since Sun 2016-10-23 14:41:15 BST; 1 day 23h ago
>  Main PID: 1141 (code=exited, status=0/SUCCESS)
>     Tasks: 0 (limit: 4915)
>    CGroup: /system.slice/xenstored.service
> 
> Oct 23 14:41:15 xen systemd[1]: Starting The Xen xenstore...
> Oct 23 14:41:15 xen systemd[1]: Started The Xen xenstore.

I don't see there is any error. I'm no systemd expert though.

Wei.

> root@xen:~# 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Pry Mar]

[-- Attachment #1.1: Type: text/plain, Size: 3231 bytes --]

Juergen,

Can we see your actual `./configure *` line? Were you able to build the
included qemu-xen and stubdom/pvgrub?

By the way, here is the Debian way to configure the Xen in repo:
(from https://anonscm.debian.org/cgit/pkg-xen/xen.git/tree/debian/rules.real
)
$(STAMPS_DIR)/setup-utils_$(ARCH):
    @rm -rf $(DIR)
    mkdir -p $(DIR)
    cp -al $(SOURCE_FILES) $(DIR)
    cp --remove-destination /usr/share/misc/config.guess
/usr/share/misc/config.sub $(DIR)
    cd $(DIR); \
        WGET=/bin/false \
        ./configure \
            --disable-docs --disable-stubdom --disable-xen \
            --prefix=/usr \
            --includedir=/usr/include \
            --libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
            --mandir=/usr/share/man \
            --infodir=/usr/share/info \
            --sysconfdir=/etc \
            --localstatedir=/var \
            --disable-blktap1 \
            --disable-blktap2 \
            --disable-ocamltools \
            --disable-qemu-traditional --disable-rombios \
            --with-system-qemu=/usr/bin/qemu-system-i386 \
            --with-system-seabios=/usr/share/seabios/bios-256k.bin
    @$(stamp)

See how they disable and outsource so many parts of upstream Xen?

thanks,
PryMar56

On Mon, Oct 24, 2016 at 6:27 AM, Wei Liu <wei.liu2@citrix.com> wrote:

> On Mon, Oct 24, 2016 at 02:14:26PM +0100, Juergen Schinker wrote:
> >
> > >
> > > still start up Problem with xenstored/oxenstored - I have to start it
> manually
> > >
> > > must be in Correlation with systemd
> > > </quote>
> > > xen 4.8-rc2 configure
> > > [ http://paste.ubuntu.net/23366138/ | http://paste.ubuntu.net/
> 23366138/ ]
> > >
> > > Above is a link to my `./configure` call in Xenial when building xen
> 4.8-rc2.
> > > It is easier to use xen when you do a proper configure of the build.
> The
> > > xenstored service should start with no trouble too.
> > >
> > > I tested:
> > > pvgrub
> >
> > Then why don't you write an Tes Report ?
>
> Juergen, please be courteous to fellow users. :-)
>
> There could be many reasons why Pry didn't send out a report. I think we
> should be grateful that he took the time to response to the issue you
> discovered.
>
> >
> > and I tested "your" Flags they set mostly Feature which are defaults
> > and you didn't test or report
> >
> > so what is the Point?
> >
> > Xen should compile cleanly with none or all Flags set...
> >
>
> I bet to differ.
>
> Those flags exist for a reason -- so that users can configure Xen as
> they see fit.
>
> It is quite often downstream packagers need to tune the paths to fit
> into the file system hierarchy of his or her distro.
>
>
> > I don't know which systemd service starts xentored coz it refuses
> > intentionally the restart and is not supposed to be an service on its
> > own
> >
> > maybe the devs can shed some light
>
> There are a bunch of systemd service files under
> tools/hotplug/Linux/systemd. I think you should build and install all of
> them. The logic in those scripts should sort out all the dependencies
> all by themselves.
>
>
> Wei.
>
>
> >
> >
> > J
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > https://lists.xen.org/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 4659 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Juergen Schinker]

* Hardware:
 Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz
 Sandisk SSD
 32G Ram
* Software:

Debian Stretch/testing is dom0
 
* Guest operating systems:

Guests Ubuntu 14.04 LTS Debian Stretch/Sid 

Ubuntu 16.10 with latest 4.8 kernel crashes
 
* Functionality tested:
xl 
creating booting 
pygrub
credit2

* Comments:

 
Credit2 scheduler rocks  

still start up Problem with xenstored/oxenstored - I have to start it manually

must be in Correlation with systemd

 host                   : xen
release                : 4.7.0-1-amd64
version                : #1 SMP Debian 4.7.6-1 (2016-10-07)
machine                : x86_64
nr_cpus                : 4
max_cpu_id             : 3
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 2
cpu_mhz                : 2312
hw_caps                : b7ebfbff:77bae3ff:28100800:00000001:00000001:00000281:00000000:00000100
virt_caps              : hvm hvm_directio
total_memory           : 32711
free_memory            : 84
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 8
xen_extra              : .0-rc
xen_version            : 4.8.0-rc
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 
xen_scheduler          : credit2
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Thu Sep 1 10:38:27 2016 +0100 git:a05b4d8
xen_commandline        : placeholder sched=credit2 iommu=1
cc_compiler            : gcc (Debian 6.2.0-6) 6.2.0 20161010
cc_compile_by          : root
cc_compile_domain      : 
cc_compile_date        : Fri Oct 21 15:48:52 BST 2016
build_id               : c2e35d4ffe8983af1abe9b800e9905fc128242f9
xend_config_format     : 4

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: Test Xen 4.8 RC3 FULL SUCCESS 21.10.16

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 668 bytes --]

On Fri, 2016-10-21 at 22:27 +0100, Juergen Schinker wrote: 
> * Functionality tested:
> xl 
> creating booting 
> pygrub
> credit2
> 
Cool!

> * Comments:
>  
> Credit2 scheduler rocks  
> 
Wow, I'm quite interested about this line, actually!

So, first of all, thanks a lot for testing it.

Can I ask what you did with it, and why you think it rocks? :-D

Thanks and Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel