Re: Missing virtio modules for sparc64

[James Clarke]

On 17 Mar 2017, at 11:42, Mark Cave-Ayland  
wrote:
> On 17/03/17 11:40, James Clarke wrote:
>> On 17 Mar 2017, at 11:36, Mark Cave-Ayland  
>> wrote:
>>> On 17/03/17 11:33, John Paul Adrian Glaubitz wrote:
>>> 
 On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
> There is one issue I've found in that the debian-installer fails to
> detect the installation CDROM hardware automatically.
> 
> I was able to workaround this by selecting the option to load an
> external driver, let that fail, then manually enter the /dev/vda device
> which allowed installation to continue but something is preventing the
> virtio-blk device being seen as a CDROM.
 
 It's most likely the same issue as the one we have with the vdisk block
 devices when installing inside a SPARC LDOM [1].
 
 Can you post the output of "udevadm info -q env -p /sys/block/vda" if
 /dev/vda is the virtual block device for your CD-ROM drive? If it
 doesn't include any indication of a CD device, you know why d-i doesn't
 detect the CD drive.
>>> 
>>> Yep, here she is:
>>> 
>>> ~ # udevadm info -q env -p /sys/block/vda
>>> DEVLINKS=/dev/disk/by-path/platform-ffe2d650-pci-:00:06.0
>>> /dev/disk/by-label/Debian\x209.0\x20sparc64\x201
>>> /dev/disk/by-uuid/2017-03-16-23-13-57-00
>>> DEVNAME=/dev/vda
>>> DEVPATH=/devices/root/ffe2d650/pci:00/:00:06.0/virtio0/block/vda
>>> DEVTYPE=disk
>>> ID_FS_LABEL=Debian_9.0_sparc64_1
>>> ID_FS_LABEL_ENC=Debian\x209.0\x20sparc64\x201
>>> ID_FS_TYPE=iso9660
>>> ID_FS_USAGE=filesystem
>>> ID_FS_UUID=2017-03-16-23-13-57-00
>>> ID_FS_UUID_ENC=2017-03-16-23-13-57-00
>>> ID_PART_TABLE_TYPE=sun
>>> ID_PATH=platform-ffe2d650-pci-:00:06.0
>>> ID_PATH_TAG=platform-ffe2d650-pci-_00_06_0
>>> MAJOR=254
>>> MINOR=0
>>> SUBSYSTEM=block
>>> USEC_INITIALIZED=4920671
>>> ~ #
>>> 
>>> Presumably the DEVTYPE=disk gives away that the device isn't correctly
>>> being detected as a CDROM?
>> 
>> Nah, it would still be a disk, but you would have:
>> 
>>> ID_CDROM=1
>> 
>> 
>> What does `/lib/udev/cdrom_id /dev/vda` say?
> 
> Hmmm seemingly nothing:
> 
> ~ # /lib/udev/cdrom_id /dev/vda
> ~ #

Aha, known issue with virtio[1]. This would be fixed by scanning for
ID_FS_TYPE=iso9660 as well as ID_CDROM=1...

Regards,
James

[1] https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1155403

Re: Missing virtio modules for sparc64

[Mark Cave-Ayland]

On 17/03/17 11:40, James Clarke wrote:
> On 17 Mar 2017, at 11:36, Mark Cave-Ayland  
> wrote:
>> On 17/03/17 11:33, John Paul Adrian Glaubitz wrote:
>>
>>> On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
 There is one issue I've found in that the debian-installer fails to
 detect the installation CDROM hardware automatically.

 I was able to workaround this by selecting the option to load an
 external driver, let that fail, then manually enter the /dev/vda device
 which allowed installation to continue but something is preventing the
 virtio-blk device being seen as a CDROM.
