unRAID Server Release 6.2.0-beta18 Available


Recommended Posts

Hope that's not in reference to me, bit hard to post an 'os' derived diagnostics when the os won't even load ;)  Just incase it was here's my diagnostics.zip from 6.1.9 which works.

 

As an aside, given that this is the first foray of 6.2 into the wild LimeTech should be investigating all bugs regardless of whether a diagnostic.zip is posted or not - given that it's a paid product I'd expect the devs to be polishing it until it shines.

zeus-diagnostics-20160315-0111.zip

Link to comment
  • Replies 421
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

A note to anyone posting issues with 6.2.

 

If you do not include your diagnostics, your post will probably go unanswered and your issue unresolved.  Describing an issue you are having in a reply on this thread is not sufficient to report a bug.  We need a copy of your system diagnostics after the bug occurred.

 

The diagnostics zip file contains critical information we need to help debug any issues discovered.

 

jonp ---- Why don't you put this into reply #2 of this thread.  Otherwise this post will be lost among all of the other 325 Posts on some twenty-two plus pages in this thread.  ;)

Link to comment

oh sorry didn't even know Unraid had diagnostics, anyways here is the diagnostics did another test same result transfer goes for about 10% then drops to 0 bytes/s and Openelec VM is frozen.

 

Only happens when i transfer from share to share, if i transfer to my computer first then to the share it works.

 

Every time this happens i can't get Unraid to shutdown properly or i don't know how to, the webui stops responding

tower-diagnostics-20160314-1928.zip

Link to comment

Failing to find the flash drive labeled UNRAID, was reported three times, in my case I used the GUI for the update. I suspected the flash drive but chkdsk did not report any errors. Ended up copying the info from the flash drive to a hdd, format the flash, copy the info back on the flash and running the bat file. This seemed to have fixed my issue, did several reboots after that with no problems.

 

Link to comment

Failing to find the flash drive labeled UNRAID, was reported three times, in my case I used the GUI for the update. I suspected the flash drive but chkdsk did not report any errors. Ended up copying the info from the flash drive to a hdd, format the flash, copy the info back on the flash and running the bat file. This seemed to have fixed my issue, did several reboots after that with no problems.

 

I have two of the recommended flash drives, one of which being the sandisk cruzerfit which this install has the guid tied to.  I've taken the files off the drive, formatted with rufus to fat32 with an mbr and label of 'UNRAID' and it still refuses to see the usb drive after the os goes to ram and mount /boot.  I've also tried another usb stick to rule out a dodgy usb drive (although both are 3/4weeks old) and moved the usb stick from the esxi/hypervisor usb port underneath the gfx card to one at the rear, which as a by product saves me from swearing trying to get a finger underneath the gtx970.

 

Anyway, long story short - i've ruled out hardware so unless 6.2 needs a new bios setting or something i've missing in the supermicro bios I'm calling it as a software/kernel issue.

 

Link to comment

Please explain the logic of expanding the number of drives allowed in Trial to 6? I mean, aren't they restricted to 250Gb/ drive already? Who would want dual parity on 4 250 Gb beyond verifying that it 'works" - Is that the only reason? And then if they actually pay $29 they get - TADA - 6 drives?

 

Maybe the 250 Gb limitation was removed? Just thinking I am missing the point... ???  Seems like Pro users made out like a bandit and the rest of us - not so much?

 

There is no 250 GB limit to trial anymore.  The purpose of expanding the trial to include more devices was so folks could test out a wider array configuration before committing to a purchase.  It also made sense to match the number of devices allowed for trial with that of Basic.

 

Pro users definitely got a nice uplift to their license capabilities.  Perhaps upgrading to Pro is in your future?

 

To expand on Jon's reply: there was never a 250GB limit ever imposed on Trial.  We talked about it, actually implemented, but decided against releasing it.

 

Guys - I AGONIZED over deciding whether or not to go PRO...ultimately deciding that I would probably never need that many drives, but I needed more than Basic because it was too friggin' small....you guys just kill me.

 

Not unhappy - I love this system - it gets better and better. Just not feeling like the midrange offering is getting any love.

Link to comment

Please explain the logic of expanding the number of drives allowed in Trial to 6? I mean, aren't they restricted to 250Gb/ drive already? Who would want dual parity on 4 250 Gb beyond verifying that it 'works" - Is that the only reason? And then if they actually pay $29 they get - TADA - 6 drives?

 

Maybe the 250 Gb limitation was removed? Just thinking I am missing the point... ???  Seems like Pro users made out like a bandit and the rest of us - not so much?

 

