Slackware 14RC2 install on qemu
Hi all,
I was just wondering if there are plans to add to the installer support for virtio hdd ( /dev/vda ) since 13.37 did not , I tried to install the 14 but unfortunately seems thing have improved a little but not by much. 1) the installer has virtio support but lilo fails to install 2) I edited the lilo.conf adding Code:
disk = /dev/vda boot=0x80 max-partitions=7 3) the stock kernel though fails to see my disk and dies orrible death with : Code:
VFS:Cannot open root device "fc02" or unknown-block(252,2) |
You probably did something wrong. The installer has virtio support, but you still have to create an initrd because all virtio support of the kernel has been implemented as modules.
In the installer, you could run "chroot /mnt" after completing the installation process. Then in the chroot, run Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Don't forget to update /etc/lilo.conf and re-run lilo. Eric |
Just great, using your posts I successfully fixed my boot issues ("disk = ..." in lilo.conf and added virtio modules to initrd.gz).
I have another issue(???). I cannot boot HUGESMP.S kernel from the install ISOs (mini and current) and the huge-smp / gen-smp kernels from the installed Slackware 14 RC3. Each time the boot process stops in the very beginning: Code:
Loading Slackware-hsmp ....................... I tested with: http://taper.alienbase.nl/mirrors/sl...nstall-dvd.iso http://ponce.cc/slackware/iso/slackw...nstall-dvd.iso http://ponce.cc/slackware/iso/slackw...ni-install.iso (Why ponce's and alien's ISOs have different md5 sum and size?) Note: I tested with 13.37 ISOs, no problems at all, smp/nosmp kernels work fine: ftp://slackware.mirrors.tds.net/pub/...install-d1.iso http://slackware.com/~alien/slackboo...ni-install.iso My QEMU script: Code:
#!/bin/sh I use Alien's SlackBuild built on my host 14 RC3 32-bit. |
What are the parameters you pass to that script?
In order to boot off the ISO, BOOT_DEV="c" would be wrong. Also, the Slackware installer will not understand the virtio block device- unless you manually load the virtio drivers you need (the modules are available in the installer). Eric |
The parameters are:
d installer_iso_filename I don't load any virtio driver at boot. But I had to mention explicitly that HUGE.s boots with no problem, that is how I managed to install the guest Slackware 14 RC3. Also, on the installed guest OS I can boot only the non SMP kernels. The SMP ones stop at the same line (Booting the kernel.) So, I installed using HUGE.s. Firstly, after reboot (started the QEMU script with no params) I finished with a kernel panic because of the missing virtio modules. I fixed it with: 1. Boot again HUGE.s 2. mount /dev/vda1 /mnt 3. chroot /mnt 4. Added virtio and ext4 modules to initrd.gz 5. Modified lilo.conf 6. exit (to leave chroot /mnt) 7. lilo -b /dev/vda -C /mnt/etc/lilo.conf And I successfully boot with non SMP kernels (generic and huge). I have network (after loading of other 8139 driver), start KDE. But huge-smp and generic-smp stop at the mentioned line. |
And what if you replace "-smp cores=2,threads=1,sockets=1" with "-smp 2" ?
Eric |
Quote:
|
Quote:
Here is the cpuinfo from the guest OS: Code:
processor : 0 Next week I'm going to install 64-bit 14 RC3 (or 14 stable if ready:hattip:) I will try with QEMU-KVM64 and 32/64-bit guest Slackware. |
Quote:
I never messed with initrd since I normally rebuild my kernel to match only the needed stuff ( and I build driver and filesystem static ) , though I want to try it , only one question since I like to slack ;-) this is what I Did : I rebooted with the Slackware64 Install CD Code:
mount /dev/vda2 /mnt Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Code:
find: '/sys/block' : No Such file or directory Though the command seems to have a syntax error in "(IN" so I deleted the "(" and ran it : Code:
cat: /proc/partitions: No such file or directory Code:
fatal: do_disk: stat /dev/vda: No such file or directory |
before doing the chroot you gotta make some stuff from the boot system available also to the chroot environment.
execute these commands (before the chroot) Code:
mount -t proc proc /mnt/proc Code:
umount /mnt/sys |
Quote:
Anyway thank you all for the help |
Quote:
I changed -cpu parameter in the QEMU script using: Code:
-cpu host,-nx |
All times are GMT -5. The time now is 07:25 AM. |