|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] PV and HVM domains left as zombies with grants [was: Re: AW: Payed Xen Admin]
ii xen-hypervisor-4.8-amd64 4.8.0~rc5-1 amd64
Xen Hypervisor on AMD64
xentop shows: Xen 4.8.0-rc
We could not fix this with stable packages, so we are trying now to catch it by
using latest software and
the help of xen-devel. Symptoms are the same in stable and unstable.
I maintain myself kernels since 2004. So I am quiet deep in this. Our advantage
is to have a custom kernel
which supports latest hardware. We have hundreds of older hardware combinations
and always also newest
boxes which need to be installable..
We use our own interface to let customers configure/install/start/restart their
servers.
The interface does that what you would do in a shell to start/stop servers
(create/destroy)
Mit freundlichen Grüßen
Thomas Toka
- Second Level Support -
IP-Projects GmbH & Co. KG
Am Vogelherd 14
D - 97295 Waldbrunn
Telefon: 09306 - 76499-0
FAX: 09306 - 76499-15
E-Mail: info@xxxxxxxxxxxxxx
Geschäftsführer: Michael Schinzel
Registergericht Würzburg: HRA 6798
Komplementär: IP-Projects Verwaltungs GmbH
-----Ursprüngliche Nachricht-----
Von: Juergen Schinker [mailto:ba1020@xxxxxxxxxxxxxxxxxxx]
Gesendet: Dienstag, 29. November 2016 21:32
An: Thomas Toka <toka@xxxxxxxxxxxxxx>; xen-devel <xen-devel@xxxxxxxxxxxxx>
Betreff: Re: [Xen-devel] PV and HVM domains left as zombies with grants [was:
Re: AW: Payed Xen Admin]
>
>
> xenversion: It happened with 4.4.1 from Debian Jessie, then we
> upgraded the Hypervisor to 4.8-rc from Debian Stretch. Symptoms are the same.
>
> So now its
>
> (d11) HVM Loader
>
> (d11) Detected Xen v4.8.0-rc
>
>
Debian Strech has now 4.8.0.rc5-1 and I think it's very stable....
>
> Kernel is our build:
> [
> http://mirror.ip-projects.de/kernel/linux-image-4.8.10-xen_4810_amd64.
> deb |
> http://mirror.ip-projects.de/kernel/linux-image-4.8.10-xen_4810_amd64.
> deb ] (config file inside .deb as you know..)
>
> And yes its Linux 4.8.10 from linux.org. We maintain our own .deb
> packeges for all latest kernel.
>
why do you do this? esp (I assume) on Production machines? I have done it
myself and consider it very risky...
you don't need the bleeding edge kernel - and what is the advantage?
Compiling the latest kernel requires a lot of experience and knowldege what the
kernel hacker are doing and
you need to follow the lkml mailinglist which is another beast mighter than the
xen-devel.
Have you considered an Orchestration tool etc ?
How do you let customer create or destroy machines?
Do you use PVM ?
How do you plan to pay for XEN-Support - have you considered Bitcoin ?
Gruesse
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |