# Virtualization 7.1.4 **URL:** \ **Category:** UNIX for Beginners Q & A\ **Created:** [November 21, 2025, 1:07pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365 "2025-11-21T13:07:58Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Bleche0815](https://community.unix.com/letter_avatar/bleche0815/32/5_5575768a8748004e209b776fc1b2916d.png) [@Bleche0815](https://community.unix.com/u/Bleche0815)\ **Post date:** [November 21, 2025, 1:07pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/1 "2025-11-21T13:07:58Z")
Hi everyone, I have a question about virtualizing UNIXware 7.1.4. We have a physical Unix machine with a LSI megasas RAID Controller and it needs to be virtualized. So we booted from a Linux Live CD and performed a disk dump of the partitions. ```plaintext (/dev/sda and /dev/sdb) ``` These images were booted in VirtualBox. During startup, the Unix logo appears, but then the errors "megasas: FW in FAULT state" and "PANIC: vfs\_mountroot: cannot mount root" occur. How can we fix this error? Several tests and searches using the boot prompt and the emergency disk have unfortunately not led to a solution. Perhaps someone can give me a hint? Is it possible to rebuild the kernel at current state in the virtual machine and disable the megasas controller maybe? Thanks in Advance ---
**Author:** ![jgt](https://community.unix.com/user_avatar/community.unix.com/jgt/32/10703_2.png) [@jgt](https://community.unix.com/u/jgt)\ **Post date:** [November 21, 2025, 6:54pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/2 "2025-11-21T18:54:29Z")
Which disk controller did you choose in the VirtualBox settings? ---
**Author:** ![Bleche0815](https://community.unix.com/letter_avatar/bleche0815/32/5_5575768a8748004e209b776fc1b2916d.png) [@Bleche0815](https://community.unix.com/u/Bleche0815)\ **Post date:** [November 21, 2025, 8:22pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/3 "2025-11-21T20:22:50Z")
hey jgt, its an "lsi megasas" raid controller at the physical system. At virtualbox I tried different controller settings like LSI Logal or LSI Logal SAS. The error message never changed. ---
**Author:** ![jgt](https://community.unix.com/user_avatar/community.unix.com/jgt/32/10703_2.png) [@jgt](https://community.unix.com/u/jgt)\ **Post date:** [November 21, 2025, 10:00pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/4 "2025-11-21T22:00:26Z")
I searched “megasas: FW in FAULT state” and my interpretation of the results is that the device driver is not finding the card microcode. Try doing a fresh install on the VM, and then doing a restore from the production system. ---
**Author:** ![Bleche0815](https://community.unix.com/letter_avatar/bleche0815/32/5_5575768a8748004e209b776fc1b2916d.png) [@Bleche0815](https://community.unix.com/u/Bleche0815)\ **Post date:** [November 22, 2025, 10:31am UTC](https://community.unix.com/t/virtualization-7-1-4/397365/5 "2025-11-22T10:31:33Z")
Ok I did a fresh install on virtual box and I can boot the system. So what do you think its the best option now: Attach the 2 images (sda.img and sdb.img) to the working vm and mount / copy the disks and files? Or what do you exactly mean with a restore from the production system? Thanks again for your help. ---
**Author:** ![jgt](https://community.unix.com/user_avatar/community.unix.com/jgt/32/10703_2.png) [@jgt](https://community.unix.com/u/jgt)\ **Post date:** [November 22, 2025, 4:24pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/6 "2025-11-22T16:24:02Z")
Make a backup copy of the new VM, then mount the two images. Do not copy the kernel or configuration files. I don’t know Unixware as well as Openserver, so I am guessing that you should not copy /stand, or /etc/conf. ---
**Author:** ![Bleche0815](https://community.unix.com/letter_avatar/bleche0815/32/5_5575768a8748004e209b776fc1b2916d.png) [@Bleche0815](https://community.unix.com/u/Bleche0815)\ **Post date:** [November 26, 2025, 12:05pm UTC](https://community.unix.com/t/virtualization-7-1-4/397365/7 "2025-11-26T12:05:12Z")
hello, An update on the issue: The "megasas" message disappears when the kernel is rebuilt using the "new" base image with VirtualBox. I just switched the kernel file "unix" manually. However, it still can't find the root directory/disk. I've done some research, and it's possible to restore the necessary directories like "/" and /stand. ```plaintext NOTE: OpenServer commands might be different! mount the new '/' at /mnt; mount /stand at /mnt/stand # chroot /mnt /bin/sh # /usr/sbin/disksetup -B -b /etc/boot /dev/rdsk/c0b0t0d0s0 # exit # cd / # sync; sync; sync # sh_umount /mnt/stand # sh_umount /mnt CTRL-ALT-DEL to reboot ``` I can access the /dev/sda image from the old physical system. What could be meant by mounting the "old" root directory? Thanks for any further hints or advice. ---
**Author:** ![Bleche0815](https://community.unix.com/letter_avatar/bleche0815/32/5_5575768a8748004e209b776fc1b2916d.png) [@Bleche0815](https://community.unix.com/u/Bleche0815)\ **Post date:** [December 3, 2025, 7:47am UTC](https://community.unix.com/t/virtualization-7-1-4/397365/8 "2025-12-03T07:47:34Z")
hello, an update on the case: I got the system to boot. I had to exchange the files from the /stand directory from the disk dump backup (/dev/sda). I started the fresh install image and mounted the "/stand - /dev/dsk" from the disk-dump backup. After that I could start unix with the disk-dump images and can change the vfstab-file and the network-configuration for my internal usage. ---
**Author:** ![system](https://community.unix.com/uploads/default/original/2X/c/c7e9e16a595259edafe88615719d5c5dcda035c2.png) [@system](https://community.unix.com/u/system)\ **Post date:** [June 1, 2026, 7:47am UTC](https://community.unix.com/t/virtualization-7-1-4/397365/9 "2026-06-01T07:47:57Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.