SliTaz Forum

1. 

   purpleleaf
   

   offline

   Member

   I tried to load the virtio-* modules after installing linux64-kvm, but the vda disk that is installed on the vm is detected.

   Posted 1 month ago #
2. 

   shann
   

   offline

   Administrator

   Hi purpleleaf,

   Sorry for mistake, think found reason, can you paste result of this command please ?

   find /lib/modules/5.10.238-slitaz64/kernel -name "*virtio*"

   If not found suspect you use iso of april instead november with grub2 suffix
   https://people.slitaz.org/~shann/slitaz-current64-stuff/isos/

   I rework tazpkg package compress function since, in this case you need upgrade tazpkg first, and reinstall packages, sorry for issue.

   Need to rebuild iso without grub2 installed or remove old isos (for 64 bits could be prefered to use grub2 as default bootloader).

   Suggest to use slitaz-current64-base64-grub2.iso, tazpkg is uptodate with slitaz-boot-scripts include fix to boot smooth in kvm vm.

   You need also initrd to be boot and detect vda disk, i build it and could be found here.
   https://people.slitaz.org/~shann/initrd-kvmraid.gz, should be rename to /boot/initrd-5.10.238-slitaz64.gz.

   After edit /etc/default/grub and uncomment GRUB_CMDLINE_LINUX_DEFAULT="" and change to it GRUB_CMDLINE_LINUX_DEFAULT="kvmroot=/dev/vdXY" (XY for disk and partition, exemple vda1).
   Don't forget to update grub.cfg grub-mkconfig -o /boot/grub/grub.cfg

   He found automatically initrd and add line for him.

   Posted 1 month ago #
3. 

   purpleleaf
   

   offline

   Member

   Hi Shann,

   i downloaded the last slitaz-rolling-core-5in1.iso from https://mirror.slitaz.org/iso/rolling/

   in /lib/modules there are only the 3.16.55-slitaz and 3.16.55-slitaz64 dirs.

   I will try your suggestion,

   many thanks

   Posted 1 month ago #
4. 

   purpleleaf
   

   offline

   Member

   Ok, finally i got a working system but it was a little bit tricky; i will try to report all step i followed (i had some problems updating the packages with tazpkg under chroot environment):

   changed the NIC to e1000 on guest configuration

   boot from slitaz-current64-core64-grub2.iso
   updated tazpkg
   updated all remaining packages
   installed linux64-kvm
   executed modprobe virtio-pci - the system now recognize the vda disk
   created a vda1 and vda2 partition for / and swap
   downloaded in live system slitaz-current64-core64-grub2.iso (the only way i found to proceed with installation)
   after installation i mounted /dev/vda1 under /mnt
   mounted /dev /proc /sys on /mnt
   chroot /mnt

   the i followed the step suggested by @shann (download of initrd, editing of /etc/default/grub, grub-mkconfig and also a grub-install /dev/vda (it should already be done during the installation...)

   reboot the system then update again tazpkg and the remaining packages, install linux64-kvm, shutdown the guest and switch NIC to virtio, boot again.

   done.

   Now i miss the vda-agent and the qxl video driver.
   There are any way to install them from some package or the only way is compiling?

   Last question, the system is using the vda2 swap partition as /run. I must continue to use this settings or can i reconfigure the system to use a normal swap partition?

   many thanks.

   Posted 1 month ago #
5. 

   shann
   

   offline

   Administrator

   Hi purpleleaf,

   slitaz rolling use 3.16.55 kernel, i thinking you use current64 (should be call 6.0 x64 ;))

   Infact at first, you need to define e1000 nic to have internet access for install linux64-kvm.
   After install linux64-kvm, nic can be switched to virtio.

   For moment, i don't build vda-agent and qxl video, let's me check this week-end.

   /run for swap it's strange, can you do free -m and df -h command please ? thanks

   Posted 1 month ago #
6. 

   purpleleaf
   

   offline

   Member

   Hi shann,
   sorry for the late, the VM i'm using right now is on the pc i have at work :)

   current64 is available only from your personal space? and if not what is the correct iso to download from slitaz mirrors?

   many thanks for you work, I will wait for vda-agent and qxl-video as long as it takes ;)

   about / run, my fault, swap on /dev/vda2 is correctly mounted, but to me is strange that run is mounted with 3.9 GB, following free -m and df -h output:

   free -m
   total used free shared buff/cache available
   Mem: 7970 130 7754 0 85 7757
   Swap: 8081 0 8081

   df -h
   Filesystem Size Used Available Use% Mounted on
   tmpfs 3.9G 236.0K 3.9G 0% /run
   /dev/vda1 15.6G 1.0G 13.8G 7% /
   devtmpfs 3.9G 0 3.9G 0% /dev
   tmpfs 3.9G 0 3.9G 0% /dev/shm
   tmpfs 3.9G 12.0K 3.9G 0% /var/lock

   Posted 1 month ago #
7. 

   shann
   

   offline

   Administrator

   Hi purpleleaf,

   Thanks for return.
   For /run, it's tmpfs and by default size is 50% of memory.

   For isos, i push them on my space because not follow official process on tank.
   Each version have cook chroot env on tank and automatically build/push packages/isos on mirror.

   For current64, use more recent kernel / toolchain can't be use cook chroot env on tank, why i push iso on my space.

   Posted 1 month ago #
8. 

   shann
   

   offline

   Administrator

   Hi purpleleaf,

   For video driver qxl, it's available on repository, you can install it with tazpkg -gi xorg-xf86-video-qxl.

   For vda-agent, need to take time to build it.

   Posted 1 month ago #
9. 

   purpleleaf
   

   offline

   Member

   Hi shann,
   many many thanks.

   The qxl driver works fine, but trying to run xrandr to set monitor resolution make xorg crash.
   I succesfully changed monitor resolution configuring a xorg conf file.

   I will wait for the vda-agent

   Many thanks again and Merry Christmas and Happy New Year

   Posted 1 month ago #
10. 

    shann
    

    offline

    Administrator

    Hi purpleleaf,

    Thanks for feedback, for xorg crash, need to check why :/

    Thanks, merry christmas and happy new year too (early little bit ^^)

    Posted 1 month ago #
11. 

    purpleleaf
    

    offline

    Member

    You're right, but i will not connect in the next few days (very likely until new year) so... best wishes ;)

    Posted 1 month ago #
12. 

    shann
    

    offline

    Administrator

    Hi purpleleaf,

    To be sure when you said vda-agent, it's qemu guest agent ?
    I build it, test with success on proxmox vm with slitaz 60 x64

    Remain create init.d script, for moment i run it manually.
    qemu-ga -f /var/run/qemu-ga.pid -t /var/run -l /var/log/qemu-ga.log -d

    root@cluster-aragog-01:~# qm agent 3002 get-osinfo
    {
    "kernel-release" : "5.10.238-slitaz64",
    "kernel-version" : "#2 SMP Mon Dec 22 13:07:01 Europe 2025",
    "machine" : "x86_64"
    }

    Posted 13 hours ago #
13. 

    shann
    

    offline

    Administrator

    packages qemu-guest-agent available and have init script to start/stop agent.

    Posted 13 hours ago #

RSS feed for this topic

Reply

You must log in to post.