root@HomeServer:/mnt/cache/.VMs/Windows# xl create windows.cfg
Parsing config from windows.cfg
libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 3 device model: spawn failed (rc=-3)
libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3
libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited

 

my windows.cfg

 

#name of vm
name="windows"

builder="hvm"
device_model_version='qemu-xen-traditional'

#change this to the number of cores you require for the vm
vcpus=4

#change this to the amount of memory for the vm
memory=2048

#change the lines below to specify the virtual disk image used and the cdrom iso to boot from, remove file:/...iso once windows installed
disk = ['file:/mnt/cache/.VMs/Windows/windows.img,hda,w' , 'file:/mnt/cache/.VMs/Windows/Win81.iso,hdc:cdrom,r']

#change the mac to be UNIQUE, MUST start with 00:16:3e IMPORTANT make sure bridge is defined as "br0" in unraid
vif = [ 'type=ioemu,mac=00:16:3e:a1:bc:a5,bridge=br0,model=e1000' ]
netmask = '255.255.255.0'
gateway = '10.0.0.138'
ip = '10.0.0.15'

#boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n).
boot="dc"

acpi = '1'
apic = '1'
viridian = '1'
xen_platform_pci='1'
sdl = '0'

#this is the port number vnc will listen on, a value of 2 means port 5050+2, so port will be 5052 for this vm, must be UNIQUE
vnc = '1'

#listen on all adapters
vnclisten = '10.0.0.15'

vncconsole=1

vncpasswd = '00773211'
usb = '1'

#this is for the mouse pointer
usbdevice = 'tablet'

on_poweroff="destroy"
on_reboot="restart"
on_crash="restart"

 

My File

 

root@HomeServer:/mnt/cache/.VMs/Windows# ls
Win81.iso  windows.cfg  windows.img

That kind of error usually points to a problem with the disk specification but yours looks OK on first glance.

 

A couple of things to try;

 

You have your disk images inside a hidden directory - I've never done that. No reason what it wouldn't work but any reason why you don't put them in a 'domains' directory on cache? Unraid won't move the domains directory and it makes things easy when registering the VMs with unraid.

 

The other thing to try is, temporarily, remove the .iso disk and try to launch. This will help you diagnose if it's the .img or the .iso that might be causing the problem.

 

Apart from that, I'm not sure what else to look at.

 

Peter

...You have your disk images inside a hidden directory - I've never done that. No reason what it wouldn't work but any reason why you don't put them in a 'domains' directory on cache? Unraid won't move the domains directory and it makes things easy when registering the VMs with unraid...

mover doesn't ignore a folder named "domains". It only ignores hidden folders at the top level of cache (the old way of doing things) and it ignores shares (also a folder at the top level) set to cache-only. So if you use a domains share you will have to set it to Use cache disk: Only

 

You can examine the mover script yourself and see that it never mentions "domain"

root@unSERVER:~# which mover
/usr/local/sbin/mover
root@unSERVER:~# cat /usr/local/sbin/mover
#!/bin/bash

# This is the 'mover' script used for moving files from the cache disk to the
# main array.  It is typically invoked via cron.

# After checking if it's valid for this script to run, we check each of the top-level
# directories on the cache disk: if the directory also already exists in the array, then we
# use the 'find' command to process the objects (files and directories) of that directory.
# Note that files at the top level of the cache disk are never copied to the array.

# The script is set up so that hidden directories (i.e., directory names beginning with a '.'
# character) at the topmost level of the cache drive are also not copied to the user share file
# system. This behavior can be turned off by uncommenting the following line:
# shopt -s dotglob

# The 'find' command generates a list of all files and directories on the cache disk.
# For each file, if the file is not "in use" by any process (as detected by 'fuser' command),
# then the file is copied to the array, and upon success, deleted from the cache disk.
# For each directory, if the directory is empty, then the directory is created on the array,
# and upon success, deleted from the cache disk.

# For each file or directory, we use 'rsync' to copy the file or directory to the array.
# We specify the proper options to rsync so that files and directories get copied to the
# array while preserving ownership, permissions, access timess, and extended attributes (this
# is why we use rsync: a simple mv command will not preserve all metadata properly).

# Only run script if cache disk enabled and in use
if [ ! -d /mnt/cache -o ! -d /mnt/user0 ]; then
  exit 0
fi

# If a previous invokation of this script is already running, exit
if [ -f /var/run/mover.pid ]; then
  if ps h `cat /var/run/mover.pid` | grep mover ; then
      echo "mover already running"
      exit 0
  fi
fi
echo $$ >/var/run/mover.pid
echo "mover started"

cd /mnt/cache

for Share in */ ; do
  if [ -d "/mnt/user0/$Share" ]; then
    echo "moving $Share"
    find "./$Share" -depth \( \( -type f ! -exec fuser -s {} \; \) -o \( -type d -empty \) \) -print \
      -exec rsync -i -dIWRpEAXogt --numeric-ids --inplace {} /mnt/user0/ \; -delete
  else
    echo "skipping $Share"
  fi
done

