LinuxQuestions.org
Help answer threads with 0 replies.
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 04-10-2021, 09:53 PM   #1
epitaxial
Member
 
Registered: Dec 2019
Posts: 38

Rep: Reputation: Disabled
Current no longer works in ESXI


Once in a while I try -current (64) in an ESXI VM. A few weeks ago something changed and it no longer sees the virtual disk. Here is the output from dmesg. I'm running ESXI 6.
Attached Files
File Type: txt log.txt (68.9 KB, 20 views)
 
Old 04-11-2021, 04:31 AM   #2
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
I've got a VM running on ESXi 6.7 which I installed using an iso made from the current tree on 12 March, with kernel 5.10.22.

The log you posted shows that the controller gets loaded. What happens next? Can you ssh into the machine? What actual errors do you get?
 
Old 04-11-2021, 09:17 AM   #3
epitaxial
Member
 
Registered: Dec 2019
Posts: 38

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by rkelsen View Post
I've got a VM running on ESXi 6.7 which I installed using an iso made from the current tree on 12 March, with kernel 5.10.22.

The log you posted shows that the controller gets loaded. What happens next? Can you ssh into the machine? What actual errors do you get?
Running lsblk shows no drives are detected. I was able to run ifconfig and tftp the log file out.
Attached Thumbnails
Click image for larger version

Name:	lsblk.png
Views:	24
Size:	23.2 KB
ID:	36065  
 
Old 04-11-2021, 09:40 AM   #4
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 845

Rep: Reputation: Disabled
Long time ago, a thing happened to me where I lost access to virtual hardware because the host kernel was upgraded.
Turned out I did forget to recompile relevant modules on the host. It can also happen on guest if the kernel is updated and tools are not re-installed.
Just a possibility to consider, however, none of this happens to me anymore since I moved everything to KVM which is included in the kernel.
 
Old 04-11-2021, 09:44 AM   #5
epitaxial
Member
 
Registered: Dec 2019
Posts: 38

Original Poster
Rep: Reputation: Disabled
This is booting from a new VM with a blank disk.
 
Old 04-11-2021, 07:18 PM   #6
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
Quote:
Originally Posted by epitaxial View Post
Running lsblk shows no drives are detected.
That is quite strange. I see LSI Logic SAS listed as the SCSI controller in the dmesg output. Is that what you're running?

Looks like you're using the ESXi console, so clearly you can log in and run commands that way. Have you installed VMWare tools?
 
Old 04-11-2021, 07:38 PM   #7
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
Quote:
Originally Posted by elcore View Post
Long time ago, a thing happened to me where I lost access to virtual hardware because the host kernel was upgraded.
That's a different issue to the one being discussed here. VMware ESXi is not Linux, and its kernel is not updated separately from the rest of the system.
 
Old 04-11-2021, 09:30 PM   #8
epitaxial
Member
 
Registered: Dec 2019
Posts: 38

Original Poster
Rep: Reputation: Disabled
This is a blank VM and I'm booting from the iso provided by Alien Bob. This isn't a currently running system, I'm trying to do a new install inside ESXI. Several weeks ago this process worked fine. It would boot, detect a disk and allow me to install.
 
Old 04-11-2021, 09:43 PM   #9
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
OK. So that's AB's iso? Which version? I'll make an iso from today's current and will let you know what happens.
 
Old 04-11-2021, 11:14 PM   #10
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
Experiment done, using an iso file created from the -current tree updated for all changes up to & including Friday 9 April.

New VM: [Other 4.x or later Linux (64 bit)]
Default settings, except for:
4 vCPUs
4096Mb RAM
LSI Logic SAS SCSI controller,
50Gb virtual disk - thin provisioned
Video card - 10Mb memory
CD/DVD drive - datastore iso (picked iso file)

It boots the setup kernel & initrd without any issues.

This is what I get:

Code:
root@slackware:/# lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda    8:0    0   50G  0 disk
sr0   11:0    1  3.3G  0 rom
root@slackware:/#
Perhaps there's a problem with your download?
 
Old 04-12-2021, 12:27 AM   #11
z80
Member
 
Registered: Jul 2019
Location: Europe
Distribution: Slackware
Posts: 49

Rep: Reputation: 25
How is your VM configuration on the ESXi?
 
Old 04-12-2021, 05:34 AM   #12
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 845

Rep: Reputation: Disabled
Quote:
Originally Posted by rkelsen View Post
That's a different issue to the one being discussed here. VMware ESXi is not Linux, and its kernel is not updated separately from the rest of the system.
Well, just assumed it's the kernel because of the OP where it worked before, but stopped working at some point after the upgrade of guest OS.
And what other part was recently updated in Slackware, other than the kernel, which has an effect on virtual hardware recognition?
I'd dare to assume hwdata or eudev, but it's not that easy to guess with no logs other than dmesg.

Also. the usual point of failure is that the distributions' kernel provides the open source vmware module, where normally this type of software expects an out-of-tree module.
So it could be a regression, or intentional change in the kernel, which may require an update of hypervisor software on the host.

In any case, I don't know how is this a Slackware problem unless there is evidence of Slackware changing something internally and causing a regression.
Are other distributions working in that same scenario? Does the older version of Slackware work in the same scenario?
 
Old 04-12-2021, 07:57 AM   #13
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
Quote:
Originally Posted by elcore View Post
Does the older version of Slackware work in the same scenario?
The current version works. See post #10 above. I tried it and was unable to replicate OP's problem.
 
1 members found this post helpful.
Old 04-12-2021, 07:51 PM   #14
epitaxial
Member
 
Registered: Dec 2019
Posts: 38

Original Poster
Rep: Reputation: Disabled
I'm using the slackware64-current-install-dvd.iso dated 2021-04-09 from https://slackware.uk/people/alien-cu...4-current-iso/
Here is the VM config. Every other operating system will boot and install, *BSD, Lubuntu, Windows.
Attached Thumbnails
Click image for larger version

Name:	esxi_settings.png
Views:	17
Size:	32.6 KB
ID:	36081  
 
Old 04-12-2021, 09:39 PM   #15
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,868

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
Quote:
Originally Posted by epitaxial View Post
Here is the VM config.
You need to change the SCSI controller from VMware Paravirtual to LSI Logic SAS.

Once the installation is complete and you have installed VMware Tools, then *I think* you can switch to the ParaVirtual SCSI controller.

Edit: I just checked the stock Slackware configs - the VMware PVSCSI driver is built as a module on both the huge and generic kernels. You can add it to your initrd and then switch over and it should work. But for installation, you'll definitely need to use the LSI Logic SAS SCSI controller. To correct my previous statement - you don't need to install VMWare Tools to get support for the PV SCSI controller.

Last edited by rkelsen; 04-12-2021 at 09:51 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Fedora 22 filer upgraded to Fedora 29 - no longer presenting luns to initiators (CentOS 7 / ESXi 6.0) JoseCuervo Linux - Server 0 04-03-2019 01:45 AM
[SOLVED] No longer able to add multiple TC rules on same handle in current kernels (4.5.5 works, but anything current does not) herbalbert Linux - Networking 1 01-24-2019 10:08 AM
LXer: Upgrade/Migrate VMware ESX/ESXi 4.x To ESXi 5.0 LXer Syndicated Linux News 0 09-11-2011 03:10 PM
RAID card for vmware esxi, and some other esxi questions JustinHoMi Linux - Enterprise 1 06-04-2010 03:57 PM
DVB usb device no longer detected as a DVB , but as V4L., so no longer works vdemuth Slackware 4 12-21-2008 06:31 PM

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

All times are GMT -5. The time now is 12:02 PM.

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