gathering 3 machines in 1


boelle

Recommended Posts

Hi

 

Thanks to linus i discovered unraid.... and it did not take many hours to convince me that it was the way to go, spec given that i only have one pc that are partly used for gaming

 

what i want to melt in to one is:

 

Raspberry Pi Running some datalogging of my utility usage... So here I need something that runs Debian so i can use the same guides etc... (more or less...)

2 Windows 8.1 pc's - the more gamer oriented have 1 GPU the other has 2 in sli config (but not using it

 

First Q... Do i need a GPU card to run the debian? i'm running headless on the pi anyway

Next... for each of the 3 setups i have one harddrive... can i get by with assigning each drive to each of the 3 VM's i need to run? or do i have to split up as the guides says... 1 iso share and then 3 shares for each of the VM's? i do have one offsite drive for backup i could use to store the iso's on until i have things going

 

 

Link to comment

You will not need a dedicated gpu for debian.

The 3 harddrives you have should be used as one array. Then You can assign as much space as you like to each machine as a virtual harddrive.

However it is better to have a cache drive. Preferably ssd (but doesnt have to be) and use that on to store the virtual hd images, as it is quicker than running them off the array.

 

Link to comment

thanks for that... i will give the cahce drive a thought thou my spending limit might prevent it...

 

i have just tested to see which of my current 2 pc's are up for the task... one of them have a simple on/off setting for Virtual and the other have 2... i might have misunderstood something but both cpu's should also be able.... for some reason one of the motherboards are not up to the task and i cant figure if i'm doing something wrong

 

will the 2 diagnostic zip's give any clue? the one ending in _bo is the one that has the all clear... but can the other maybe be able but i have done something wrong?

tower-diagnostics-20151022-1831_tina.zip

tower-diagnostics-20151022-1814_bo.zip

Link to comment

got everything gathered and wanted to start my first VM.. only to be greeted with this error:

 

ternal error: early end of file from monitor: possible problem:

2015-10-24T13:37:56.557351Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T13:37:56.557377Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 12

2015-10-24T13:37:56.557384Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to get group 12

2015-10-24T13:37:56.557394Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T13:37:56.557404Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

last lines in log:

 

Oct 24 06:37:55 Tower kernel: device vnet0 entered promiscuous mode

Oct 24 06:37:55 Tower kernel: virbr0: port 2(vnet0) entered listening state

Oct 24 06:37:55 Tower kernel: virbr0: port 2(vnet0) entered listening state

Oct 24 06:37:56 Tower kernel: vfio_iommu_type1_attach_group: No interrupt remapping support.  Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform

Oct 24 06:37:56 Tower kernel: virbr0: port 2(vnet0) entered disabled state

Oct 24 06:37:56 Tower avahi-daemon[1574]: Withdrawing workstation service for vnet0.

Oct 24 06:37:56 Tower kernel: device vnet0 left promiscuous mode

Oct 24 06:37:56 Tower kernel: virbr0: port 2(vnet0) entered disabled state

 

any clues?

Link to comment

a bit stuck...

 

the info page gives me the all clear... when i start the vm the spinning thingy at the installer rotates 1-2 times and then the whole box is locked up...

 

i noted that if i choose to edit XML for the VM nothing shows up.. not even an empty edit box

 

i have attached a new diagnose zip

 

EDIT: as i have just downloaded unraid i use the latest version.... no plugins etc loaded....

EDIT2: removed vfio_iommu_type1.allow_unsafe_interrupts=1 again so back to a "no edits or mods status"

EDIT3: of course now back at this error:

 

Execution error

 

internal error: early end of file from monitor: possible problem:

2015-10-24T17:23:42.164233Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T17:23:42.164257Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 12

2015-10-24T17:23:42.164264Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 12

2015-10-24T17:23:42.164273Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T17:23:42.164281Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

EDIT4: looks the same if i opt for qemu64 mode

 

Execution error

 

internal error: early end of file from monitor: possible problem:

2015-10-24T17:25:51.761805Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T17:25:51.761832Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 12

2015-10-24T17:25:51.761841Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 12

2015-10-24T17:25:51.761852Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T17:25:51.761862Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

EDIT5: a bit different if i opt for Q35 under machine:

 

Execution error

 

internal error: early end of file from monitor: possible problem:

2015-10-24T17:28:06.861453Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T17:28:06.861479Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 12

2015-10-24T17:28:06.861494Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: vfio: failed to get group 12

2015-10-24T17:28:06.861508Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T17:28:06.861518Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=pcie.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

 

EDIT6... i have hyper-v disabled as i use nvidia gpu's

 

not sure what else info to provide

 

EDIT7: the last bit of the log under the VM says:

 

2015-10-24 17:38:35.091+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0

Domain id=8 is tainted: high-privileges

Domain id=8 is tainted: custom-argv

Domain id=8 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

2015-10-24T17:38:35.737971Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T17:38:35.737999Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 12

2015-10-24T17:38:35.738012Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 12

2015-10-24T17:38:35.738024Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T17:38:35.738034Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

2015-10-24 17:38:35.789+0000: shutting down

tower-diagnostics-20151024-1839.zip

Link to comment

with that enabled and the following settings in VM

 

 

I2gyPI2

 

 

 

i get :

 

Execution error

 

internal error: early end of file from monitor: possible problem:

2015-10-24T23:50:22.503526Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to set iommu for container: Operation not permitted

2015-10-24T23:50:22.503551Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to setup container for group 16

2015-10-24T23:50:22.503559Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16

2015-10-24T23:50:22.503568Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed

2015-10-24T23:50:22.503578Z qemu-system-x86_64: -device vfio-pci,host=04:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device 'vfio-pci' could not be initialized

Link to comment

given its sunday i dont expect anything to happen

 

but are there any extra info i could bring forward that would be a big helper in getting things to run?

 

i can assign keyboards and mouse to my vm's

 

but as soon i assign a physical GPU or the onboard sound it refuses to start..

 

and for games vnc are just a bit to slow in updating and cumbersome as the only extra machine i have is a ras pi

Link to comment

i have come to the same conclusion, now i just need to fix it but have no idea on how..

 

all i know is that the info screen has given the go for hardware pass through

 

and if i add that unsafe interrupts line it can start but then the hole box frezzes up... not only the vm but also unraid

 

 

i guess that since i have uploaded a new dignose zip there is not much else i can bring to the table...

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.