rm /var/run/mover.pid
echo "mover finished"
root@unSERVER:~#

I stand corrected - it's been so long since I set this up, I forgot!

 

You're right, of course, now that I think about it if I look in my shares, I see 'domains' there.

 

Any thoughts on whether the invisible directory might affect xen paths?

I stand corrected - it's been so long since I set this up, I forgot!

 

You're right, of course, now that I think about it if I look in my shares, I see 'domains' there.

 

Any thoughts on whether the invisible directory might affect xen paths?

Probably not, but I never use hidden folders anymore since cache-only shares were introduced in v5. Most things that have any sort of GUI won't show hidden folders.

I tried all kinds of options, and the last is, I still get the same error

 

#name of vm
name="windows"

builder="hvm"
device_model_version='qemu-xen-traditional'

#change this to the number of cores you require for the vm
vcpus=4

#change this to the amount of memory for the vm
memory=2048

#change the lines below to specify the virtual disk image used and the cdrom iso to boot from, remove file:/...iso once windows installed
disk = ['file:/mnt/user/cache_only/Windows/windows.img,hda,w' , 'file:/mnt/user/cache_only/Windows/Win81.iso,hdc:cdrom,r']

#change the mac to be UNIQUE, MUST start with 00:16:3e IMPORTANT make sure bridge is defined as "br0" in unraid
vif = [ 'type=ioemu,mac=00:16:3e:a1:bc:a5,bridge=br0,model=e1000' ]

#boot=[c|d|n] # Selects the emulated virtual device to boot from. Options are hard disk (c), cd-rom (d) or network/PXE (n).
boot="dc"

acpi = '1'
apic = '1'
viridian = '1'
xen_platform_pci='1'
sdl = '0'

#this is the port number vnc will listen on, a value of 2 means port 5050+2, so port will be 5052 for this vm, must be UNIQUE
vnc = '1'

#listen on all adapters
vnclisten = '0.0.0.0'

vncconsole=1

vncpasswd = ''
usb = '1'

#this is for the mouse pointer
usbdevice = 'tablet'

on_poweroff="destroy"
on_reboot="restart"
on_crash="restart"

Try commenting this line like so.

 

# device_model_version='qemu-xen-traditional'

 

It has been deprecated.

 

Gary

Thanks for your help,

 

But as you see, did not help. What could be the problem?

 

root@Abeksis:/mnt/user/Backup/Windows# xl create windows.cfg
Parsing config from windows.cfg
libxl: error: libxl_create.c:478:libxl__domain_make: domain creation fail
libxl: error: libxl_create.c:743:initiate_domain_create: cannot make domain: -3
libxl: error: libxl.c:1384:libxl__destroy_domid: non-existant domain -1
libxl: error: libxl.c:1348:domain_destroy_callback: unable to destroy guest with domid 4294967295
libxl: error: libxl_create.c:1320:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation
root@Abeksis:/mnt/user/Backup/Windows#

Looking at your first and most recent windows.cfg file, there is a difference in your file locations. Double check your actual file locations and this line in your windows.cfg file.

 

disk = ['file:/mnt/user/cache_only/Windows/windows.img,hda,w' , 'file:/mnt/user/cache_only/Windows/Win81.iso,hdc:cdrom,r']

 

Gary

True, I changed to another server and the last file location is correct.

So if your latest location is correct, and that is where your windows.cfg file is located, try this.

 

xl create /mnt/user/cache_only/Windows/windows.cfg

 

Gary

Correct location of the file windows.cfg, I tried the said

 

xl create /mnt/user/Backup/Windows/windows.cfg

 

I get an error

 

root@Abeksis:~# xl create /mnt/user/Backup/Windows/windows.cfg
Parsing config from /mnt/user/Backup/Windows/windows.cfg
libxl: error: libxl_create.c:478:libxl__domain_make: domain creation fail
libxl: error: libxl_create.c:743:initiate_domain_create: cannot make domain: -3
libxl: error: libxl.c:1384:libxl__destroy_domid: non-existant domain -1
libxl: error: libxl.c:1348:domain_destroy_callback: unable to destroy guest with domid 4294967295
libxl: error: libxl_create.c:1320:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation
root@Abeksis:~# cd /mnt/user/Backup/Windows
root@Abeksis:/mnt/user/Backup/Windows# ls
Win81.iso  windows.cfg  windows.img

What's the output of in a telnet session? Want to see if Intel VT-d is working.

 

xl dmesg

 

Gary

root@Abeksis:/mnt/user/Backup/Windows# xl dmesg
Xen 4.4.1
(XEN) Xen version 4.4.1 (root@) (gcc (GCC) 4.8.2) debug=n Wed Oct  8 18:02:05 PDT 2014
(XEN) Latest ChangeSet: 
(XEN) Bootloader: SYSLINUX 4.03 0x4d8ae235 
(XEN) Command line: 
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: none; EDID transfer time: 0 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information:
(XEN)  Found 4 MBR signatures
(XEN)  Found 4 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cff70000 (usable)
(XEN)  00000000cff70000 - 00000000cff7e000 (ACPI data)
(XEN)  00000000cff7e000 - 00000000cffd0000 (ACPI NVS)
(XEN)  00000000cffd0000 - 00000000d0000000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000fff00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000170000000 (usable)
(XEN) ACPI: RSDP 000FAFF0, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT CFF70000, 0040 (r1 A_M_I_ OEMRSDT   4000927 MSFT       97)
(XEN) ACPI: FACP CFF70200, 0084 (r2 A_M_I_ OEMFACP   4000927 MSFT       97)
(XEN) ACPI: DSDT CFF70440, 9737 (r1  A0981 A0981001        1 INTL 20060113)
(XEN) ACPI: FACS CFF7E000, 0040
(XEN) ACPI: APIC CFF70390, 006C (r1 A_M_I_ OEMAPIC   4000927 MSFT       97)
(XEN) ACPI: MCFG CFF70400, 003C (r1 A_M_I_ OEMMCFG   4000927 MSFT       97)
(XEN) ACPI: OEMB CFF7E040, 0089 (r1 A_M_I_ AMI_OEM   4000927 MSFT       97)
(XEN) ACPI: HPET CFF79B80, 0038 (r1 A_M_I_ OEMHPET   4000927 MSFT       97)
(XEN) ACPI: OSFR CFF79BC0, 00B0 (r1 A_M_I_ OEMOSFR   4000927 MSFT       97)
(XEN) ACPI: SSDT CFF7E8D0, 0A7C (r1 DpgPmm    CpuPm       12 INTL 20060113)
(XEN) System RAM: 5119MB (5241916kB)
(XEN) Domain heap initialised
(XEN) Processor #0 7:7 APIC version 20
(XEN) Processor #1 7:7 APIC version 20
(XEN) Processor #2 7:7 APIC version 20
(XEN) Processor #3 7:7 APIC version 20
(XEN) IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2333.109 MHz processor.
(XEN) Initing memory sharing.
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) I/O virtualisation disabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) Brought up 4 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1e2d000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   0000000160000000->0000000164000000 (1223383 pages to be allocated)
(XEN)  Init. ramdisk: 000000016a91b000->000000016ffffe0c
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff81e2d000
(XEN)  Init. ramdisk: ffffffff81e2d000->ffffffff87511e0c
(XEN)  Phys-Mach map: ffffffff87512000->ffffffff87eb2de0
(XEN)  Start info:    ffffffff87eb3000->ffffffff87eb34b4
(XEN)  Page tables:   ffffffff87eb4000->ffffffff87ef7000
(XEN)  Boot stack:    ffffffff87ef7000->ffffffff87ef8000
(XEN)  TOTAL:         ffffffff80000000->ffffffff88000000
(XEN)  ENTRY ADDRESS: ffffffff8189c1f0
(XEN) Dom0 has maximum 4 VCPUs
(XEN) Scrubbing Free RAM: .done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 272kB init memory.
(XEN) hvm.c:543:d0 Attempt to create a HVM guest on a non-VT/AMDV platform.
root@Abeksis:/mnt/user/Backup/Windows# 

This is showing that virtualization is disabled. Enable VT-d in your bios. It is also possible that virtualization support on the MB is not very good.

 

You should see something like this.

 

(XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled

 

Gary

I should modify the changes in the bios?

 

(XEN) Intel VT-d iommu 0 supported page sizes: 4kB.
(XEN) Intel VT-d iommu 1 supported page sizes: 4kB, 2MB, 1GB.
(XEN) Intel VT-d Snoop Control not enabled.
(XEN) Intel VT-d Dom0 DMA Passthrough not enabled.
(XEN) Intel VT-d Queued Invalidation enabled.
(XEN) Intel VT-d Interrupt Remapping enabled.
(XEN) Intel VT-d Shared EPT tables not enabled.
(XEN) I/O virtualisation enabled

Yeah, look for something like Enable Intel VT in the bios settings for your motherboard.

 

Gary

Let me try and I'll be back whit answers

Unfortunately there is no motherboards support virtualization technology (vt-x / amd-v)

I looked at your MB manual. ECS H55H-M. Looks like it does support it. Not sure about your CPU though. Make sure Intel VT is set to Enabled.

 

See my attached pic.

 

Gary

 

As I mentioned, I have two computers / servers first server is the main mb ECS H55H-M, II, ASUS P5QC

 

ASUS P5QC is where I try to install win

Your Asus P5QC shows that it supports virtualization also. See my attached pic. You can check you CPU for virtualization support at this website. http://ark.intel.com

 

Flaky motherboard support can be a problem though and sometimes it just won't work.

 

Gary

 

Here's a picture (taken with the iPhone) to the area you mentioned, there's no Intel VT

Well, that's odd. Maybe it is available as a bios update? I just checked your CPU though and the Q8200 does not have virtualization support. So there isn't much more that can be done on this server. You can check your other one though and maybe that one does.

 

Gary

Too bad .. Maybe in the next version of unrarid windows will be installed directly ..

 

Thank you for your help.