"cde" not OK when controler is VirtIO-scsi instead of SATA-AHCI in VirtualBox

[nick65go]

Using VirtualBox 6.1.4 on Win10, and TinyCore-11.1.iso. When the Disk COntroler is SATA-AHCI, then Tinycore runs OK, Xvesa runs OK. But when the CDROM is attached to disk controler VIrtIO-scsi to boot from CDROM, then Xvesa will not run.Because the normal /dev/sr0

Code: [Select]

cat cde
/mnt/sr0/cde/optionalbecome now /dev/whatever-cdrom-driver is not mounted. Where is better to change/improve tinycore, in tce-setup? or in udev rules? or in /etc/fstab? maybe you have a patch for the next version of TC.
FYI: the TinyCorePure64-11.1.iso (64 bits) boots OK with virtIO-scsi as cdrom controler.

[curaga]

Well, I don't think any of us run Virtualbox. Qemu is preferred usually. So tracking this would be up to Virtualbox users like you. First, what is the device name? Can you mount it manually? Is it listed in fstab? etc.

[nick65go]

well, this is my problem: i do not know what device to asign to the cdrom driver. after this is just simply to myself tune-up or remaster my TC11_x32. With TC11_x64 the cdrom is still /dev/sr0 and is working. But in TC11_32 i do not know. I tried with most /dev/v* and /dev/sd* and /dev/hd* etc, but unsuccesfuly.

In the end is NOT a big deal, because it was just a matter of "preferences" in VirtualBox, so I can choose SATA controler for CDROM drive to boot from it with no HDD attached.

The problem derived because I just wanted to remaster (for myself) TC11_32, to be the minimum posible size, optimized to the only controlers and devices needed strict specificaly to virtual machine (of course recompiling the kernel, so not very well contribution back to comunity).
FYI: I like very much TC (same as Apline Linux), but dual booting with Windows 10 is a pain, because UEFI64 of my laptop is so slow (default to MS Win bootloader). And I could use just Linux for most of my tasks at home, but F2/F3 as backlight not working in my laptop, AMDGPU still rise my fan speed, Firefox_75 not proper video accelatation (maybe in wayland), etc.So, yap, Win10 for the near future, studing  linux from Vitual machines.

[curaga]

dmesg may have some info, but custom kernels depend on your config.

[nick65go]

Thank you curaga for your interest! I have found the bug, it is about the ORDER the devices are assigned in VirtualBox, not as TC expectations.So, using TC11_64 (virgin kernel), one CDROM (IDE attached -> /dev/sr0) and with 3 HDD (SATA attached-> /dev/[sda..sdc]), booting from sda1 is OK.

Code: [Select]

code]# /etc/fstab
proc            /proc        proc    defaults          0       0
sysfs           /sys         sysfs   defaults          0       0
devpts          /dev/pts     devpts  defaults          0       0
tmpfs           /dev/shm     tmpfs   defaults          0       0
/dev/zram0  swap         swap    defaults,noauto   0       0
/dev/sda1       /mnt/sda1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sdb1       /mnt/sdb1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sdc1       /mnt/sdc1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sr0        /mnt/sr0        auto     noauto,users,exec    0 0 # Added by TC
--
blkid /dev/sd* /dev/sr*
/dev/sda1: LABEL="KERNELS" UUID="40628810-57ff-42f4-904c-11094f2e786f" TYPE="ext2"
/dev/sdb1: LABEL="TC10-32" UUID="67a87341-e46e-48d5-ab8c-cdd9363862f9" TYPE="ext2"
/dev/sdc1: LABEL="TC10-64" UUID="a0c5b409-fd3e-4bc3-855f-7fbd941b971d" TYPE="ext2"
/dev/scd0: UUID="2020-02-18-17-20-05-35" LABEL="VBox_GAs_6.1.4" TYPE="iso9660"
Now Adding a new controller, type virtIO-scsi, and one CDROM (XP-WIM.iso) and one HDD (ext2, Apline root), after reboot I have:

Code: [Select]

