Bug#812327: xen: initrd booting with xen don't find any harddisks

2019-02-22 Thread Hans van Kranenburg
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 following scenarios
does apply to your situation?

* I had this problem a long time ago. It was never solved, but I found a
workaround, which is ...
* I had this problem a long time ago, and I solved it by not using Xen
any more, but by doing ...
* I still experience this problem, and I'm still using Xen
3.2/4.1/4.4/etc. I cannot upgrade to Debian Stretch or Buster because ...
* I had this problem, and since upgrading to Stretch / Buster / ? it
seems it was solved, and I forgot to report it again. Please close it,
thanks.
* Other: ...

Note that even if you found a solution, it's still very useful to report
it back to our bug tracker. There might be someone else running into the
same problem, who can be helped with your information.

Please note that unless there's a response within a while from now, we
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.

Thanks,
Hans van Kranenburg



Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-11-15 Thread Ian Jackson
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 not detecting the VIA sata and pata controllers.  It
seems strange to me because I would have expected many people to have
such controllers.

In any case this is probably a kernel bug rather than a Xen bug.  And
the kernel 4.3 is no longer in Debian AFAICT.  Is the bug still
happening with recent kernels ?  If so then perhaps we should reassign
the bug to an appropriate linux kernel package.

Thanks,
Ian.



Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-05-12 Thread Thomas

Did you guys every find a solution for this??

Cheers,
Thomas



Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-01-22 Thread Markus Schräder

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 get the Xen dmesg one too (which you may not
from a initrd) that would be useful as well.

In the Xen case you might find http://wiki.xenproject.org/wiki/XenSerialCon
sole useful (if your hardware has a serial port, which is less common these
days). Failing that a digital photo of all the bits with (XEN) at the front
(a big block near the start of boot and possibly odd bits in the middle of
the dom0 logs later) would be better than nothing.

Ian.





Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-01-22 Thread Ian Campbell
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 /, joined each by RAID 1.
> 
> Then I just installed "xen-system-amd64", nothing more. After
> rebooting, selecting on grub to boot XEN, it hangs on
> 
>   mdadm: no devices listed in conf file were found
> 
> . I reproduced this on a different machine, and there is the same case.
> 
> In initrd you can see that it just do not have any /dev/sd* or
> /dev/hd*. So it is clear why it cannot find the arrays.
> 
> Why does the kernel not find any disks booting via XEN? If you select
> in grub the entry without xen, it just finds its discs and boots fine...

Please can you post full boot logs of the successful (without Xen) and
unsuccessful (with Xen) cases using the exact same kernel + initrd binaries
(i.e. the only difference being the presence of Xen under the kernel)

Thanks,
Ian.



Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-01-22 Thread Markus Schraeder
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 more. After
rebooting, selecting on grub to boot XEN, it hangs on

  mdadm: no devices listed in conf file were found

. I reproduced this on a different machine, and there is the same case.

In initrd you can see that it just do not have any /dev/sd* or
/dev/hd*. So it is clear why it cannot find the arrays.

Why does the kernel not find any disks booting via XEN? If you select
in grub the entry without xen, it just finds its discs and boots fine...

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xen-system-amd64 depends on:
ii  xen-hypervisor-4.6-amd64  4.6.0-1
ii  xen-utils-4.6 4.6.0-1

xen-system-amd64 recommends no packages.

xen-system-amd64 suggests no packages.

-- no debconf information



Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

2016-01-22 Thread Ian Campbell
(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 well.

In the Xen case you might find http://wiki.xenproject.org/wiki/XenSerialCon
sole useful (if your hardware has a serial port, which is less common these
days). Failing that a digital photo of all the bits with (XEN) at the front
(a big block near the start of boot and possibly odd bits in the middle of
the dom0 logs later) would be better than nothing.

Ian.