mhvtl
mhvtl copied to clipboard
markh794
Setup procedure
Hi, I just installed the 1.6.4 RPM and started the service, but don't see any devices in lsscsi -g what steps are missing in order to
get devices to be visible in lsscsi?
sudo systemctl status mhvtl.target
● mhvtl.target - mhvtl service allowing to start/stop all [email protected] and [email protected] instances at once
Loaded: loaded (/usr/lib/systemd/system/mhvtl.target; enabled; vendor preset: disabled)
Active: active since Wed 2022-06-22 22:07:44 UTC; 20min ago
Docs: man:man:vtltape(1)
man:man:vtllibrary(1)
Jun 22 22:07:44 systemd[1]: Reached target mhvtl service allowing to start/stop all [email protected] and [email protected] instances at once.
Sorry for the delay in responding.
If you run 'lsmod | grep vtl' - you should see something like:
# lsmod | grep vtl
mhvtl 45056 32
otherwise, some hints may be in the 'syslog' - typically /var/log/messages
Feel free in attaching the /var/log/messages.
Alternatively, try running a single tape daemon in debug mode
e.g.
# vtltape -q 11 -d | tee /tmp/vtltape.out (and provide /tmp/vtltape.out for further troubleshooting steps)
In another terminal - check if device '11' is running using the 'lsscsi' command.
To exit the above 'vtltape' in debug mode, simply run:
# vtlcmd 11 exit
lsmod | grep vtl
Is empty so how do I enable the kernel module for it?
As an aside: I tried running the CentOS vagrant box and ran into an issue where it didn't have permissions for the preload_tape in the usr Makefile. I think had to modify it to use sudo to create the links. But then it worked.
The kernel module build is a unique step.
Change directory into kernel module source: cd mhvtl/kernel
Build the module against the current running kernel: make
Copy mhvtl.ko to a known location: make install
Load the module: modprobe mhvtl opts=0
Check the module is loaded - lsmod | grep vtl
Once the kernel module is loaded, the user space should start up OK :)
Hi, i meet the same problem. Following your instructions, i run modprobe mhvtl opts=0, and get the following error:
modprobe: ERROR: could not insert 'mhvtl': Exec format error.
BTW, im using WSL2 and have already recompiled the kernel to install the kernel-devel.
Hmmm. Never tried with WSL. Let me spin up an environment this week and see if I can reproduce the error
Hi, i meet the same problem. Following your instructions, i run
modprobe mhvtl opts=0, and get the following error:modprobe: ERROR: could not insert 'mhvtl': Exec format error.
BTW, im using WSL2 and have already recompiled the kernel to install the kernel-devel.
Can I get a "uname-a" output please
Hi, i meet the same problem. Following your instructions, i run
modprobe mhvtl opts=0, and get the following error: modprobe: ERROR: could not insert 'mhvtl': Exec format error. BTW, im using WSL2 and have already recompiled the kernel to install the kernel-devel.
Trying to spin up WSL now.
What distribution are you using ?
https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature lists various common distros.
Hi, i meet the same problem. Following your instructions, i run
modprobe mhvtl opts=0, and get the following error: modprobe: ERROR: could not insert 'mhvtl': Exec format error. BTW, im using WSL2 and have already recompiled the kernel to install the kernel-devel.Trying to spin up WSL now. What distribution are you using ? .appx
https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature lists various common distros.
Thx for your reply. The info is below ~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.6 LTS Release: 20.04 Codename: focal ~$ uname -r 5.15.79.1-microsoft-standard-WSL2