On 2/17/19 12:27 AM, Marek Marczykowski-Górecki wrote:
> On Sat, Feb 16, 2019 at 10:36:00PM +0100, Hans van Kranenburg wrote:
>> Actually, while looking at this again...
>>
>> In the init script, we already have...
>>
>> capability_check()
>> {
>> [ -e "/proc/xen/capabilities" ] || return 1
On Sat, Feb 16, 2019 at 10:36:00PM +0100, Hans van Kranenburg wrote:
> Actually, while looking at this again...
>
> In the init script, we already have...
>
> capability_check()
> {
> [ -e "/proc/xen/capabilities" ] || return 1
> grep -q "control_d" /proc/xen/capabilities || retur
On 2/16/19 1:41 PM, Hans van Kranenburg wrote:
> On 2/16/19 4:26 AM, Marek Marczykowski-Górecki wrote:
>> On Wed, Feb 13, 2019 at 02:27:18AM +0100, Hans van Kranenburg wrote:
>>> Creating new binary packages etc... is not an option anymore during the
>>> Buster freeze.
>>
>> Ok, I can carry myself
On 2/16/19 4:26 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Feb 13, 2019 at 02:27:18AM +0100, Hans van Kranenburg wrote:
>> Creating new binary packages etc... is not an option anymore during the
>> Buster freeze.
>
> Ok, I can carry myself a startup script calling actual xl directly. But
> on
On Wed, Feb 13, 2019 at 02:27:18AM +0100, Hans van Kranenburg wrote:
> Creating new binary packages etc... is not an option anymore during the
> Buster freeze.
Ok, I can carry myself a startup script calling actual xl directly. But
one thing would be very useful to have in buster - avoid starting
On 2/13/19 2:17 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Feb 13, 2019 at 02:07:22AM +0100, Hans van Kranenburg wrote:
>> xen-utils-common 4.11 does not depend on xen-utils 4.11, so it can be
>> missing.
>
> Oh... so maybe search for latest one and error out if none is there?
> Or, create ye
On Wed, Feb 13, 2019 at 02:07:22AM +0100, Hans van Kranenburg wrote:
> xen-utils-common 4.11 does not depend on xen-utils 4.11, so it can be
> missing.
Oh... so maybe search for latest one and error out if none is there?
Or, create yet another binary package which depends on both, intended to
be i
Hi,
On 2/13/19 1:53 AM, Marek Marczykowski-Górecki wrote:
> Preliminary test results of something based on debian-xen master branch:
> Xen version detection seems fundamentally wrong when talking about domU
> side. I've installed relevant packages in buster-based domU, then tried
> manually `xl de
Preliminary test results of something based on debian-xen master branch:
Xen version detection seems fundamentally wrong when talking about domU
side. I've installed relevant packages in buster-based domU, then tried
manually `xl devd`. The result:
ERROR: Can't find version 4.8 of xen utils,
Hi,
On 2/11/19 6:35 PM, Marek Marczykowski-Górecki wrote:
> On Mon, Feb 11, 2019 at 04:27:45PM +0100, Hans van Kranenburg wrote:
>> A number of the things above are currently being done.
>
> Thanks for the info.
>
>> If you want to help testing, please subscribe to the team mailing list
>> for p
On Mon, Feb 11, 2019 at 04:27:45PM +0100, Hans van Kranenburg wrote:
> A number of the things above are currently being done.
Thanks for the info.
> If you want to help testing, please subscribe to the team mailing list
> for progress updates.
I can help with testing guest side of the things (in
Hi,
On 2/11/19 2:15 PM, Marek Marczykowski-Górecki wrote:
> Source: xen
> Severity: normal
>
> Dear Maintainer,
>
> Driver domain running Debian buster does not work, because
> xendriverdomain service is missing. Upstream xen have
> /etc/init.d/xendriverdomain (and equivalent xendriverdomain.ser
12 matches
Mail list logo