>>>
>>> It's most likely the same issue as the one we have with the vdisk block
>>> devices when installing inside a SPARC LDOM [1].
>>>
>>> Can you post the output of "udevadm info -q env -p /sys/block/vda" if
>>> /dev/vda is the virtual block device for your CD-ROM drive? If it
>>> doesn't include any indication of a CD device, you know why d-i doesn't
>>> detect the CD drive.
>>
>> Yep, here she is:
>>
>> ~ # udevadm info -q env -p /sys/block/vda
>> DEVLINKS=/dev/disk/by-path/platform-ffe2d650-pci-:00:06.0
>> /dev/disk/by-label/Debian\x209.0\x20sparc64\x201
>> /dev/disk/by-uuid/2017-03-16-23-13-57-00
>> DEVNAME=/dev/vda
>> DEVPATH=/devices/root/ffe2d650/pci:00/:00:06.0/virtio0/block/vda
>> DEVTYPE=disk
>> ID_FS_LABEL=Debian_9.0_sparc64_1
>> ID_FS_LABEL_ENC=Debian\x209.0\x20sparc64\x201
>> ID_FS_TYPE=iso9660
>> ID_FS_USAGE=filesystem
>> ID_FS_UUID=2017-03-16-23-13-57-00
>> ID_FS_UUID_ENC=2017-03-16-23-13-57-00
>> ID_PART_TABLE_TYPE=sun
>> ID_PATH=platform-ffe2d650-pci-:00:06.0
>> ID_PATH_TAG=platform-ffe2d650-pci-_00_06_0
>> MAJOR=254
>> MINOR=0
>> SUBSYSTEM=block
>> USEC_INITIALIZED=4920671
>> ~ #
>>
>> Presumably the DEVTYPE=disk gives away that the device isn't correctly
>> being detected as a CDROM?
> 
> Nah, it would still be a disk, but you would have:
> 
>> ID_CDROM=1
> 
> 
> What does `/lib/udev/cdrom_id /dev/vda` say?

Hmmm seemingly nothing:

~ # /lib/udev/cdrom_id /dev/vda
~ #


ATB,

Mark.

Re: Missing virtio modules for sparc64

[James Clarke]

On 17 Mar 2017, at 11:36, Mark Cave-Ayland  
wrote:
> On 17/03/17 11:33, John Paul Adrian Glaubitz wrote:
> 
>> On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
>>> There is one issue I've found in that the debian-installer fails to
>>> detect the installation CDROM hardware automatically.
>>> 
>>> I was able to workaround this by selecting the option to load an
>>> external driver, let that fail, then manually enter the /dev/vda device
>>> which allowed installation to continue but something is preventing the
>>> virtio-blk device being seen as a CDROM.
>> 
>> It's most likely the same issue as the one we have with the vdisk block
>> devices when installing inside a SPARC LDOM [1].
>> 
>> Can you post the output of "udevadm info -q env -p /sys/block/vda" if
>> /dev/vda is the virtual block device for your CD-ROM drive? If it
>> doesn't include any indication of a CD device, you know why d-i doesn't
>> detect the CD drive.
> 
> Yep, here she is:
> 
> ~ # udevadm info -q env -p /sys/block/vda
> DEVLINKS=/dev/disk/by-path/platform-ffe2d650-pci-:00:06.0
> /dev/disk/by-label/Debian\x209.0\x20sparc64\x201
> /dev/disk/by-uuid/2017-03-16-23-13-57-00
> DEVNAME=/dev/vda
> DEVPATH=/devices/root/ffe2d650/pci:00/:00:06.0/virtio0/block/vda
> DEVTYPE=disk
> ID_FS_LABEL=Debian_9.0_sparc64_1
> ID_FS_LABEL_ENC=Debian\x209.0\x20sparc64\x201
> ID_FS_TYPE=iso9660
> ID_FS_USAGE=filesystem
> ID_FS_UUID=2017-03-16-23-13-57-00
> ID_FS_UUID_ENC=2017-03-16-23-13-57-00
> ID_PART_TABLE_TYPE=sun
> ID_PATH=platform-ffe2d650-pci-:00:06.0
> ID_PATH_TAG=platform-ffe2d650-pci-_00_06_0
> MAJOR=254
> MINOR=0
> SUBSYSTEM=block
> USEC_INITIALIZED=4920671
> ~ #
> 
> Presumably the DEVTYPE=disk gives away that the device isn't correctly
> being detected as a CDROM?

Nah, it would still be a disk, but you would have:

> ID_CDROM=1


What does `/lib/udev/cdrom_id /dev/vda` say?

James

Re: Missing virtio modules for sparc64

[Mark Cave-Ayland]

On 17/03/17 11:33, John Paul Adrian Glaubitz wrote:

> On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
>> There is one issue I've found in that the debian-installer fails to
>> detect the installation CDROM hardware automatically.
>>
>> I was able to workaround this by selecting the option to load an
>> external driver, let that fail, then manually enter the /dev/vda device
>> which allowed installation to continue but something is preventing the
>> virtio-blk device being seen as a CDROM.
> 
> It's most likely the same issue as the one we have with the vdisk block
> devices when installing inside a SPARC LDOM [1].
> 
> Can you post the output of "udevadm info -q env -p /sys/block/vda" if
> /dev/vda is the virtual block device for your CD-ROM drive? If it
> doesn't include any indication of a CD device, you know why d-i doesn't
> detect the CD drive.