There is no 250 GB limit to trial anymore.  The purpose of expanding the trial to include more devices was so folks could test out a wider array configuration before committing to a purchase.  It also made sense to match the number of devices allowed for trial with that of Basic.

 

Pro users definitely got a nice uplift to their license capabilities.  Perhaps upgrading to Pro is in your future?

 

To expand on Jon's reply: there was never a 250GB limit ever imposed on Trial.  We talked about it, actually implemented, but decided against releasing it.

 

Guys - I AGONIZED over deciding whether or not to go PRO...ultimately deciding that I would probably never need that many drives, but I needed more than Basic because it was too friggin' small....you guys just kill me.

 

Not unhappy - I love this system - it gets better and better. Just not feeling like the midrange offering is getting any love.

 

Plus and Basic customers just got a huge uplift on their license limits from v5.  Basic started at 4 devices and plus at only 7.  Now it's 6 and 12, which I would say is a pretty big increase given that pricing only went up marginally.  Pro users never received an increase before, so we decided to add that in with 6.2.  In addition, Plus and Basic customers both have access to Active Directory, a feature previously reserved for Pro users only.  It sure feels like we've been taking good care of all of our registration key customers, but I'm sorry you don't feel that way.

Link to comment

Hope that's not in reference to me, bit hard to post an 'os' derived diagnostics when the os won't even load ;)  Just incase it was here's my diagnostics.zip from 6.1.9 which works.

 

As an aside, given that this is the first foray of 6.2 into the wild LimeTech should be investigating all bugs regardless of whether a diagnostic.zip is posted or not - given that it's a paid product I'd expect the devs to be polishing it until it shines.

 

It was in reference to ALL who have failed to include diagnostics on their issue.  When a bug is reported here, if we can't recreate it, the only thing else we have to go off of would be diagnostics from that system, otherwise we literally cannot resolve the issue.  It's really that simple.

 

We continue to polish and improve the product at all time, hence why a 6.2 exists at all in the first place ;-).

 

jonp ---- Why don't you put this into reply #2 of this thread.  Otherwise this post will be lost among all of the other 325 Posts on some twenty-two plus pages in this thread.  ;)

 

I just did ;-).

Link to comment

 

Is there any reason when creating a vdisk for a VM via the GUI that you are limited to raw and qcow2?  Could not any of the other KVM supported types be listed.  For instance I regularly use .vdi files which seem to provide a good compromise between space and performance and allow me to easily interchange the vdisk files with Virtualbox on my desktop PC.

There is also LVM :-)

 

Other vdisk types may be added in the future.  The reality is that just because KVM "supports" something, doesn't mean that it will necessarily work in all configurations.  We certainly don't want to get dragged down a path of supporting various vdisk types for performance and other issues when raw and qcow2 work well enough for most.

although I can understand there might be support issues if you offered alternative formats via the GUI I would be happy if after using Edit XML to set a VM to use a format such as .vdi subsequent use of the Edit option left such a change intact so I could use it for other settings.
Link to comment

All of a sudden starting getting the following in my log file - this happens with any drive that spins down - any idea on what to look for?

 

Mar 13 21:27:04 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:27:04 Tower kernel: mdcmd (74): spindown 8

 

Here is a force spindown command

 

Mar 13 21:40:28 Tower emhttp: Spinning down all drives...
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: shcmd (7072): /usr/sbin/hdparm -y /dev/sdd &> /dev/null
Mar 13 21:40:28 Tower kernel: mdcmd (76): spindown 0
Mar 13 21:40:28 Tower kernel: mdcmd (77): spindown 1
Mar 13 21:40:28 Tower kernel: mdcmd (78): spindown 2
Mar 13 21:40:28 Tower kernel: mdcmd (79): spindown 3
Mar 13 21:40:28 Tower kernel: mdcmd (80): spindown 4
Mar 13 21:40:28 Tower kernel: mdcmd (81): spindown 5
Mar 13 21:40:28 Tower kernel: mdcmd (82): spindown 6
Mar 13 21:40:28 Tower kernel: mdcmd (83): spindown 7
Mar 13 21:40:28 Tower kernel: mdcmd (84): spindown 8
Mar 13 21:40:28 Tower kernel: mdcmd (85): spindown 9
Mar 13 21:40:28 Tower kernel: mdcmd (86): spindown 10
Mar 13 21:40:28 Tower kernel: mdcmd (87): spindown 11
Mar 13 21:40:28 Tower kernel: mdcmd (88): spindown 12
Mar 13 21:40:28 Tower kernel: mdcmd (89): spindown 13
Mar 13 21:40:28 Tower kernel: mdcmd (90): spindown 14
Mar 13 21:40:28 Tower kernel: mdcmd (91): spindown 15
Mar 13 21:40:28 Tower kernel: mdcmd (92): spindown 16
Mar 13 21:40:29 Tower emhttp: shcmd (7073): /usr/sbin/hdparm -y /dev/sdc &> /dev/null

 

