Re: ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16

Re: ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16

[Juergen Schinker]

* Hardware:
 Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz
* Software:

Debian testing is the Host
 
* Guest operating systems:
Guests Ubuntu 14.04 LTS Debian Stretch/Sid Ubuntu 16.04
 
* Functionality tested:
xl 
creating booting 
pygrub

* Comments:

 
I found the Bug - it is the xenstored daemon which doesn't start automagicaly

i start it manually and everything works 

/usr/local/sbin/xenstored

all needed services enabled



systemctl enable xen-qemu-dom0-disk-backend.service
systemctl enable xen-init-dom0.service
systemctl enable xenconsoled.service

nothing usefull in the Logs

Live-patching also works nicely - I tested with "hello world"


how would I know that a new security patch is available?



next I test the new credit2 and RTDS scheduler yay



host                   : xen
release                : 4.7.0-1-amd64
version                : #1 SMP Debian 4.7.5-1 (2016-09-26)
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            : 0
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          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Mon Oct 10 11:10:56 2016 -0700 git:68dc718
xen_commandline        : placeholder ”iommu=pass-through”
cc_compiler            : gcc (Debian 6.2.0-5) 6.2.0 20160927
cc_compile_by          : root
cc_compile_domain      : 
cc_compile_date        : Fri Oct 14 16:52:11 BST 2016
build_id               : e846bc09029d4a0d0eb9e253168aa53e666d5977
xend_config_format     : 4


would it make sense to give every VM all cpu cores and balance via scheduler with differet weightings?

J

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

Re: ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16

[Wei Liu]

On Sat, Oct 15, 2016 at 11:17:06AM +0100, Juergen Schinker wrote:
[...]
> 
> 
> how would I know that a new security patch is available?
> 

Keep an eye on https://xenbits.xen.org/xsa/

> 
> 
> next I test the new credit2 and RTDS scheduler yay
> 
[...]
> 
> would it make sense to give every VM all cpu cores and balance via scheduler with differet weightings?

Play with it however you like.

Wei.

> 
> J

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Wei Liu]

On Mon, Oct 10, 2016 at 04:34:31PM +0100, Ian Jackson wrote:
> Wei Liu writes ("[PATCH for-4.8] ipxe: update to newer commit"):
> > The current commit in tree is rather old. It has come to a point that
> > cherry-picking commits from upstream isn't trivial anymore.
> > 
> > There is long term plan to track ipxe upstream, but for 4.8 release, we
> > should just update ipxe to a newer commit (they are using rolling
> > release model now).
> > 
> > Forward-port the one boot prompt patch that is still relevant and retire
> > the rest which are already in upstream.
> 
> As I said IRL, I think this is a goiod approach.  (I hadn't realised
> we were cloning it rather than getting a tarball from xenbits...)
> 
> How did you choose 827dd1bfee67daa683935ce65316f7e0f057fe1c ?
> 

That's the latest commit -- since upstream wants us to always use the
latest, I just picked that one.

I built that commit with gcc 4.9 and gcc 6.1, both compiled OK.
Realistically I don't expect issues with nic boot roms -- those are the
only things we really use AFAICT.

Wei.

> Ian.

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Wei Liu]

On Wed, Oct 12, 2016 at 05:03:11PM -0400, Boris Ostrovsky wrote:
> On 10/12/2016 05:27 AM, Wei Liu wrote:
> > On Tue, Oct 11, 2016 at 08:31:31PM +0100, Juergen Schinker wrote:
> >>  
> >>> We're going to tag rc2 some time this week. Thanks for help testing Xen!
> >>>
> >>> Wei.
> >>>
> >>>> J
> >>>>
> >>>> ----- On 11 Oct, 2016, at 09:37, Wei Liu wei.liu2@citrix.com wrote:
> >>>>
> >>>>> No, you can try to work around this issue by appending --disable-rombios
> >>>>> to your ./configure invocation. You can test major functionalities of
> >>>>> Xen just fine without rombios.
> >>>>>
> >>>>> Wei.
> >> Now for the fun of it I tried the RELEASE-4.7 
> >>
> >> and it turns out it has no support for xz-decompression 
> >>
> > That's probably because you don't have libzx development package
> > installed when building Xen.
> 
> 
> Which would be a new requirement for building Xen. And it broke our
> (pre-historic) build server that never had it installed.
> 

