Hi Markus,
This is about the bug report (#812327) that you filed
before in the Debian bug tracker, against the Xen packages.
Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable (Stretch).
Can you please help us by confirming that any of the
Control: severity -1 normal
Control: tags -1 + moreinfo
Hi. I seem to be in the process of taking over the Xen packages in
Debian. I'm looking at some of these bugs to see if some of them can
be fixed or whatever.
Thanks for the boot logs. I think the problem is that the Linux
kernel there is
Did you guys every find a solution for this??
Cheers,
Thomas
Hi Ian,
does
https://www.priv.de/debianbugs/
help?
Regards,
Markus Schraeder
(adding the bug back, please keep it ccd)
On Fri, 2016-01-22 at 13:05 +0100, Markus Schräder wrote:
What is for you a full log? A dmesg?
At least the linux dmesg in both cases, yes.
In the Xen case if you can
On Fri, 2016-01-22 at 12:40 +0100, Markus Schraeder wrote:
> Package: xen-system-amd64
> Version: 4.6.0-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I installed fresh from ALPHA5, no UEFI, with two disks. Each disk
> got a partition for /boot and one for
Package: xen-system-amd64
Version: 4.6.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed fresh from ALPHA5, no UEFI, with two disks. Each disk
got a partition for /boot and one for /, joined each by RAID 1.
Then I just installed "xen-system-amd64", nothing
(adding the bug back, please keep it ccd)
On Fri, 2016-01-22 at 13:05 +0100, Markus Schräder wrote:
> What is for you a full log? A dmesg?
At least the linux dmesg in both cases, yes.
In the Xen case if you can get the Xen dmesg one too (which you may not
from a initrd) that would be useful as
7 matches
Mail list logo
