Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

OpenElec 5 VM

Featured Replies

I'm trying to build an OpenElec 5 VM, but I can't get it to boot.  It appears to be having trouble mounting the System drive.

 

I've followed the manual install from a Live Ubuntu CD from here: http://wiki.openelec.tv/index.php/Live_Boot_%26_Manual_Installation

 

DEFAULT linux
PROMPT 0
LABEL linux
KERNEL /KERNEL
APPEND boot=LABEL=System disk=LABEL=Storage quiet ssh

 

Basically, the APPEND boot=LABEL=System command is not working.  I also tried changing it to /dev/### but the few options I tried for that didn't work.  I think it's having issues with drivers for the virtio qcow2 drive.  Any tips?

  • Author

Not sure this is the best way, but it is a driver issue. I changed the qcow2 image to a raw file, and was then able to get OpenElec to boot to its start up cli stuff.  Won't go into OpenElec due to no vid card.  I'll have to continue this tonight when I have access to the monitor it'll be connected to.

  • Author

I've got OpenElec booted, but it's not recognizing the virtual NIC.  Will I have to either passthrough a dedicated NIC or recompile OpenElec to include the driver?  I've never compiled before, and there don't appear to be any thorough instructions so I'm hesitant to go that route.

 

Tips would be greatly appreciated!

  • Author

Was very sluggish and had some weird audio ticks/pops.  I think I'm going to wait for the unVM.

I've got OpenElec booted, but it's not recognizing the virtual NIC.  Will I have to either passthrough a dedicated NIC or recompile OpenElec to include the driver?  I've never compiled before, and there don't appear to be any thorough instructions so I'm hesitant to go that route.

 

Tips would be greatly appreciated!

 

What ended up making it boot?

Was very sluggish and had some weird audio ticks/pops.  I think I'm going to wait for the unVM.

 

That's a shame. I was hoping it would work for you.

But... I'm sure they'll be able to tell us more about this later, soon.

  • Author

I needed the vm HD image to be in raw format, and I attached it as a sata bus instead of virtio.  This is because Openelec doesn't have virtio drivers installed.  Then I had to do a manual install from a live ubuntu iso, since there's no iso file for Openelec.  Afterwards, I heard someone made a vmdk from the OpenElec img file and attached it as another hard drive in order to perform an install.  Would've been much easier and probably would have worked, but that wasn't the route I went.

 

That got it to boot, but then there was no NIC detected, as that needed virtio drivers as well.  I then did physical passthrough of a physical NIC, and I was up and operational except for the sluggishness and ticks and everything.  Here's my XML.

 

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>OpenElec</name>
  <uuid>8c998f9d-0d03-2cbc-5a33-c77fd685c1af</uuid>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <os>
    <type arch='x86_64' machine='pc-q35-2.1'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='yes'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/snapvms/vm/OpenElec/OpenElec5.qcow2'/>
      <target dev='hda' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/iso/ubuntu-14.04.1-desktop-amd64 (1).iso'/>
      <target dev='hdc' bus='sata'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/>
    </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'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:f1:2b:97'/>
      <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>
    <input type='tablet' bus='usb'/>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x046d'/>
        <product id='0xc52b'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x045e'/>
        <product id='0x006d'/>
      </source>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0cf3'/>
        <product id='0x3002'/>
      </source>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=02:00.1,bus=pcie.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=04:00.0'/>
  </qemu:commandline>
</domain>

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.