I don't think it breaks building Xen -- you just can't decompress xz
format file, right? Otherwise Juergen would not have been able to build
Xen.

Wei.

> -boris
> 
> 
> >
> >> so it can't decompress the kernel via pygrub
> >>
> >> what
> > _______________________________________________
> > 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: [PATCH for-4.8] ipxe: update to newer commit

[Juergen Schinker]

Right and still no solution 

there is no xz-dev or libxz-dev;  I installed everything which just looks remote like xz or lzma

building is no problem as I build with

./configure --enable-githttp --enable-systemd --disable-rombios --disable-qemu-traditional --disable-stubdom --disable-docs


I'm thinking of building a special VM with only stable Debian and old gcc and old everything - Pepperidge Farm remembers

and build there

----- On 13 Oct, 2016, at 09:04, Wei Liu wei.liu2@citrix.com wrote:

> I don't think it breaks building Xen -- you just can't decompress xz
> format file, right? Otherwise Juergen would not have been able to build
> Xen.
> 
> Wei.

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Wei Liu]

On Thu, Oct 13, 2016 at 10:10:46AM +0100, Juergen Schinker wrote:
> Right and still no solution 
> 
> there is no xz-dev or libxz-dev;  I installed everything which just looks remote like xz or lzma
> 

On Debian it is called liblzma-dev. Not sure what distro you use.

> building is no problem as I build with
> 
> ./configure --enable-githttp --enable-systemd --disable-rombios --disable-qemu-traditional --disable-stubdom --disable-docs
> 
> 

And you sorta worked around the lzma requirement by disabling rombios.

This issue you encountered is a different issue from Boris'.

Wei.

> I'm thinking of building a special VM with only stable Debian and old gcc and old everything - Pepperidge Farm remembers
> 
> and build there
> 
> ----- On 13 Oct, 2016, at 09:04, Wei Liu wei.liu2@citrix.com wrote:
> 
> > I don't think it breaks building Xen -- you just can't decompress xz
> > format file, right? Otherwise Juergen would not have been able to build
> > Xen.
> > 
> > Wei.

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Juergen Schinker]

----- On 13 Oct, 2016, at 09:29, Wei Liu wei.liu2@citrix.com wrote:

> On Thu, Oct 13, 2016 at 10:10:46AM +0100, Juergen Schinker wrote:
>> Right and still no solution
>> 
>> there is no xz-dev or libxz-dev;  I installed everything which just looks remote
>> like xz or lzma
>> 
> 
> On Debian it is called liblzma-dev. Not sure what distro you use.
> 
>> building is no problem as I build with
>> 
>> ./configure --enable-githttp --enable-systemd --disable-rombios
>> --disable-qemu-traditional --disable-stubdom --disable-docs
>> 
>> 
> 
> And you sorta worked around the lzma requirement by disabling rombios.
> 
> This issue you encountered is a different issue from Boris'.
 
no still no solution

the xz problem is only for xen-4.7 but i gave up on that

my last test was 4.8-rc2 which also didn't work ; building and booting hypervizor is ok

xl tools                      nope

creating or starting a VM      nope

xl -v cr something              hangs forever

restarting xencommons           hangs

restarting xenconsoled          hangs

sigh

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Wei Liu]