Thanks

Myk

 

I am receiving these as well when all disks are spun down

tower-diagnostics-20160314-2320.zip

Link to comment

All of a sudden starting getting the following in my log file - this happens with any drive that spins down - any idea on what to look for?

 

Mar 13 21:27:04 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:27:04 Tower kernel: mdcmd (74): spindown 8

 

Here is a force spindown command

 

Mar 13 21:40:28 Tower emhttp: Spinning down all drives...
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: shcmd (7072): /usr/sbin/hdparm -y /dev/sdd &> /dev/null
Mar 13 21:40:28 Tower kernel: mdcmd (76): spindown 0
Mar 13 21:40:28 Tower kernel: mdcmd (77): spindown 1
Mar 13 21:40:28 Tower kernel: mdcmd (78): spindown 2
Mar 13 21:40:28 Tower kernel: mdcmd (79): spindown 3
Mar 13 21:40:28 Tower kernel: mdcmd (80): spindown 4
Mar 13 21:40:28 Tower kernel: mdcmd (81): spindown 5
Mar 13 21:40:28 Tower kernel: mdcmd (82): spindown 6
Mar 13 21:40:28 Tower kernel: mdcmd (83): spindown 7
Mar 13 21:40:28 Tower kernel: mdcmd (84): spindown 8
Mar 13 21:40:28 Tower kernel: mdcmd (85): spindown 9
Mar 13 21:40:28 Tower kernel: mdcmd (86): spindown 10
Mar 13 21:40:28 Tower kernel: mdcmd (87): spindown 11
Mar 13 21:40:28 Tower kernel: mdcmd (88): spindown 12
Mar 13 21:40:28 Tower kernel: mdcmd (89): spindown 13
Mar 13 21:40:28 Tower kernel: mdcmd (90): spindown 14
Mar 13 21:40:28 Tower kernel: mdcmd (91): spindown 15
Mar 13 21:40:28 Tower kernel: mdcmd (92): spindown 16
Mar 13 21:40:29 Tower emhttp: shcmd (7073): /usr/sbin/hdparm -y /dev/sdc &> /dev/null

 

Thanks

Myk

 

I am receiving these as well when all disks are spun down

 

Same here.. loads of them..

Link to comment
Stubbing and assigning other PCI devices

 

To stub PCI devices so they can be assigned to VMs through the webGui directly, you'll need to follow these steps:

 

Login to your server using the unRAID webGui

Navigate to the Tools -> System Devices page

Locate the PCI device you wish to stub and then copy the vendor and product ID specified in brackets near the end of it's row.  Example (the bolded part highlights the vendor/product ID):

 

I've browsed the whole thread and would like to ask:

 

Do I still need the ACS override enabled with the stubbing option? Without the option I had one big IOMMU group for my GPU/USB/SATA controller, so I enabled the override.

 

Either way: what a great improvement over xml fiddling.  :D I haven't really been able to get my PCIe USB 3.0 and SATA controllers passed through to my main VM.. so this seems like the optimal route!

Link to comment

I was wondering what is the best config for using 3 ssds on 6.2.

 

My machine is splitted in two workstations, so I was using on version 6.18:

Parity: 5tb hd

Drive 1: 5tb hd (general storage)

Drive 2: 256gb ssd (workstation 1 system only)

Drive 3: 256gb ssd (workstation 2 system only)

Cache: 256gb ssd (to speed up overall transfers)

 

Now on the 6.2 appears that system(OS) is cache only by default. So, to have the most efficient use of those ssds, I should assign all 3 to cache?

I bought a license about 2 weeks ago, so I'm very noob in it.

Link to comment

I was wondering what is the best config for using 3 ssds on 6.2.

 

My machine is splitted in two workstations, so I was using on version 6.18:

Parity: 5tb hd

Drive 1: 5tb hd (general storage)

Drive 2: 256gb ssd (workstation 1 system only)

Drive 3: 256gb ssd (workstation 2 system only)

Cache: 256gb ssd (to speed up overall transfers)

 

Now on the 6.2 appears that system(OS) is cache only by default. So, to have the most efficient use of those ssds, I should assign all 3 to cache?

I bought a license about 2 weeks ago, so I'm very noob in it.

