TRIXMED Posted May 19, 2021 Share Posted May 19, 2021 I am a new user of UNRAID I want to move Virtual Machine (UBUNTU) from VMWARE to UNRAID. Do you need to convert VMWARE (ovf or vmdk file) to UNRAID file (img)? If so, how? Regards Quote Link to comment
itimpi Posted May 19, 2021 Share Posted May 19, 2021 You should be able to use a VMWare .vmdk file directly under KVM on UnRaid, but you will need to type the path in manually as there is no GUI support for selecting ..vmdk files. Quote Link to comment
ghost82 Posted May 19, 2021 Share Posted May 19, 2021 True, and remember to set as driver type 'vmdk' <disk type='file' device='disk'> <driver name='qemu' type='vmdk'/> <source file='/path/to/vmdk/file/diskname.vmdk'/> <target dev='hda' bus='sata'/> </disk> Read also the comment here: I would also convert that vmdk file, your choice! Quote Link to comment
TRIXMED Posted May 20, 2021 Author Share Posted May 20, 2021 I don't know where to enter this configuration? Quote Link to comment
ghost82 Posted May 20, 2021 Share Posted May 20, 2021 (edited) 6 minutes ago, TRIXMED said: I don't know where to enter this configuration? in your vm tab, click on your vm icon then edit xml, modify the section and save. Edited May 20, 2021 by ghost82 Quote Link to comment
TRIXMED Posted May 20, 2021 Author Share Posted May 20, 2021 I'm really new to UNRAID. Can you please tell me exactly what to do? I used TAB VMS ADD VM CUSTOM I typed the code into the XML window "<disk type = 'file' device = 'disk'> <driver name = 'qemu' type = 'vmdk' /> <source file = '/ path / to / vmdk / file / diskname.vmdk' /> <target dev = 'hda' bus = 'sata' /> </disk> " Of course, I gave the correct path to the vmdk file After pressing the create buttons a message appeared "XML error: unexpected root element <disk>, expecting <domain>" I am asking good souls for help. I want to run Unraid quickly Quote Link to comment
ghost82 Posted May 20, 2021 Share Posted May 20, 2021 8 minutes ago, TRIXMED said: I'm really new to UNRAID. Can you please tell me exactly what to do? I used TAB VMS ADD VM CUSTOM I typed the code into the XML window "<disk type = 'file' device = 'disk'> <driver name = 'qemu' type = 'vmdk' /> <source file = '/ path / to / vmdk / file / diskname.vmdk' /> <target dev = 'hda' bus = 'sata' /> </disk> " Of course, I gave the correct path to the vmdk file After pressing the create buttons a message appeared "XML error: unexpected root element <disk>, expecting <domain>" I am asking good souls for help. I want to run Unraid quickly I think you pasted/modify the code in the wrong place: where did you paste it?It seems at the same level of the <domain> section; the disk section has to be copied inside the <devices></devices> section. Paste here the full xml, please use the code tag to properly format, see </> button Quote Link to comment
TRIXMED Posted May 20, 2021 Author Share Posted May 20, 2021 As I wrote. I have no experience using VMs on UNRAID. I have several dockers installed, but no virtual machine. I have been using a VM with VMWare for several years. Now I want to move the finished machine to UNRAID. I copied the entire folder to the directory / mnt / disk1 / vmed / vmx / and i want to run it. Please help Quote Link to comment
ghost82 Posted May 20, 2021 Share Posted May 20, 2021 24 minutes ago, ghost82 said: Paste here the full xml, Paste the full code here, the code where you pasted the disk section, so we can look at it, modify and reupload here. Quote Link to comment
TRIXMED Posted May 20, 2021 Author Share Posted May 20, 2021 I don't know where the XML code I should modify is. As I wrote, I tried to use VMS ..............CUSTOM. After opening Custom, the XML window is shown. I don't think this is the right place Quote Link to comment
ghost82 Posted May 20, 2021 Share Posted May 20, 2021 (edited) 5 hours ago, TRIXMED said: I don't know where the XML code I should modify is. As I wrote, I tried to use VMS ..............CUSTOM. After opening Custom, the XML window is shown. I don't think this is the right place VM tab --> there's a list of your vms --> left click on the icon of the vm --> edit xml --> copy the whole content to a txt file, save it and upload it here. OR VM tab --> there's a list of your vms --> left click on the vm --> top right corner, switch to advance view (or xml view) --> copy the whole content to a txt file, save it and upload it here. Other than this I cannot be of more help. Edited May 20, 2021 by ghost82 Quote Link to comment
TRIXMED Posted May 21, 2021 Author Share Posted May 21, 2021 As I already wrote, I do not have a VM installed my server screenshots are attached. As I already wrote, I do not have a VM installed my server screenshots are attached Please help me on how to move VM to UnRAID. Quote Link to comment
ghost82 Posted May 21, 2021 Share Posted May 21, 2021 (edited) Ok, try to follow this video, from minute 7:34 to 10:50 Choose the Linux or Ubuntu template instead of windows 10 Do not set the OS install cdrom Choose VNC as graphics Do not select a sound card (none), or select the onboard audio (do not choose hdmi audio) Do not check any usb device Uncheck start vm after creation Click create Now you should have one vm in the vms tab. Then, 14 hours ago, ghost82 said: VM tab --> there's a list of your vms --> left click on the icon of the vm --> edit xml --> copy the whole content to a txt file, save it and upload it here. OR VM tab --> there's a list of your vms --> left click on the vm --> top right corner, switch to advance view (or xml view) --> copy the whole content to a txt file, save it and upload it here. Edited May 21, 2021 by ghost82 Quote Link to comment
TRIXMED Posted May 21, 2021 Author Share Posted May 21, 2021 I INSTALLED LINUX I don't know what video you are talking about. I can't find xml files anywhere Quote Link to comment
TRIXMED Posted May 21, 2021 Author Share Posted May 21, 2021 I found XML <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Linux</name> <uuid>deb64a9c-9ae5-5366-9ab5-38e4cc6329df</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/deb64a9c-9ae5-5366-9ab5-38e4cc6329df_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Linux/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:c7:9b:b4'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
TRIXMED Posted May 21, 2021 Author Share Posted May 21, 2021 I modified the xml file but the machine does not start <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Linux</name> <uuid>deb64a9c-9ae5-5366-9ab5-38e4cc6329df</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/deb64a9c-9ae5-5366-9ab5-38e4cc6329df_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='vmdk' cache='writeback'/> <source file='/mnt/disk1/vmed/vmx/vmx.vmdk'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:c7:9b:b4'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> Quote Link to comment
ghost82 Posted May 21, 2021 Share Posted May 21, 2021 (edited) My bad I didn't paste the link to the video...anyway happy to see that you found the xml. Try to create a new vm, but this time choose i440fx instead of q35 and seabios instead of ovmf. Or q35 + seabios. Then open again the new xml and modify the disk section as you did before. I cannot see the EFI partition in your screenshot of the uefi shell, so maybe the legacy bios seabios can boot that disk. Edited May 21, 2021 by ghost82 Quote Link to comment
TRIXMED Posted May 21, 2021 Author Share Posted May 21, 2021 Thank you very much For now, I've run a test MXlinux. It starts very quickly. I have the impression that it is faster than bare metal. I have a license generator on Ubuntu. I will test it on Monday. Do you know how to do VM to Docker conversion? This license generator has a web interface. After entering the data, he sends the license file to the internet database. It seems to me that using a VM is unnecessary Quote Link to comment
TRIXMED Posted May 24, 2021 Author Share Posted May 24, 2021 I did some testing with various linux vmdk images. I found that when I entered the complete path in the primary disk location field, e.g. /mnt/disk1/vmed/LICENSES/LICENSES.vmdk, type = 'vmdk' automatically appears in the xml file. So there is no need to edit the xml file. Unfortunately, my license generator won't start. Ubuntu booting up ok. And then the following picture shows Can you advise me something <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>LICENCJE SEABIOS Q35-5-1</name> <uuid>ddc33144-58ea-779b-79b7-655e1abca807</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.0.1'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='vmdk' cache='writeback'/> <source file='/mnt/disk1/vmed/LICENCJE/LICENCJE.vmdk'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:ec:e5:b1'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> </domain> QEMU (LICENCJE SEABIOS Q35-5-1) - noVNC2.pdf Quote Link to comment
ghost82 Posted May 24, 2021 Share Posted May 24, 2021 7 minutes ago, TRIXMED said: my license generator won't start mmm I think this has something to do with the uuid of the root disk, which could have changed, because the "virtual hardware" changed. You should need to check the fstab and change there the uuid of the root volume to the actual one. It happened to me after restoring a linux dd image to a new disk, with manjaro I had to boot from an external usb with a live manjaro on it, run chroot to modify the installed environment and change the uuid. I don't know if something similar exists for ubuntu, if it does, instead of booting from a usb (which could be tricky), I would add a cdrom in qemu with its path pointing to the live iso of ubuntu and boot from it. Quote Link to comment
TRIXMED Posted May 24, 2021 Author Share Posted May 24, 2021 Unfortunately, today I have a lot of other activities? Can you tell me where the UUID can be changed. I understand that this may have something to do with QEMU. I copied the license disk to several places and VMWARE PLAYER16 always started the machine. There was no problem with the uuid. Meanwhile, UnRAID has a problem. I tried to use the Linux and Ubuntu template. Quote Link to comment
ghost82 Posted May 24, 2021 Share Posted May 24, 2021 (edited) I mean the uuid of your disk inside the vmdk image file. I think that vmware is always able to start that vmdk because it emulates a specific machine: with that machine ubuntu booted from vmware generated the uuid for the disk inside the vmdk; that uuid is stored in the fstab file, and ubuntu booted from vmware will always be able to mount the disk since the uuid in the fstab reflects that of the disk in the vmdk file. Qemu emulates another type of machine, so uuid could have changed, so the uuid in the fstab file is not that of the real new disk, and ubuntu cannot find what to mount. I never tried ubuntu, the following is only a research on google, based on what I would do to change the uuid on that vmdk file, commands may be different since I didn't test them in a live environment. First copy your vmdk file and store it in a secure place. 0. Download a live iso of ubuntu if you don't have one, I assume you have if you installed it. 1. Modify your virtual machine, to add a virtual cd rom, pointing to the ubuntu live iso file; eventually change the boot order, so that the vm boots from cd first. Let the vmdk disk file attached. 2. Once booted from the emulated cdrom go to a terminal from the live iso 3. Assuming the disk in the vmdk file is formatted as ext4, mount the partition (assumed as sda1) of that disk: sudo mount -t ext4 /dev/sda1 /mnt A tutorial tells also to bind /dev /run /proc and /sys, not sure if it's necessary: for i in dev proc sys run; do sudo mount --bind /$i /mnt/$i; done 4. chroot into the mounted partition: the chroot command is a useful command that allows you to operate on the existing installation (on sda1 in this case) from a live cd: sudo chroot /mnt 5. List the uuid: ls -l /dev/disk/by-uuid You will see next to sda1 (in this example) its uuid, write down in a piece of paper that uuid. 6. Edit the fstab file: sudo nano /etc/fstab 7. see if the uuid listed in fstab for sda1 (in this example) is different from that you took note; if it's different replace the uuid with the new one, save the fstab file and exit nano; note, I'm using "nano" here as a text editor, most probably the live ubuntu doesn't have it, search what is the command line editor in ubuntu and use it instead of nano. 8. exit chroot: exit 9. unmount the disk: cd ~ for i in /dev /proc /sys /run /; do sudo umount -l /mnt$i; done sudo umount /dev/sda1 /mnt 10. Shutdown the vm 11. Remove the virtual cdrom from the vm 12. Start the vm Good luck Edited May 24, 2021 by ghost82 Quote Link to comment
TRIXMED Posted May 25, 2021 Author Share Posted May 25, 2021 I was unable to install. I think I will give up such a solution. In case of UNRAID server failure, I will have a lot of trouble. I don't think you can base everything on one server. For now, I'm testing UNRAID on an old unused server. In a few days I will receive the ordered large powerful server. I cannot understand why MXLinux.vmdk can be migrated without any problem, while UBUNTU.vmdk cannot. I will try to prepare a new UBUNTU machine tomorrow. The license generator on the UBUNTU machine has been in operation for over 10 years and is based on Ubuntu 10. Maybe this is the reason? How do I move Windows 7-10.vmdk machines? Quote Link to comment
TRIXMED Posted May 27, 2021 Author Share Posted May 27, 2021 Thank you for your help Finally, I ran my license generator. I have converted my vmware machine to the latest format. I copied to UNRAID I have created a VMS type UBUNTU I chose: MACHINE: I440 fx 5-1 BIOS: SEABIOS Primary vDisk Location: Manual: /mnt/.../LICENCE.vmdk I will try the same for Windows Quote Link to comment
ghost82 Posted May 27, 2021 Share Posted May 27, 2021 1 minute ago, TRIXMED said: I have converted my vmware machine to the latest format Nice, that did the trick! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.