Samuel Thibault, le dim. 15 nov. 2020 23:19:15 +0100, a ecrit: > Damien Zammit, le lun. 16 nov. 2020 09:06:16 +1100, a ecrit: > > On 16/11/20 8:16 am, Samuel Thibault wrote: > > > wd1 at atabus7 drive 0 > > Do you have two controllers or one? This looks like IDE (?) > > I'm using > > -device ahci,id=ahci1 > -device ahci,id=ahci2 > -drive id=boot,format=raw,file=/root/boot,cache=writeback,if=none > -drive id=root,format=raw,file=/home/hurd,cache=writeback,if=none > -device ide-hd,drive=boot,bus=ahci2.0 > -device ide-hd,drive=root,bus=ahci2.1 > > (yes, it's an odd setup, that was meant to stress the ahci driver > discovery). > > > > wd1: <QEMU HARDDISK> > > > wd1: drive supports 16-sector PIO transfers, LBA48 addressing > > > wd1: 20480 MB, 41610 cyl, 16 head, 63 sec, 512 bytes/sect x 41943040 > > > sectors > > > wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) > > > wd1(ahcisata1:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 > > > (Ultra/100) (using DMA) > > That definitely looks like an AHCI controller with disk attached. > > > > > opening /dev/wd1d > > > could not open > > > ext2fs: device:/dev/wd1: No such device or addressHmm, what does > > > showtrans say on your disk node? > > > > > It seems rump didn't manage to open it, do you have an idea? > > Perhaps your controller does not support DMA? > > It's the qemu controller, I don't think there is any issue there.
I tried with -drive format=raw,file=/root/boot,cache=writeback,index=0 -drive format=raw,file=/home/hurd,cache=writeback,index=1 -machine q35 instead, but got the same issue: wd1 at atabus1 drive 0 wd1: <QEMU HARDDISK> wd1: drive supports 16-sector PIO transfers, LBA48 addressing wd1: 20480 MB, 41610 cyl, 16 head, 63 sec, 512 bytes/sect x 41943040 sectors wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA) opening /dev/wd1d could not open ext2fs: device:/dev/wd1: No such device or address Samuel