# /etc/fstab
proc            /proc        proc    defaults          0       0
sysfs           /sys         sysfs   defaults          0       0
devpts          /dev/pts     devpts  defaults          0       0
tmpfs           /dev/shm     tmpfs   defaults          0       0
/dev/zram0  swap         swap    defaults,noauto   0       0
/dev/sda3       /mnt/sda3       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sda1       /mnt/sda1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sdb1       /mnt/sdb1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sdc1       /mnt/sdc1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sdd1       /mnt/sdd1       ext2     noauto,users,exec,relatime 0 0 # Added by TC
/dev/sr0        /mnt/sr0        auto     noauto,users,exec    0 0 # Added by TC
/dev/sr1        /mnt/sr1        auto     noauto,users,exec    0 0 # Added by TCso all devices are known, but in wrong order, because blkid shows now:

Code: [Select]

/dev/sda3: UUID="aa6a66b3-a77d-4c60-9cf9-d6fbfa0b9453" TYPE="ext2" PARTUUID="60dca8ba-03"
/dev/sda1: UUID="bfd26ab8-80bc-4db9-adb5-3550026fd356" TYPE="ext2" PARTUUID="60dca8ba-01"
/dev/sdb1: LABEL="KERNELS" UUID="40628810-57ff-42f4-904c-11094f2e786f" TYPE="ext2"
/dev/sdc1: LABEL="TC10-32" UUID="67a87341-e46e-48d5-ab8c-cdd9363862f9" TYPE="ext2"
/dev/sdd1: LABEL="TC10-64" UUID="a0c5b409-fd3e-4bc3-855f-7fbd941b971d" TYPE="ext2"
/dev/sr0: UUID="2018-07-22-22-51-11-00" LABEL="XPWIM" TYPE="iso9660"
/dev/sr1: UUID="2020-02-18-17-20-05-35" LABEL="VBox_GAs_6.1.4" TYPE="iso9660"plus wrongly only one (/dev/sdc1) is auto-mounted:

Code: [Select]

rootfs on / type rootfs (rw,size=2779016k,nr_inodes=1017976)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /dev/shm type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdc1 on /mnt/sdc1 type ext2 (rw,relatime)even more wrongly, the former /dev/sdb1 and /dev/sdc1 are now union mounted under /dev/sdc1;

Code: [Select]

ls -al /mnt/sdc1
total 3
drwxrwxr-x    4 tc       staff         1024 Apr 14 15:23 ./
drwxrwxr-x    9 root     staff          180 Apr 14 15:55 ../
drwxrwxr-x    4 tc       staff         1024 Jun 15  2019 tce10-32/
drwxrwxr-x    4 tc       staff         1024 Apr 14 15:23 tce11-64/Summary: a VirtualBox control type VirtIO-scsi will
- mount first CDROM (win XP) attached under it as /dev/sr0. so the first IDE CDROM (Vbox.iso) is now /dev/sr1- mount first HDD attached under it as /dev/sda (sda1-sda3, because 3 partitions on Alpine), so the former /dev/[sda..sdc] will become /dev/[sdb..sdd]And the normal default TC scripts will not work, without a remaster.

[nick65go]

I think this subject can be closed. The time of the Tinycore developers could be better use to puposes which more benefit the linux comunity.
FYI: searching your TC history/archives website, I found the optimal point for a virtual machine, without any kernel recompile etc.the virtio-net driver is present starting in latest kernel 2.x (Tinycore 3.8.4, 10.2 MB, kernel 2.6.33.3). it has also ntfs-ro driver.
but the next kernel 3.x (Tinycore 4.7.7, 12.3 MB, kernel 3.0.21) has "cde" boot option. and has near the same vmlinuz of 2.3MB. then the 5.4 MB core.gz then could be drasticaly reduced/remastered if in need.
So, for learning/testing linux, the virtio-net, scsi-cdrom, sata-hdd, sound ac97 -->TC_4.7.7 it is just best for speed and size. and it "works" in 32 MB RAM