On Thu, Oct 13, 2016 at 11:02:09AM +0100, Juergen Schinker wrote:
> 
> 
> ----- On 13 Oct, 2016, at 09:29, Wei Liu wei.liu2@citrix.com wrote:
> 
> > On Thu, Oct 13, 2016 at 10:10:46AM +0100, Juergen Schinker wrote:
> >> Right and still no solution
> >> 
> >> there is no xz-dev or libxz-dev;  I installed everything which just looks remote
> >> like xz or lzma
> >> 
> > 
> > On Debian it is called liblzma-dev. Not sure what distro you use.
> > 
> >> building is no problem as I build with
> >> 
> >> ./configure --enable-githttp --enable-systemd --disable-rombios
> >> --disable-qemu-traditional --disable-stubdom --disable-docs
> >> 
> >> 
> > 
> > And you sorta worked around the lzma requirement by disabling rombios.
> > 
> > This issue you encountered is a different issue from Boris'.
>  
> no still no solution
> 
> the xz problem is only for xen-4.7 but i gave up on that
> 
> my last test was 4.8-rc2 which also didn't work ; building and booting hypervizor is ok
> 
> xl tools                      nope
> 
> creating or starting a VM      nope
> 
> xl -v cr something              hangs forever
> 
> restarting xencommons           hangs
> 
> restarting xenconsoled          hangs
> 
> sigh

Hmm... I think no amount of hand-holding is going to help you.

In your situation I would suggest you to use various tools available on
Linux to figure out why it hang. Tools like strace, ldd, gdb etc, but
that's going to be rather technical and the finding isn't going to be
useful or interesting to you in the long run. The hang is likely due to
mismatch in various bits in the system.

I think your best bet is to have a clean installation of Xen.

Wei.

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

Re: [PATCH for-4.8] ipxe: update to newer commit

[Wei Liu]

Add back xen-devel

On Thu, Oct 13, 2016 at 05:26:12PM +0100, Juergen Schinker wrote:
> 
> 
> ----- On 13 Oct, 2016, at 14:53, Wei Liu wei.liu2@citrix.com wrote:
> 
> > Hmm... I think no amount of hand-holding is going to help you.
> > 
> > In your situation I would suggest you to use various tools available on
> > Linux to figure out why it hang. Tools like strace, ldd, gdb etc, but
> > that's going to be rather technical and the finding isn't going to be
> > useful or interesting to you in the long run. The hang is likely due to
> > mismatch in various bits in the system.
> > 
> > I think your best bet is to have a clean installation of Xen.
> > 
> > Wei.
> 
> I don't want hand holding - this is a bug report dude
> 
> I;m very technical and it is useful and interesting

Sorry if that came out offensive to you -- I didn't mean to.

If you're really interested in going down this rabbit hole, I think you
will need to do the following:

1. Make sure all the Xen related libraries are properly installed into
   the location you specified when building Xen.
2. Use ldd to check if xl / xenstored are the ones you installed.
3. Make sure they can find all the libraries (ldd should be handy).
4. Use strace to identify when and where they hang.

There is a lot information about Xen in general on wiki.xenproject.org.
If you need to get more information about the architecture / moving
parts of Xen, check out the wiki.

After identifying why they don't work, you will have a lot more
information to either submit a detailed bug report or start hunting down
these issues for fun and profit (!). :-)

There isn't enough information in the current report for me to tell what
goes wrong in your setup. The basic life cycle of running Xen (the
operations in your bug report) is constantly tested in Xen project CI
and all developers -- neither CI nor humans spotted bugs in those areas
in the past week.

Wei.

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

Re: ANNOUNCEMENT] Xen 4.8 RC2 FULL SUCCESS 13.10.16

[Juergen Schinker]

* Hardware:
 Intel(R) Xeon(R) CPU E3-1220L V2 @ 2.30GHz


* Software:

Debian testing is the Host
 

* Guest operating systems:
Guests Ubuntu 14.04 LTS Debian Stretch/Sid Ubuntu 16.04
 
* Functionality tested:
xl 
creating booting 
pygrub

* Comments:

Wei Liu is the man

----- On 13 Oct, 2016, at 16:45, Wei Liu wei.liu2@citrix.com wrote:

> Add back xen-devel

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