Thanks.

 

It seems I can do passthrough to my GPUs but only if I change my i3-3220 to a Xeon of some sort.

 

I think I'll stick with my Slackware build for now...

 

I was in your exact shoes and found an i5 3470 for less than £100 second hand. That's your cheapest route into this passthrough game.

Thanks.

 

It seems I can do passthrough to my GPUs but only if I change my i3-3220 to a Xeon of some sort.

 

I think I'll stick with my Slackware build for now...

 

I was in your exact shoes and found an i5 3470 for less than £100 second hand. That's your cheapest route into this passthrough game.

 

It would have to be an Xeon to maintain ECC.

 

I'm not that concerned really anyway, I'll be ditching this mining malarky once things get warmer.

Hi can you add to the FAQ some answers about RAM and vcpus?  In particular:

 

Ram allocation:

Is it exclusive? As in, if I have 4GB of Ram and 2GB is set for Dom0 does that mean there is only 2GB left for the VM?

Is ram allocation for Dom0 different to that of a VM? for example if 2GB is set for Dom0 is it taken out of the available pool for VMs, but VMs can share the rest of the pool, or is VM Ram allocation exclusive?

If I have 8GB of Ram and 2GB is set for Dom0, and I create a VM that has 6GB is that exclusive or could I create another VM with 2GB?

If RAM is exclusive does it matter if the VM is running or not?

If I only have 2GB of Ram and that is set for Dom0, can I still create a VM?

 

vcpus:

Is hyperthreading taken into account for vcpus, so if I have a quad core with hyperthreading would that be classed as 8 vcpus?

Are vcpus exclusive or can they be shared?

If Dom0 has 2 vcpus, could a VM still have 8 vcpus or could you only set 6 vcpus?

Is Dom0 vcpu allocation handled the same as VM vcpu allocation? (similar to the ram question above)

If vcpus can be shared across VMs and you had 3 VMs 1 with 8 vcpus and the other 2 with 4 cpus, how would this be handled internally?

Hi can you add to the FAQ some answers about RAM and vcpus?  In particular:

 

Ram allocation:

Is it exclusive? As in, if I have 4GB of Ram and 2GB is set for Dom0 does that mean there is only 2GB left for the VM?

Is ram allocation for Dom0 different to that of a VM? for example if 2GB is set for Dom0 is it taken out of the available pool for VMs, but VMs can share the rest of the pool, or is VM Ram allocation exclusive?

If I have 8GB of Ram and 2GB is set for Dom0, and I create a VM that has 6GB is that exclusive or could I create another VM with 2GB?

If RAM is exclusive does it matter if the VM is running or not?

If I only have 2GB of Ram and that is set for Dom0, can I still create a VM?

 

vcpus:

Is hyperthreading taken into account for vcpus, so if I have a quad core with hyperthreading would that be classed as 8 vcpus?

Are vcpus exclusive or can they be shared?

If Dom0 has 2 vcpus, could a VM still have 8 vcpus or could you only set 6 vcpus?

Is Dom0 vcpu allocation handled the same as VM vcpu allocation? (similar to the ram question above)

If vcpus can be shared across VMs and you had 3 VMs 1 with 8 vcpus and the other 2 with 4 cpus, how would this be handled internally?

 

Feel free to make a start on your own answers, I'm really very busy with Uni this week and haven't got the time to do it.

Heh, I have no idea what the answers are, hence asking as I'm sure other Xen newbies are probably wondering as well, I know with OpenVZ you can share all the resources so you could create 2 VMs with 8 cpus each and they would in effect have 50% each, whereas I believe with KVM (which Xen is similar to I think? At least closer to KVM than OpenVZ) setting 1 VM with say 6 cpus would only leave 2 left for another VM (that might not be true, I've never used KVM either, and not sure if hyperthreading is counted there either)

Xen supports time slicing if you over commit vcpus but once ram is allocated that's it.

 

Sent from my Nexus 5 using Tapatalk

 

 

So with the default 2GB for Dom0 if you only have 2GB in the system you can't run any VM's or is Dom0 a special case (I read something about Dom0 ballooning or something, and that you could/should allocate a specific amount to it)?

As a total newb to virtualization, I'm trying to get unRAID setup to run my first VM. This thread is bit too advanced. For example, my first boot up didn't even boot into the Xen/unRaid version. I'm working on figuring that out right now.

So with the default 2GB for Dom0 if you only have 2GB in the system you can't run any VM's or is Dom0 a special case (I read something about Dom0 ballooning or something, and that you could/should allocate a specific amount to it)?

Well with only 2gb of ram in a system you should not be even contemplating running vm at all

 

 

Sent from my SGH-T889 using Tapatalk

 

 

As a total newb to virtualization, I'm trying to get unRAID setup to run my first VM. This thread is bit too advanced. For example, my first boot up didn't even boot into the Xen/unRaid version. I'm working on figuring that out right now.

 

By default UnRAID will boot without the Xen option. If you connect to \\tower\flash from a Windows machine and then go to the syslinux folder you will se a syslinux.cfg file which controls your boot options the default value.

 

This is how your default file looks:

 

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

You will see the menu default option is the non-Xen option. If you want to make it boot into Xen by default then you can change it to:

 

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  menu default  
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

That will ensure that every time you reboot you load the Xen config.

 

Once you've done that you can use IronicBadgers VM and instructions (both text and video) to set up your VM and install common apps:

 

http://lime-technology.com/forum/index.php?topic=31687.0

 

 

Ok, I modified my syslinux.cfg to start with XEN as default.

I changed my Domain-0 to use half my physical memory.

I can't use the second half in it's entirely, anybody know how to find out what the max will be?

Also I installed Windows 8 but my network card is not working how can I fix it?  (I used the example .cfg from the first post)

 

Thanks!

 

EDIT:  Network started working out of nowhere...  huh....  So all I need to know is how much memory to allocate.  I have a total of 8 GB.  I allocated 4192 to Domain-0  (unRAID) how much can I allocate to my Windows 8?

VT-d (or AMD-Vi) is required for device passthrough PERIOD, regardless of the type of VM you are passing it to.

 

Perhaps you were referring to VT-x (or AMD-V)?  VT-x is required for HVM, but has nothing to do with passthrough.  It is not required for PV, nor am I aware of an instance where it's recommended.

 

I have AMD-V, is that the same as AMD-Vi?