Wiki: Do not assign an SSD as a data/parity device

 

3 x 256 in btrfs raid1 gives 384GB

 

btrfs disk usage calculator

Link to comment

I've browsed the whole thread and would like to ask:

 

Do I still need the ACS override enabled with the stubbing option? Without the option I had one big IOMMU group for my GPU/USB/SATA controller, so I enabled the override.

 

Either way: what a great improvement over xml fiddling.  :D I haven't really been able to get my PCIe USB 3.0 and SATA controllers passed through to my main VM.. so this seems like the optimal route!

 

Simple answer is yes.

 

(While I have not upgraded yet, and will wait for you poor suckers to do the testing.. (kidding, calm)  ;) )

If you disable ACS and stub all the other devices in that group (and NOT use them), then you don't need it.

However this has nothing to do with the natural grouping of devices, more for UnRAID to assign the devices that are then stubbed, and "free" to assign.

 

The basics for IOMMU grouping are the same in that:

a) you either pass all devices in the group to one system

b)stub the devices you don't use and don't use them at all.

 

The ACS patch will break them up, where the a/b above will not be an issue.

Link to comment

Ok so no idea if anyone can figure this one out.

 

Ive just had 2 entire system crashes, both boots did not make it to 5 minutes uptime.

 

And as you can image, i am unable to get any diagnostics due to the crash. I know its a full system crash as the unraid gui (actual gui) stops responding, no shh, no telnet, no web gui, i lose everything.

 

I have just done another boot but this time i did not boot up any VM's where as the first 2 times i had my "Jamie" vm booted up. It seems to be staying up now without the vm. That vm has been working for 2 days without issues but crashed the server whilst i was at work earlier today (same issue with nothing responding)

 

I have attached my diagnostic file to see if anyone can figure out what is going wrong as i have no clue

 

Regards,

Jamie

archangel-diagnostics-20160315-1852.zip

Link to comment

If you check your syslog  it mentions this error, I simply googled it..

 

Thanks, i found that part.

 

The scary bit is that the system was not even booted for a second before that entered the log. The boot that generated that log has remained on even now i have started a parity check and my vm is enabled.

 

I'm unsure where that is coming from but it doesn't seem to be the culprit but i will keep that in mind

 

 

Edit (cleaned up):

So i just managed a huge 40 minutes before the system locked up again. This time however it seems i have ssh access.

 

I have told a syslog to save and have told the system to shutdown.

I have attached the syslog but it does not seem to be complete as i am sure the crash was after that

 

I had another system lock-up around 4 minutes after the last log. i was unable to access ssh to do any log reporting at all.

 

I tried to gp back to 6.1.9 which lost my array settings. Upgraded again to the beta which got my array back and i am now trying again :) The joys of computers

syslog.txt

Link to comment

I'm trying to install either Ubuntu or Debian server, can't get past this screen, any advice?

 

Here is the XML:

 

<domain type='kvm'>
  <name>Ubuntu</name>
  <uuid>70152094-9d5e-b809-38b8-e1aa103cd8dc</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/70152094-9d5e-b809-38b8-e1aa103cd8dc_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='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/VM/ubuntu-12.04.5-server-i386.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </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:04:14:96'/>
      <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='0x03' function='0x0'/>
    </memballoon>
  </devices>
</domain>

Screen_Shot_2016-03-15_at_21_09_41.png.74211d69e6948e32478f955932685afe.png

Link to comment

I'm trying to install either Ubuntu or Debian server, can't get past this screen, any advice?

 

Here is the XML:

 

<domain type='kvm'>
  <name>Ubuntu</name>
  <uuid>70152094-9d5e-b809-38b8-e1aa103cd8dc</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/70152094-9d5e-b809-38b8-e1aa103cd8dc_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='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/VM/ubuntu-12.04.5-server-i386.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </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:04:14:96'/>
      <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='0x03' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

I had this issue with windows 10 when my ISO was not properly UEFI supported. Switching my ISO resolved the issue. I'm not sure what to recommend with linux guests

Link to comment

 

I'm trying to install either Ubuntu or Debian server, can't get past this screen, any advice?

 

Here is the XML:

 

<domain type='kvm'>
  <name>Ubuntu</name>
  <uuid>70152094-9d5e-b809-38b8-e1aa103cd8dc</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/70152094-9d5e-b809-38b8-e1aa103cd8dc_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='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/VM/ubuntu-12.04.5-server-i386.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </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:04:14:96'/>
      <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='0x03' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Try SeaBIOS instead of OVMF, under BIOS selection.

Link to comment
Guest
This topic is now closed to further replies.