February 19, 201412 yr hehe, im not telling alright alright i'll tell, not EXACTLY sure which issue it was but its either your mac address is in caps (not sure if its case sensitive?):- yours vif = [ 'mac=00:16:3E:51:20:4C,bridge=br0' ] mine vif = [ 'mac=00:16:3e:01:01:03,bridge=br0' ] or the other difference was the spacing between the value and the equals sign, and the fact your using ' instead of " for the values:- yours on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' mine on_poweroff="destroy" on_reboot="restart" on_crash="destroy" thats the only differences ive noticed so far, maybe hidden CR's as well in your cfg file perhaps edit - noticed quite a few more subtle differences actually, for instance you have specified vcpu and memory with single quotes around the values, mine have no quotes, there are some others as well but i will let you trawl it. my cfg file is taken from schoolbusdrivers excellent post, just adapted it slightly so i cant take all the credit http://lime-technology.com/forum/index.php?topic=31674.msg287853#msg287853
February 19, 201412 yr Great, great. I used either nano or the integrated editor in mc so that should not have been the issue. But I see the differences now. And you are also right related to the mac address; all other cfg files are written in small letters. However the network issue is hindering me on installing Windows. Here's an overview of the network related part of my cfg files: ArchVM vif = [ 'mac=00:16:3e:xx:xx:xx,bridge=br0' ] Debcloud: vif = [ 'mac=00:16:3e:a1:bc:a4,bridge=br0' ] Windows: vif = [ 'mac=00:16:3e:01:01:03,bridge=br0' ] My router typically assigns IP addresses via the mac address and it doing it well for the other two VM's...
February 19, 201412 yr hmm odd, i can only think your router doesnt like the mac address, try shutting down the windows vm, then edit the cfg file with nano and change the mac address to something like this:- vif = [ 'mac=00:16:3e:a1:bc:a5,bridge=br0' ] this is taken from your debcloud vm thats running, just changed the a4 to a5, save it and then start the vm and see what happens. btw i have checked the mac address i supplied and i it does look valid, so perhaps a firmware update on your router might be in order at some point
February 19, 201412 yr Thanks a lot bin hex - changed according to your guidance, but failed for the time being. No errors, but no success either I will give it another try over the weekend when I'm back - leavin now for the rest of the day. Thanks a again.
February 20, 201412 yr Anyone know what is wrong with this line? vif = [ 'mac=00:16:3e:00:20:a3,bridge=xenbr0' ] If I comment it out, the vm boots, if not, I get the similar error to others. libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 43 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited
February 20, 201412 yr I can't see much difference to mine but was struggling myself. Do you have defined xembr0 or br0? Gesendet von meinem V370 mit Tapatalk
February 20, 201412 yr xenbr0 I even have an arch VM that works just fine with vif = [ 'mac=00:16:3e:00:00:01,bridge=xenbr0' ] so, for the sake of comparing: vif = [ 'mac=00:16:3e:00:00:01,bridge=xenbr0' ] - Arch GOOD vif = [ 'mac=00:16:3e:00:00:03,bridge=xenbr0' ] - win 7 BAD
February 20, 201412 yr See my post #52, similar issue. ArchVM and Debian are getting IP, Windows not. Gesendet von meinem V370 mit Tapatalk
February 20, 201412 yr Hmm what about specifying the model of the nic in the cfg? Maybe windows is more picky vif = [ 'mac=00:16:5e:02:07:45, bridge=xenbr0, model=e1000' ]
February 20, 201412 yr For those "not getting an IP" for their windows VM using the configs above, there's a key concept missing: Windows is a relatively backward operating system that is unaware of fancy things like "a network" during initial stages of installation. The folks in redmond believe that all humans like fancy graphics to look at on a big monitor locally connected to some very hot hardware. Hence "Windows" is not really running with a network interface quite yet - just the windows installer - which 'out of the box' is NOT loading any sort of network driver - at least initially. Therefore there will be no new IP on your network until you install a network driver in Windows. What you really want to do is add "vncconsole=1" to your config file and then connect to the VNC console at the DomU's IP (Unraid). If the vncdisplay directive is absent in the config, this will be at port 5900. What you should then see is the lovely windows installer patiently waiting for input.
February 20, 201412 yr I don't ever get that far. Instead, my vm crashes on creation. It gets nowhere near the installer. For whatever reason mine does not like the vif= line. If I Comment it out it starts, but that does me No good. Even if I install windows without a Nic, when I add one after, my system will never boot to use it. This instead seems to be something with the configuration file, but who knows what. Otherwise it is a Xen issue. I guess if nobody knows, I always have the arch forum to turn to. edit: Here is something telling. If I use xm create instead of xl, it points right at my vif line... arch_1 /etc/xen # xm create win7.cfg Using config file "./win7.cfg". Error: Errors were found at line 10 while processing ./win7.cfg: vif = [ 'mac=00:16:3e:04:e0:a3,bridge=xenbr0' ]
February 21, 201412 yr Smakovits I think it's CR issue attach cfg file with txt extension, or download the excellent dos2unix utility and run it over your file, thats all i can think of, as that mac looks fine to me. alternatively, download the cfg file i attached a few posts up and edit the disk lines with nano (leave mac for the time being) and then give it a whirl, if it works then its either some strange setting in your cfg file or CR's
February 21, 201412 yr Are you running this with unraid host or arch as host? Sent from my Nexus 5 using Tapatalk
February 21, 201412 yr Are you running this with unraid host or arch as host? Sent from my Nexus 5 using Tapatalk Arch as host. Its from the times all this talk started, when v6 was still vaporware. I haven't ventured to v6 yet.
February 21, 201412 yr Are you running this with unraid host or arch as host? Sent from my Nexus 5 using Tapatalk Arch as host. Its from the times all this talk started, when v6 was still vaporware. I haven't ventured to v6 yet. Ah, this maybe isn't the right sub forum for you then. Take a look under the general non unraid host stuff. The best resource I know for windows virtualisation on Arch is.... my blog! *Subtle self-promotion spoiler* Do feel free to create your own thread in the right place where I'll try help.
February 21, 201412 yr Sure thing. Just came across similar errors so I thought to pile on. As a side note before moving threads, I did copy your config from your blog, removed the disk info and I got the same error. So, who knows what it is doing. I will look for this other forum and post there. What forum did you want me to go to? Technically none here seem to fit meaning to leave and go to Arch support, but I was really hoping to keep this discussion here. Just want to be sure I move to the right place, but nothing really fits.
February 21, 201412 yr Don't seem to figure it out -rw-rw-rw- 1 root root 1137 Feb 22 00:11 windows.cfg -rw-rw-rw- 1 root root 107374182400 Feb 21 23:42 windows.img -rw-rw-rw- 1 nobody users 5449775104 Jan 5 11:19 windows.iso xl create windows.cfg Parsing config from windows.cfg WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware libxl: error: libxl_create.c:416:libxl__domain_make: domain creation fail libxl: error: libxl_create.c:644:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1379:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1343:domain_destroy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1209:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation and my config: #name of vm name="windows" kernel = 'hvmloader' builder="hvm" #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/Xen/Windows8/windows.img,hda,w' , 'file:/mnt/cache/Xen/Windows8/windows.iso,hdc:cdrom,r'] #change the mac to be UNIQUE, MUST start with 00:16:3e IMPORTANT make sure bridge is defined as "xenbr0" in unraid vif = [ 'mac=00:16:3e:01:01:23,bridge=br0' ] #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' vncpasswd = '' usb = '1' #this is for the mouse pointer usbdevice = 'tablet' on_poweroff="destroy" on_reboot="restart" on_crash="destroy" Any ideea? Thank you!
February 22, 201412 yr As I have already said elsewhere, you don't need both builder and kernel options... Here is my win.cfg from my Arch box for my Windows VM which I know works because I'm writing you this on it! Obviously, amend as needed. builder = 'hvm' vcpus = '4' memory = '8192' device_model_version="qemu-xen-traditional" disk = [ 'phy:/dev/vgSSD/lvWin,hda,w', 'phy:/dev/vgWD/lvWinData,hdb,w', # 'file:/net/unraid/mnt/user/Media/Software/Windows/Windows8/8.1/windows8_1.iso,hdc:cdrom,r' ] name = 'windows' vif = [ 'type=ioemu,mac=00:16:3E:51:20:4C,bridge=br0,model=e1000' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' boot = 'cd' acpi = '1' apic = '1' viridian = '1' xen_platform_pci='1' sdl = '0' vnc = '1' vnclisten = '0.0.0.0' vncpasswd = '' stdvga = '0' usb = '1' usbdevice = 'tablet' pci = ['01:00.0','01:00.1','00:1d.0']
February 22, 201412 yr Ok, I managed to get things resolved. The fix is super complicated.... Lots of difficult steps. Had to issue the following command on dom0 Reboot I know, way complicated, eh? Keep in mind in this case arch is my dom0, not unraid. I ended up searching around on the arch forum, took the search to the basics "libxl", came across a guy with a different issue and the fix was suggested if they did updates to the kernel. Well, be it as it may, I did several pacman - Syyu since deployment, going from the December iso to January, etc via upgrades and while I have rebooted along the way, I know I have done updates without a reboot as well. So, long story short, I needed a reboot. If I can find the post, I will link it. I can now boot normal with NIC as we all figured should be possible given the correct setting. What a pain, since the system doesn't say reboot, I didn't think I needed to. Windows always tells me when it needs to. So yeah, lots of pain for nothing. One thing that did happen, is upon reboot, my pfsense system was inaccessible, so the Internet was down. I connected with vnc and it had IPs and everything so it seemed to be good. Regardless, I needed to reboot it and then I was good, could it be something with my config file, the way the reboot was handled from the dom0 to my domu pfsense system? Regardless it too is back up again. So, I will try to find the post from arch bbs and also post my pfsense config to see if that's why when the dom0 rebooted, my domu pfsense didn't come up right. Might try to reproduce to confirm that's what could be causing it as opposed to some one off occurrence.
February 22, 201412 yr As I have already said elsewhere, you don't need both builder and kernel options... Here is my win.cfg from my Arch box for my Windows VM which I know works because I'm writing you this on it! Obviously, amend as needed. builder = 'hvm' vcpus = '4' memory = '8192' device_model_version="qemu-xen-traditional" disk = [ 'phy:/dev/vgSSD/lvWin,hda,w', 'phy:/dev/vgWD/lvWinData,hdb,w', # 'file:/net/unraid/mnt/user/Media/Software/Windows/Windows8/8.1/windows8_1.iso,hdc:cdrom,r' ] name = 'windows' vif = [ 'type=ioemu,mac=00:16:3E:51:20:4C,bridge=br0,model=e1000' ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' boot = 'cd' acpi = '1' apic = '1' viridian = '1' xen_platform_pci='1' sdl = '0' vnc = '1' vnclisten = '0.0.0.0' vncpasswd = '' stdvga = '0' usb = '1' usbdevice = 'tablet' pci = ['01:00.0','01:00.1','00:1d.0'] Same error regardless of the config
February 22, 201412 yr Errr ironicbadger you got the builder option in your cfg :-) you sure it's not required?
Archived
This topic is now archived and is closed to further replies.