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
