Bug#858049: Please add ufs-modules udeb on sparc64
Source: linux Version: 4.9.13-1 Tags: patch User: debian-sparc@lists.debian.org Usertags: sparc64 X-Debbugs-Cc: debian-sparc@lists.debian.org Hi, Along with (more recently) ZFS, many Solaris installations use UFS for their root file system. Therefore, it would be extremely useful if an installer CD could mount these partitions, but at the moment there is no ufs-modules udeb available for d-i to include. Please apply the attached patch to create one on sparc64 so we can add it to d-i. Thanks, James >From 77a8ef24e9059ae1d1c9617861b78d711ecdbd94 Mon Sep 17 00:00:00 2001 From: James ClarkeDate: Fri, 17 Mar 2017 17:35:40 + Subject: [PATCH] [sparc64] Add new ufs-modules udeb --- debian/installer/modules/ufs-modules | 1 + debian/installer/package-list| 6 ++ debian/installer/sparc64/modules/sparc64/ufs-modules | 1 + 3 files changed, 8 insertions(+) diff --git a/debian/installer/modules/ufs-modules b/debian/installer/modules/ufs-modules new file mode 100644 index 0..19173e9aa --- /dev/null +++ b/debian/installer/modules/ufs-modules @@ -0,0 +1 @@ +ufs diff --git a/debian/installer/package-list b/debian/installer/package-list index a170318ac..6207e3946 100644 --- a/debian/installer/package-list +++ b/debian/installer/package-list @@ -129,6 +129,12 @@ Priority: extra Description: NTFS filesystem support This package contains the NTFS file system module for the kernel. +Package: ufs-modules +Depends: kernel-image +Priority: extra +Description: UFS filesystem support + This package contains the UFS filesystem module for the kernel. + Package: xfs-modules Depends: kernel-image, crc-modules Priority: standard diff --git a/debian/installer/sparc64/modules/sparc64/ufs-modules b/debian/installer/sparc64/modules/sparc64/ufs-modules new file mode 100644 index 0..163ead095 --- /dev/null +++ b/debian/installer/sparc64/modules/sparc64/ufs-modules @@ -0,0 +1 @@ +#include -- 2.11.0
Re: Missing virtio modules for sparc64
On 17 Mar 2017, at 11:42, Mark Cave-Aylandwrote: > 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
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
On 17 Mar 2017, at 11:36, Mark Cave-Aylandwrote: > 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
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
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: report on debian-9.0-sparc64-NETINST-1.iso with qemu [SOLVED]
On 27/01/17 18:52, Bruno Haible wrote: >> But there is a point in Marks reply: maybe nowadays virtio-net also >> has to be switched into the legacy mode. >> Instead of "-net nic,model=virtio -net user" can you please try: >> >> -netdev user,id=hostnet0 -device >> virtio-net-pci,disable-modern=off,disable-legacy=off,disable-modern=on,netdev=hostnet0 > > Yeah! This works! The machine now can connect to the internet. > The ifconfig output now is: > > # /target/sbin/ifconfig > enp0s5: flags=4163mtu 1500 > inet 10.0.2.15 netmask 255.255.255.0 broadcast 0.0.0.0 > inet6 fec0::5054:ff:fe12:3456 prefixlen 64 scopeid 0x40 > inet6 fe80::5054:ff:fe12:3456 prefixlen 64 scopeid 0x20 > ether 52:54:00:12:34:56 txqueuelen 1000 (Ethernet) > RX packets 291 bytes 263098 (256.9 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 174 bytes 15608 (15.2 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1 (Local Loopback) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > # lsmod | grep virt > virtio_net 24168 0 > virtio_pci 14583 0 > virtio_ring12099 2 virtio_net,virtio_pci > virtio 6188 2 virtio_net,virtio_pci > > (qemu) info network > virtio-net-pci.0: > index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:56 > \ hostnet0: index=0,type=user,net=10.0.2.0,restrict=off > > Thanks a lot! BTW just a heads-up: I've found and fixed the bug in OpenBIOS which was causing virtio in its default modern mode to freeze (it was the 64-bit virtio BAR being programmed incorrectly), and the fix has been merged into QEMU git master as of yesterday. So in the upcoming 2.9 release you will no longer need to specify "disable-modern=on" as part of the qemu-system-sparc64 command line and "-net nic,model=virtio -net user" will work once again. ATB, Mark.
Re: Missing virtio modules for sparc64
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.
Bug#858014: udev: Please add SPARC vdisk devices to 60-cdrom_id.rules
Source: systemd Version: 232-20 Severity: normal Tags: patch User: debian-sparc@lists.debian.org Usertags: sparc64 Hi! When installing Debian inside a SPARC LDOM virtual machine, d-i is unable to detect any virtual CD-ROM drives when scanning for the installation media. debian-installer uses 'udevadm info' to check which of the available block devices are actually CD drives for which the 60-cdrom_id.rules rules file applies. See the discussion in [1]. Since 60-cdrom_id.rules has a whitelist for the block devices it checks, we need to add "vdisk*" to the whitelist so that udev will also scan the vdisk block devices found inside a SPARC LDOM virtual machine. Thus, could you please add "vdisk*" to the whitelist in the 60-cdrom_id.rules file so that debian-installer detects the virtual CD-ROM drives inside a SPARC LDOM? The attached patch is enough. Thanks, Adrian > [1] https://lists.debian.org/debian-sparc/2017/03/msg00050.html > [2] https://github.com/systemd/systemd/pull/5599 -- .''`. 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 diff -Nru old/systemd-233/rules/60-cdrom_id.rules new/systemd-233/rules/60-cdrom_id.rules --- old/systemd-233/rules/60-cdrom_id.rules 2017-03-01 22:43:06.0 +0100 +++ new/systemd-233/rules/60-cdrom_id.rules 2017-03-17 11:36:29.952543056 +0100 @@ -2,7 +2,7 @@ ACTION=="remove", GOTO="cdrom_end" SUBSYSTEM!="block", GOTO="cdrom_end" -KERNEL!="sr[0-9]*|xvd*", GOTO="cdrom_end" +KERNEL!="sr[0-9]*|vdisk*|xvd*", GOTO="cdrom_end" ENV{DEVTYPE}!="disk", GOTO="cdrom_end" # unconditionally tag device as CDROM