LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-05-2020, 06:44 PM   #1
Panagiotis Nik
Member
 
Registered: Jul 2014
Distribution: Slackware64-Current, Slackware64-14.2
Posts: 33

Rep: Reputation: Disabled
Slackware64-current as a KVM host


Yesterday I wanted to install Slackware64-current in a KVM host. I grabbed the iso (thanks to alienbob) and I started the installation process.
When it was time to install lilo I chose expert and I changed the disk from sda to vda and I also added: bios = 0x80 max-partitions = 7.
Despite the above settings lilo was complaining with: "linux experimental device 0xfd00 needs to be defined"

I ended up to change the disk driver from virtio to ide but I would like to know what I was missing or doing wrong...
 
Old 06-06-2020, 07:58 AM   #2
davleema
Member
 
Registered: Jun 2015
Location: Belgium
Distribution: Slackware x64
Posts: 43

Rep: Reputation: Disabled
Quote:
Originally Posted by Panagiotis Nik View Post
Yesterday I wanted to install Slackware64-current in a KVM host. I grabbed the iso (thanks to alienbob) and I started the installation process.
When it was time to install lilo I chose expert and I changed the disk from sda to vda and I also added: bios = 0x80 max-partitions = 7.
Despite the above settings lilo was complaining with: "linux experimental device 0xfd00 needs to be defined"

I ended up to change the disk driver from virtio to ide but I would like to know what I was missing or doing wrong...
I guess the virtio driver is mising or not loaded anyway. I am running several Slackware VM's on a Proxmox VE server,and always use the IDE driver. Works fine.
 
Old 06-06-2020, 05:40 PM   #3
Panagiotis Nik
Member
 
Registered: Jul 2014
Distribution: Slackware64-Current, Slackware64-14.2
Posts: 33

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by davleema View Post
I guess the virtio driver is mising or not loaded anyway. I am running several Slackware VM's on a Proxmox VE server,and always use the IDE driver. Works fine.
I checked for virtio in the config-huge and it seems most of the virtio modules are already built-in:

grep 'VIRTIO' config-huge-5.4.44.x64
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
CONFIG_NET_9P_VIRTIO=y
CONFIG_VIRTIO_BLK=y
# CONFIG_VIRTIO_BLK_SCSI is not set
CONFIG_SCSI_VIRTIO=y
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM_VIRTIO=y
CONFIG_DRM_VIRTIO_GPU=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_MENU=y
CONFIG_VIRTIO_PCI=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_VIRTIO_PMEM=m
CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_INPUT=m
CONFIG_VIRTIO_MMIO=y
# CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set
CONFIG_RPMSG_VIRTIO=m
CONFIG_VIRTIO_FS=m
CONFIG_CRYPTO_DEV_VIRTIO=m

I found a similar problem: https://www.linuxquestions.org/quest...-issue-871981/ that goes back to 2011 and the suggestion was to use a generic kernel with a initrd. But it seems that nowadays the huge kernel has the necessary modules like CONFIG_VIRTIO_BLK already built-in.

Last edited by Panagiotis Nik; 06-06-2020 at 05:48 PM.
 
Old 06-07-2020, 12:57 AM   #4
kingbeowulf
Senior Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware
Posts: 1,267
Blog Entries: 11

Rep: Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744Reputation: 744
Quote:
Originally Posted by Panagiotis Nik View Post
I checked for virtio in the config-huge and it seems most of the virtio modules are already built-in:

...

I found a similar problem: https://www.linuxquestions.org/quest...-issue-871981/ that goes back to 2011 and the suggestion was to use a generic kernel with a initrd. But it seems that nowadays the huge kernel has the necessary modules like CONFIG_VIRTIO_BLK already built-in.
I run a variety of Slackware guests for testing, clean compiles/packages and various other nonsense. I've noted that on the 14.2 and current guests, using huge.s, the built in virtio modules aren't detected/used/loaded for some reason. I never did figure out why. maybe some qemu/KVM quirk? I thus always use generic kernel + initrd. A side effect is that the generic kernel has a smaller memory footprint - handy back when my host was RAM limited.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] "No KVM, No qemu-kvm" Available error while trying to install KVM on CentOS 6.3 sriramdas Linux - Virtualization and Cloud 5 01-01-2013 10:46 AM
KVM on Redhat 5.7: KVM can ping outside network, outside network can't ping KVM svandyk Linux - Networking 1 09-23-2011 06:45 AM
[Debian/Qemu/KVM] Why qemu --enable-kvm works but not kvm directly? gb2312 Linux - Virtualization and Cloud 2 03-21-2011 02:05 PM
upgrading slackware64 13.1 multilib to slackware64 -current multilib Cultist Slackware 4 03-12-2011 09:04 AM
Updating from Slackware64-current to Slackware64 13. glore2002 Slackware 4 08-28-2009 06:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:32 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration