I searched but can't seem to find an answer.

Is it possible to import a bunch of preexisting VMs from Virtualbox into unRAID?

If so then how do I do that?

you cannot 'import' them as such.    However you can set up a new VM and use the VirtualBox .vdi file from one of the existing VirtualBox VMs.    It is just a case of specifying the full path manually to the .vdi file when setting up the VM and not trying to select it via the GUI.

Thank you

Is there a tutorial somewhere? I tried using the vdi with a linux template but when I VNC into it I get a black screen with shell on it.

 

The XML from the template looked like this:

 

<domain type='kvm'>
  <name>t2</name>
  <uuid>4668687c-67e9-ab4d-7c9a-a05fecc905cd</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/>
  </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-2.5'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/4668687c-67e9-ab4d-7c9a-a05fecc905cd_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <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='vdi' cache='writeback'/>
      <source file='/mnt/user/domains/t2.vdi'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </disk>
    <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>
    <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='dmi-to-pci-bridge'>
      <model name='i82801b11-bridge'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:6e:2a:55'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='connect'/>
      <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'/>
    <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'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Anyone pleases help me figure out how to import an existing disk into a VM in unraid.

Can this work?

 

VBoxManage clonehd disk.vdi disk.raw --format raw

 

Then

 

qemu-img convert -f raw disk.raw -O qcow2 disk.qcow2

 

What do I do with it after that?

How do I run the qemu comand?

What do I do with it after that?

How do I run the qemu comand?

[*]Run the VBoxManage step with VirtualBox running.

[*]Copy the raw image to your unRAID server where you want the image to be (if it isn't already)

[*]Run QEMU command from unRAID command line

[*]Select the qcow2 image in unRAID GUI.

That's how I interpreted it anyway.

I think the results are the same as last time, but this time I happened to catch an extra message before it went to the shell.

When it starts I see "Boot failed. EFI Misc Device." After that there is a mapping table message and I end up with a shell.

 

Hmm... it looks a bit like this https://forums.virtualbox.org/viewtopic.php?f=1&t=45065

Hooray! I got it working!

That last EFI notice was the clue I needed.

I then went to edit VM and read the tooltip which said the BIOS type couldn't be adjusted on existing VMs.

I recreated the VM, selected the SEABIOS instead of the OVMF and now the VM is running well.

Hooray! I got it working!

That last EFI notice was the clue I needed.

I then went to edit VM and read the tooltip which said the BIOS type couldn't be adjusted on existing VMs.

I recreated the VM, selected the SEABIOS instead of the OVMF and now the VM is running well.

Great 

On 11/28/2016 at 1:32 PM, peter_sm said:

Can this work?

 

VBoxManage clonehd disk.vdi disk.raw --format raw

 

Then

 

qemu-img convert -f raw disk.raw -O qcow2 disk.qcow2

 

 

Just checking in from the future (2022) to let you know these steps still work.  Thanks!

This fix works GREAT in 2022, my old VBox VM's converted over just fine. Don't forget to change the BIOS type to SEABIOS.

So I am actually attempting this at the moment and I am getting some problems. I went into Virtual Box and noticed that you can create a copy of the vdi disk into qed or qcow and went ahead and did that. Now in the unraid gui i changed the type to raw and selected the qcow image that i copied and went through the other normal settings. After doing that the Vm started up and everything , but it was not assigned and ip address and refuses to pull any updates any idea why that would happen or what could be done to fix it?

9 hours ago, Coldfusion said:

it was not assigned and ip address and refuses to pull any updates any idea why that would happen or what could be done to fix it?

drivers missing for virtual network adapter?

I think I do because all my other VMs on un raid has ip address and can do updates and stuff.

I'm talking about a driver in the VM, not in Unraid.

Woops my bad , Ill check that when i retry it tonight

 

So virtual box drivers are up to date and its still giving me the problem.

4 hours ago, Coldfusion said:

So virtual box drivers are up to date and its still giving me the problem.

I thought you were running in KVM / Unraid, not virtualbox?