February 21, 20188 yr I found some software (LibreNMS) id like to try in a VM There is a vmdk image supplied https://docs.librenms.org/#Installation/CentOS-image/ Is it possible to convert this image to run in KVM? Edited February 22, 20188 yr by rorton auto spell keeps converting vmdk to vodka!
February 21, 20188 yr KVM can handle vmdk files directly. The only caveat is that you have to enter the full path to the vmdk when creating the VM as the GUI does not provide a selector for that file type.
February 21, 20188 yr Author thanks i just tried, and i get this far: Image here /mnt/cache/vms/LibreNMS/vdisk1.img ISO here /mnt/user/isos/librenms_centos_7.vmdk
February 21, 20188 yr Is the image UEFI compatible? Try creating a new VM template, this time select SeaBIOS instead of OVMF before starting it for the first time. Advanced view.
February 22, 20188 yr Author thanks, wasn't aware of the advanced tab! so used that, and i get a diff BIOS boot now: Im guessing this is an issue with the VMDK file? my xml for the vm is: <domain type='kvm' id='31'> <name>Libre</name> <uuid>05cdac3e-6001-b20c-6a2d-7f700b29f005</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.10'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='1' threads='1'/> </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/cache/vms/Libre/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/librenms_ubuntu_1604.vmdk'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <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'/> <alias name='pci.2'/> <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'/> <alias name='pci.3'/> <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'/> <alias name='pci.4'/> <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'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/user/data/'/> <target dir='data'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:82:46:71'/> <source bridge='virbr0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-31-Libre/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' 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'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
February 22, 20188 yr Try switching the vdmk to boot order 1 and the vdisk to boot order 2. Why do you even have a vdisk entered? I thought you were trying to run the vdmk as the VM's hard drive?
February 22, 20188 yr Author 15 hours ago, jonathanm said: Try switching the vdmk to boot order 1 and the vdisk to boot order 2. Why do you even have a vdisk entered? I thought you were trying to run the vdmk as the VM's hard drive? tried that, still the same - no ideas why i have a disk setup, this is the first time ive messed about with the VM side of things, so really don't know how it works. I assumed that the vmdk was the equivalent of an ISO, and i needed to set it up like that Are you saying that the vmdk is the replacement for the .img file and should sit in my vm disks folders? Edited February 22, 20188 yr by rorton vmdk spell checked as vodka again!
February 22, 20188 yr I had no problems getting this to run! I did the following when creating the VM: create a new VM and select the Centos option make sure that the Advanced view is selected (at top right) set the BIOS to use SeaBios Set the primary vdisk to use SATA, Manual mode and then set the path to point to the .vmdk file set the network to a bridged connection (br0 in my case) create the VM it will now be running and you can connect to it via the built-in VNC Remote or via a VNC client running on another machine (using the port shown for the running VM). If you want to connect directly to the VM bypassing VNC then you will need to gets its IP address either from your router, or using a scanning application such as Fing, or by doing an ‘ifconfig’ command from a login via VNC. Edited February 22, 20188 yr by itimpi
February 22, 20188 yr Author 1 hour ago, itimpi said: I had no problems getting this to run! I did the following when creating the VM: create a new VM and select the Centos option make sure that the Advanced view is selected (at top right) set the BIOS to use SeaBios Set the primary vdisk to use SATA, Manual mode and then set the path to point to the .vmdk file set the network to a bridged connection (br0 in my case) create the VM it will now be running and you can connect to it via the built-in VNC Remote or via a VNC client running on another machine (using the port shown for the running VM). If you want to connect directly to the VM bypassing VNC then you will need to gets its IP address either from your router, or using a scanning application such as Fing, or by doing an ‘ifconfig’ command from a login via VNC. THANKYOU followed your points, and got it working - i need to read/play a bit with the vm stuff i think. I didn't have the disk set to sata, it was set to virtio.
February 22, 20188 yr 1 hour ago, rorton said: I didn't have the disk set to sata, it was set to virtio For that to work you would have needed the virtio drivers loaded in the VM. I had a look at the .ova version and that was where I saw that it was expecting SATA and that it did not support UEFI (and thus the need to change to SeaBios for legacy style booting).
November 27, 20187 yr On 2/22/2018 at 4:46 PM, itimpi said: set the network to a bridged connection (br0 in my case) "...gets its IP address either from your router..." I'm trying to set this all up, and I got the VM working now, thanks to you! However, I was still unable to connect to the internet using this method. I'm using an openSUSE vmdk as an image, and it seems like no matter what kind of modification I do, I will not be able to pass the network controller to the vm. Any tips for this? (I have a bunch other VMs running parallel, each using br0 interface, they all able to communicate on ipv6/4.)
April 15, 20197 yr On 2/22/2018 at 10:46 AM, itimpi said: I had no problems getting this to run! I did the following when creating the VM: create a new VM and select the Centos option make sure that the Advanced view is selected (at top right) set the BIOS to use SeaBios Set the primary vdisk to use SATA, Manual mode and then set the path to point to the .vmdk file set the network to a bridged connection (br0 in my case) create the VM it will now be running and you can connect to it via the built-in VNC Remote or via a VNC client running on another machine (using the port shown for the running VM). If you want to connect directly to the VM bypassing VNC then you will need to gets its IP address either from your router, or using a scanning application such as Fing, or by doing an ‘ifconfig’ command from a login via VNC. Thank you also for sharing and confirming!
April 15, 20197 yr Update: I am trying to migrate a SophosUTM from VMware ESXi (vmdk) to Unraid as a VM. I following these above settings and it still not seeing the disk. It boots to "waiting for device /dev/disk/by-label/root to appear", then it results in "could not find /dev/disk/by-label/root" Any ideas? Edited April 15, 20197 yr by guruleenyc
April 30, 20197 yr Trying to boot off install ISO with br0 as interface in VM settings, but installer states "no network card was found". Any help would be appreciated.
April 30, 20197 yr 1 hour ago, guruleenyc said: Trying to boot off install ISO with br0 as interface in VM settings, but installer states "no network card was found". Any help would be appreciated. What type of network card is being emulated? If the default of virtio then the OS will need a virtio network driver loaded before it can access the network. If not already present this would normally be loaded off the virtio CD image.
April 30, 20197 yr 1 hour ago, itimpi said: What type of network card is being emulated? If the default of virtio then the OS will need a virtio network driver loaded before it can access the network. If not already present this would normally be loaded off the virtio CD image. Thanks for the quick reply! My VM interface settings are: <interface type='bridge'> <mac address='52:54:00:c2:66:6d'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> Not sure how to get the virtio drivers loaded into the VM, there's no option for driver ISO under vm settings.
August 10, 20196 yr On 2/22/2018 at 10:46 AM, itimpi said: I had no problems getting this to run! I did the following when creating the VM: create a new VM and select the Centos option make sure that the Advanced view is selected (at top right) set the BIOS to use SeaBios Set the primary vdisk to use SATA, Manual mode and then set the path to point to the .vmdk file set the network to a bridged connection (br0 in my case) create the VM it will now be running and you can connect to it via the built-in VNC Remote or via a VNC client running on another machine (using the port shown for the running VM). If you want to connect directly to the VM bypassing VNC then you will need to gets its IP address either from your router, or using a scanning application such as Fing, or by doing an ‘ifconfig’ command from a login via VNC. THANK YOU! Following these steps exactly got me passed the import of Wazuh VMDK "kernal panic fatal error'. It is now booting! :-) Now onto configuring it hopefully.
February 22, 20206 yr On 5/1/2019 at 2:31 AM, itimpi said: What type of network card is being emulated? If the default of virtio then the OS will need a virtio network driver loaded before it can access the network. If not already present this would normally be loaded off the virtio CD image. thanks
April 20, 20206 yr did any of you guys have a permissions issue starting the VM? I kept getting a Permission Denied error trying to start the VM...
June 19, 20206 yr i had a vmdk from my qnap what i did to get it working is Thx to lots of googling. open a console on unraid and type qemu-img convert -p -f vmdk -O raw /mnt/user/<the location of your vmdk file> /mnt/user/<the location of your new file>.img than make a VM and link to that img file and start it. Worked for me
July 3, 20215 yr On 2/23/2018 at 1:46 AM, itimpi said: I had no problems getting this to run! I did the following when creating the VM: create a new VM and select the Centos option make sure that the Advanced view is selected (at top right) set the BIOS to use SeaBios Set the primary vdisk to use SATA, Manual mode and then set the path to point to the .vmdk file set the network to a bridged connection (br0 in my case) create the VM it will now be running and you can connect to it via the built-in VNC Remote or via a VNC client running on another machine (using the port shown for the running VM). If you want to connect directly to the VM bypassing VNC then you will need to gets its IP address either from your router, or using a scanning application such as Fing, or by doing an ‘ifconfig’ command from a login via VNC. On 2/23/2018 at 2:56 AM, rorton said: THANKYOU followed your points, and got it working - i need to read/play a bit with the vm stuff i think. I didn't have the disk set to sata, it was set to virtio. Just wanted to say thanks for the solution here. Can State that the above settings still working a treat today for running MetaSploitable.vmdk Directly in UnRaid VM manager. No need to convert the vmdk just configure the new VM as above and off you go.
July 3, 20215 yr On 6/19/2020 at 10:34 PM, KoNeko said: i had a vmdk from my qnap what i did to get it working is Thx to lots of googling. open a console on unraid and type qemu-img convert -p -f vmdk -O raw /mnt/user/<the location of your vmdk file> /mnt/user/<the location of your new file>.img than make a VM and link to that img file and start it. Worked for me You can normally avoid converting the .vmdk file and use it directly as long as you enter the full path to it manually and not via selecting it from the GUI.
December 10, 20223 yr Sorry to dig up this old post but can xen handle split vmdk files? (I currently have a bunch of vmware VMs with split VMDKs running on vmware workstation 16.x) and would like to run the Vm on unraid. Thanks!
December 11, 20223 yr As far as I know qemu isn't able to manage splitted vmdk files, but you can merge them into one vmdk. There should be tools available in internet.
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.