Working out virtualization setup

[Atown]

So I've had three machines running. 

 

1. Sophos Router
2. OpenMediaVault NAS
3. Small machine running minecraft modded servers

 

So I'm trying to push these all into 1 box using a little older but I think sufficient tech. S3000AH motherboard, 8gb ram, XEON 3070, etc.

 

Is it reasonable/possible to run:

 

Proxmox

Eth0

1. Sophos
   1. Eth0 - Bridged -outside
   2. Eth1 - Inside/intranet
2. OpenVaultNas
   1. Eth2
3. Minecraft Server 
   1. Eth? Or maybe install extra NIC?

Just looking for feedback

[Electronics Wizardy]

1. Stay far away form xeon 54xx and older cpus. There hot, slow and missing many features.

 

Id get something like a dell r710 or c2100

 

For nics, you would only need 2. One for wan and one for lan.

 

The router would connect to both. 

 

Eveything else would only connect to the lan one.

 

You don't need a eth2.

[samiscool51]

you adleast 4-cores to run minecraft server without much lag

Sophos and OpenVaultNas, not sure about, just leave them sepereate and upgrade the systems septerelty

if you still want to run them under a Vm make a tree of how it's going to work

e.g

main system
|  | |
|  |  - Minecraft server
|  - Sophos 
- OpenVaultNAS

 

it realy helps to understand how its going to work

loads of people use this trick and it works well

 

 

[Atown]

22 hours ago, Electronics Wizardy said:

1. Stay far away form xeon 54xx and older cpus. There hot, slow and missing many features.

 

Id get something like a dell r710 or c2100

 

For nics, you would only need 2. One for wan and one for lan.

 

The router would connect to both. 

 

Eveything else would only connect to the lan one.

 

You don't need a eth2.

11

Just for future reference moving forward:

 

1. define features?

 

2. I had thought not bridging for the NAS would allow for faster dedicated transfer speeds?

 

 

[Electronics Wizardy]

9 minutes ago, Atown said:

Just for future reference moving forward:

 

1. define features?

 

2. I had thought not bridging for the NAS would allow for faster dedicated transfer speeds?

 

 

1. VT-d if you want to do passtrhough. The older chips also don't worth with hyper-v if you ever want to use that.

 

2. Its like adding a switch, it won't hurt the performance at all.

Even if you give its own nic, it stilll has to go through the virtual switches. The only way to get past this is to give it a pcie nic.

[Atown]

35 minutes ago, Electronics Wizardy said:

1. VT-d if you want to do passtrhough. The older chips also don't worth with hyper-v if you ever want to use that.

 

 

Thanks for this tips. I tried reading through a few websites to learn more. 

 

Does the Motherboard or CPU manage the VT-D in conjunction with the virtual machine? And how far does the passthrough run? Meaning, I'll be trying to do this 100% remotely once I get the proxmox working so the only concerns are the hard drives.

 

Hyper-v was a little confusing because I guess microsoft has like a hyper-v server os? But as far as I understood it, it's a manager that works with assigning the processes/threads with the available resources that sits inside the CPU?

[Electronics Wizardy]

1 hour ago, Atown said:

Thanks for this tips. I tried reading through a few websites to learn more. 

 

Does the Motherboard or CPU manage the VT-D in conjunction with the virtual machine? And how far does the passthrough run? Meaning, I'll be trying to do this 100% remotely once I get the proxmox working so the only concerns are the hard drives.

 

Hyper-v was a little confusing because I guess microsoft has like a hyper-v server os? But as far as I understood it, it's a manager that works with assigning the processes/threads with the available resources that sits inside the CPU?

1. VT-d(or iommu on amd) lets you give a pci device to a vm. You can use it just like any other server, but a video card, network card, or raid card would give given to a the vm. In the vm, the device works just like how it would work on bare metal. So with a gpu, you can install drivers, control fan speed, and overclock it.

 

The host will work just like normal, but it won't use the device given to a vm, so a network card give to a vm won't be usabe in the host, but you can still use the other network ports on a host just fine.

 

2. Hyper-v is microsoft's hypervisor. Its built in to windows server 2008 and newer. There is a free version of windows server that can only be used for hosting vms(hyper-v server) Its the same as proxmox, ovirt, exsi, or xenserver.

 

3. For your Server, id suggest you lookinto buy a a dell c2100. They can be found on ebay for less than 200 dollars, and are much more powerfull than the oldel 5040 xeons you were looking at. They can also hold 12 3.5in drives and 276gb of ram.

 

4. For storage, i personally run the storage server on the bare metal of the system. I have had issues when passing through storage devices, but it can be done.

[samiscool51]

watch this:

this will explain how it works and some of the technical stuff that is required to use it