physical drives in Guest OS, "Hot-Swap assignment"
Posted: 30. Jun 2011, 05:40
Okay, I'm just going to copy-pasta from my other topic on a competing virtual systems developer.
This is currently a hypothetical question until every detail can be ironed out.We already have the hard-ware, we just need the software to follow suite. Will VirtualBox allow me to run anywhere from 1 to 10 guest operating systems (all identical), while also being able to have independent physical SATA ports assigned to them?
I'm building a server that has many hot-swap bays. These bays will be used heavily, and each drive being moved will not be similar in any way. I need a virtual machine that can be "assigned" one of the bays--and whatever drive goes in that bay will be accessed by the VM. The virtual machine itself does not need to be hot-swap capable, but when the VM is turned on, it has to automatically recongized and have read\write access to the drive in that bay if one is present.
What I'm essentially doing is creating a computer to run offline virus scans on a variety of different hard-drives. I have six hot-swap bays, and want to rn six VMs. Is there a way to tell VM-1 to always recognize the drive in Bay-1 without exhaustive set-up? Is there a way to automate the process via batch? Because these will be running scans on the drive, I may not be able to shut-down the virtual machine manager each time, as three other VMs may be running when I boot-up VM4, etc. Will VirtualBox do this for me?
I'm not worried about the Virtual Machine necessarily being able to recognize the hot-swap, but just being able to "assign" whatever bay that is to a particular machine. So any drive that goes in that bay will be recognized by the VM next time it starts up. The Host is the only thing that can't be shut-down, which is why I went with a hot-swap system. But I want to be able to pluy a drive into bay 3, let's say, and then start up VM-3. When VM-3 finally boots to OS, it'll have read\write access to whatever drive is plugged into bay-3, without having to go through any arudous set-up process beforehand. If I need to go through aforementioned setup process, is there a way to automate it via batch? In this case, the host's only purpose is to run the virtual machine manager. It has no other purpose, so I'm not fantastically worried about using the the drives in raw mode with the VMs, I just need them to do what I want them to do.
This is currently a hypothetical question until every detail can be ironed out.We already have the hard-ware, we just need the software to follow suite. Will VirtualBox allow me to run anywhere from 1 to 10 guest operating systems (all identical), while also being able to have independent physical SATA ports assigned to them?
I'm building a server that has many hot-swap bays. These bays will be used heavily, and each drive being moved will not be similar in any way. I need a virtual machine that can be "assigned" one of the bays--and whatever drive goes in that bay will be accessed by the VM. The virtual machine itself does not need to be hot-swap capable, but when the VM is turned on, it has to automatically recongized and have read\write access to the drive in that bay if one is present.
What I'm essentially doing is creating a computer to run offline virus scans on a variety of different hard-drives. I have six hot-swap bays, and want to rn six VMs. Is there a way to tell VM-1 to always recognize the drive in Bay-1 without exhaustive set-up? Is there a way to automate the process via batch? Because these will be running scans on the drive, I may not be able to shut-down the virtual machine manager each time, as three other VMs may be running when I boot-up VM4, etc. Will VirtualBox do this for me?
I'm not worried about the Virtual Machine necessarily being able to recognize the hot-swap, but just being able to "assign" whatever bay that is to a particular machine. So any drive that goes in that bay will be recognized by the VM next time it starts up. The Host is the only thing that can't be shut-down, which is why I went with a hot-swap system. But I want to be able to pluy a drive into bay 3, let's say, and then start up VM-3. When VM-3 finally boots to OS, it'll have read\write access to whatever drive is plugged into bay-3, without having to go through any arudous set-up process beforehand. If I need to go through aforementioned setup process, is there a way to automate it via batch? In this case, the host's only purpose is to run the virtual machine manager. It has no other purpose, so I'm not fantastically worried about using the the drives in raw mode with the VMs, I just need them to do what I want them to do.