From: Thomas Toka <toka@ip-projects.de>
To: 'Juergen Schinker' <ba1020@homie.homelinux.net>,
'xen-devel' <xen-devel@lists.xen.org>
Subject: Re: PV and HVM domains left as zombies with grants [was: Re: AW: Payed Xen Admin]
Date: Wed, 30 Nov 2016 07:07:19 +0000 [thread overview]
Message-ID: <8a43ac98e11c467cbc51e4eb71ecbf69@ip-projects.de> (raw)
In-Reply-To: <697716643.1256.1480451514963.JavaMail.zimbra@homie.homelinux.net>
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@ip-projects.de
Geschäftsführer: Michael Schinzel
Registergericht Würzburg: HRA 6798
Komplementär: IP-Projects Verwaltungs GmbH
-----Ursprüngliche Nachricht-----
Von: Juergen Schinker [mailto:ba1020@homie.homelinux.net]
Gesendet: Dienstag, 29. November 2016 21:32
An: Thomas Toka <toka@ip-projects.de>; xen-devel <xen-devel@lists.xen.org>
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@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-30 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 20:01 PV and HVM domains left as zombies with grants [was: Re: AW: Payed Xen Admin] Thomas Toka
2016-11-29 20:31 ` Juergen Schinker
2016-11-30 7:07 ` Thomas Toka [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-29 19:43 IP-Projects - Support
2016-11-29 19:43 IP-Projects - Support
2016-11-27 8:52 Payed Xen Admin Michael Schinzel
2016-11-29 12:08 ` Dario Faggioli
2016-11-29 13:34 ` IP-Projects - Support
2016-11-29 18:16 ` PV and HVM domains left as zombies with grants [was: Re: AW: Payed Xen Admin] Dario Faggioli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a43ac98e11c467cbc51e4eb71ecbf69@ip-projects.de \
--to=toka@ip-projects.de \
--cc=ba1020@homie.homelinux.net \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).