Yep, here she is:

~ # udevadm info -q env -p /sys/block/vda
DEVLINKS=/dev/disk/by-path/platform-ffe2d650-pci-:00:06.0
/dev/disk/by-label/Debian\x209.0\x20sparc64\x201
/dev/disk/by-uuid/2017-03-16-23-13-57-00
DEVNAME=/dev/vda
DEVPATH=/devices/root/ffe2d650/pci:00/:00:06.0/virtio0/block/vda
DEVTYPE=disk
ID_FS_LABEL=Debian_9.0_sparc64_1
ID_FS_LABEL_ENC=Debian\x209.0\x20sparc64\x201
ID_FS_TYPE=iso9660
ID_FS_USAGE=filesystem
ID_FS_UUID=2017-03-16-23-13-57-00
ID_FS_UUID_ENC=2017-03-16-23-13-57-00
ID_PART_TABLE_TYPE=sun
ID_PATH=platform-ffe2d650-pci-:00:06.0
ID_PATH_TAG=platform-ffe2d650-pci-_00_06_0
MAJOR=254
MINOR=0
SUBSYSTEM=block
USEC_INITIALIZED=4920671
~ #

Presumably the DEVTYPE=disk gives away that the device isn't correctly
being detected as a CDROM?


ATB,

Mark.

Re: Missing virtio modules for sparc64

[John Paul Adrian Glaubitz]

On 03/17/2017 12:22 PM, Mark Cave-Ayland wrote:
> There is one issue I've found in that the debian-installer fails to
> detect the installation CDROM hardware automatically.
> 
> I was able to workaround this by selecting the option to load an
> external driver, let that fail, then manually enter the /dev/vda device
> which allowed installation to continue but something is preventing the
> virtio-blk device being seen as a CDROM.

It's most likely the same issue as the one we have with the vdisk block
devices when installing inside a SPARC LDOM [1].

Can you post the output of "udevadm info -q env -p /sys/block/vda" if
/dev/vda is the virtual block device for your CD-ROM drive? If it
doesn't include any indication of a CD device, you know why d-i doesn't
detect the CD drive.

Adrian

> [1] https://lists.debian.org/debian-sparc/2017/03/msg00050.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Missing virtio modules for sparc64

[Mark Cave-Ayland]

On 16/03/17 23:46, John Paul Adrian Glaubitz wrote:

> On 03/16/2017 11:24 PM, John Paul Adrian Glaubitz wrote:
>> I'm rebuilding the sparc64 installer image now and will hopefully post
>> it shortly.
> 
> Here they are: https://people.debian.org/~glaubitz/debian-cd/2017-03-17/
> 
> Adrian

Great! I can confirm the patch works as expected in that the virtio
kernel modules are now loaded upon boot - thank you very much!

There is one issue I've found in that the debian-installer fails to
detect the installation CDROM hardware automatically.

I was able to workaround this by selecting the option to load an
external driver, let that fail, then manually enter the /dev/vda device
which allowed installation to continue but something is preventing the
virtio-blk device being seen as a CDROM.

The QEMU virtio-blk device is configured like this:

-drive
file=debian-9.0-sparc64-NETINST-1.iso,if=none,index=0,id=cd,media=cdrom

-device virtio-blk-pci,drive=cd

So I am definitely telling QEMU that the virtio-blk device is CDROM
rather than HD media, but that knowledge somehow isn't getting to the
installer?


ATB,

Mark.

Re: Missing virtio modules for sparc64

[John Paul Adrian Glaubitz]

On 03/16/2017 11:24 PM, John Paul Adrian Glaubitz wrote:
> I'm rebuilding the sparc64 installer image now and will hopefully post
> it shortly.

Here they are: https://people.debian.org/~glaubitz/debian-cd/2017-03-17/

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Missing virtio modules for sparc64

[John Paul Adrian Glaubitz]

Hi Mark, Hi Helge!

On 03/16/2017 10:57 PM, Helge Deller wrote:
>> Please can you consider the attached patch for inclusion in the
>> debian-installer so that it becomes possible to perform a complete
>> sparc64 installation from virtio devices under QEMU?
>>(...)
> I just committed it, together with the patch for powerpc (bug #767487).

I'm rebuilding the sparc64 installer image now and will hopefully post
it shortly.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913