On 1/07/2020 22:48, Hans van Kranenburg wrote:
> On 7/1/20 5:09 PM, Alex Sanderson wrote:
>> On 1/07/2020 02:05, Hans van Kranenburg wrote:
>>> To do a bug report upstream, we'll need that information.
>> Sorry, completely misunderstood. Here is the output from the serial
>> terminal as Xen
Hi,
On 1/07/2020 02:05, Hans van Kranenburg wrote:
> Hi,
>
> On 6/25/20 1:44 PM, Alex Sanderson wrote:
>> Hi Hans,
>>
>> Thank you for your assistance with this. I hesitated to log this with
>> xen-dev but thought I should wait for a response here first.
>>
>>
>> On 25/06/2020 01:30, Hans van
Hi,
On 6/25/20 1:44 PM, Alex Sanderson wrote:
>
> Hi Hans,
>
> Thank you for your assistance with this. I hesitated to log this with
> xen-dev but thought I should wait for a response here first.
>
>
> On 25/06/2020 01:30, Hans van Kranenburg wrote:
>> Hi Alex,
>>
>> On 6/24/20 12:31 PM,
Hi Hans,
Thank you for your assistance with this. I hesitated to log this with
xen-dev but thought I should wait for a response here first.
On 25/06/2020 01:30, Hans van Kranenburg wrote:
> Hi Alex,
>
> On 6/24/20 12:31 PM, Alex Sanderson wrote:
>> Package: xen-hypervisor-4.11-amd64
>>
Hi Alex,
On 6/24/20 12:31 PM, Alex Sanderson wrote:
> Package: xen-hypervisor-4.11-amd64
> Version: 4.11.3+24-g14b62ab3e5-1~deb10u1
> Severity: important
>
> Dear Maintainer,
>
> After updating to Buster and Xen 4.11 our machine no longer boots the Xen
> kernel. The default kernel
5 matches
Mail list logo