|
 |  |  |  |  |  |  |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
 |
| |
08-27-2009
| #1 (permalink) |
| | Re: Represent SAN lun in Hyper-v, without exposing i to the host Aristofax wrote: Quote: > I have a problem with represent SAN lun in Hyper-v, without exposing it to > the host system: > > Say I have a 2Tb Lun visible and connected to W2k8 Hyper-V Server. I would > like to divide this > lun within the Hyper-v itself without exposing it to the Host, so that it is > explicit locked to the Hyper-V > instance. I'm not thinking of "passthrough" because as I see, this just > represent the whole disk/lun to > a single Virtual Server. > > The reason why I don't want it to be exposed to the host, is to sealing it > from System control > managing, performance or other automatic integrated system controls.... should just be able to install a physical NIC for each virtual machine that you want to access the SAN, and configure it using the iSCSI initiator from within the virtual machine. I don't see why that wouldn't work since it's just normal TCP/IP traffic, albeit with SCSI commands inside. If your SAN is FibreChannel, then I doubt it's possible since you won't be able to expose the HBA cards directly to the virtual machine. I'd be interested to know if you get it working. -- Chris. |
My System Specs |
|
08-27-2009
| #2 (permalink) |
| | Re: Represent SAN lun in Hyper-v, without exposing i to the host Hi Christ Ok..then that's the reason because I use FC SAN. Do you no if Microsoft in future might offer the same features for FC ?.. R2 maybe ? ...and do we have a problem then using live migration and shared LUN with R2 when we are using FC SAN ? Thanks Chris for answer. "Chris M" wrote: Quote: > Aristofax wrote: Quote: > > I have a problem with represent SAN lun in Hyper-v, without exposing it to > > the host system: > > > > Say I have a 2Tb Lun visible and connected to W2k8 Hyper-V Server. I would > > like to divide this > > lun within the Hyper-v itself without exposing it to the Host, so that it is > > explicit locked to the Hyper-V > > instance. I'm not thinking of "passthrough" because as I see, this just > > represent the whole disk/lun to > > a single Virtual Server. > > > > The reason why I don't want it to be exposed to the host, is to sealing it > > from System control > > managing, performance or other automatic integrated system controls.... > I've never tried it myself, but assuming you're using an iSCSI SAN, you > should just be able to install a physical NIC for each virtual machine > that you want to access the SAN, and configure it using the iSCSI > initiator from within the virtual machine. I don't see why that wouldn't > work since it's just normal TCP/IP traffic, albeit with SCSI commands > inside. > > If your SAN is FibreChannel, then I doubt it's possible since you won't > be able to expose the HBA cards directly to the virtual machine. > > I'd be interested to know if you get it working. > > -- > Chris. > |
| My System Specs |
|
09-01-2009
| #3 (permalink) |
| | Re: Represent SAN lun in Hyper-v, without exposing i to the host Hi I solved it. It seems that I'm able to see the SAN (LUN) through SCVMM and create the vhd directly to LUN visible but not exposed to the host. Thanks again "Chris M" wrote: Quote: > Aristofax wrote: Quote: > > I have a problem with represent SAN lun in Hyper-v, without exposing it to > > the host system: > > > > Say I have a 2Tb Lun visible and connected to W2k8 Hyper-V Server. I would > > like to divide this > > lun within the Hyper-v itself without exposing it to the Host, so that it is > > explicit locked to the Hyper-V > > instance. I'm not thinking of "passthrough" because as I see, this just > > represent the whole disk/lun to > > a single Virtual Server. > > > > The reason why I don't want it to be exposed to the host, is to sealing it > > from System control > > managing, performance or other automatic integrated system controls.... > I've never tried it myself, but assuming you're using an iSCSI SAN, you > should just be able to install a physical NIC for each virtual machine > that you want to access the SAN, and configure it using the iSCSI > initiator from within the virtual machine. I don't see why that wouldn't > work since it's just normal TCP/IP traffic, albeit with SCSI commands > inside. > > If your SAN is FibreChannel, then I doubt it's possible since you won't > be able to expose the HBA cards directly to the virtual machine. > > I'd be interested to know if you get it working. > > -- > Chris. > |
| My System Specs |
|
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Re: Hyper-V Host - Domain or Workgroup? | Virtual Server | |||
| Re: Hyper-V Host - Domain or Workgroup? | Virtual Server | |||
| Hyper-V: Harddisk I/O on host | Virtual Server | |||
| Change Hyper-V Host computer name? | Virtual Server | |||
| My guest machine in hyper-V has conectivity but the host has not. | Virtual Server | |||
