Detail/technical reasons for NAS (CIFS/SMB2 ?) NOT supported for Hyper-V 1.0
the following excerpt in latest (v. 1.2) hyper-v planning , deployment guide (http://www.microsoft.com/downloads/details.aspx?familyid=5da4058e-72cc-4b8d-bbb1-5e16a136ef42&displaylang=en )
implementing disks , storage
this section describes various storage options server running hyper-v supports. discusses how plan storage, how create virtual hard disk, , how configure storage.
you can use following types of physical storage server runs hyper-v:
• direct-attached storage (storage attached management operating system). can use serial advanced technology attachment (sata), external serial advanced technology attachment (esata), parallel advanced technology attachment (pata), serial attached scsi (sas), scsi, usb, , firewire.
• storage area networks (sans). can use internet scsi (iscsi), fibre channel, , sas technologies.
note: network-attached storage (nas) not supported hyper-v.
i have read jose barreto's postings on here , others regarding running vms off cifs (window storage servers) , other nas devices. exact meaning of note: in hyper-v planning , deployment guide?
implementing disks , storage
this section describes various storage options server running hyper-v supports. discusses how plan storage, how create virtual hard disk, , how configure storage.
you can use following types of physical storage server runs hyper-v:
• direct-attached storage (storage attached management operating system). can use serial advanced technology attachment (sata), external serial advanced technology attachment (esata), parallel advanced technology attachment (pata), serial attached scsi (sas), scsi, usb, , firewire.
• storage area networks (sans). can use internet scsi (iscsi), fibre channel, , sas technologies.
note: network-attached storage (nas) not supported hyper-v.
i have read jose barreto's postings on here , others regarding running vms off cifs (window storage servers) , other nas devices. exact meaning of note: in hyper-v planning , deployment guide?
term "it works" not equal term "it supported"
it supported means works @ level (msft in case) confident (the client) not have problems implementation.
yes works. yes it.
however, not support if call.
in case, there must preventing msft form calling supported. maybe have not had resources test thoroughly enough, maybe have seen problems when apply stress (in case heavy disk i/o).
in case "we not support installation if vhd running vm using located on file server (served on network either cifs / smb / nfs)"
all of other storage options mentioned local, high performance disks.
here running vhd network share not solid enough.
brian ehlert (hopefully have found useful)
it supported means works @ level (msft in case) confident (the client) not have problems implementation.
yes works. yes it.
however, not support if call.
in case, there must preventing msft form calling supported. maybe have not had resources test thoroughly enough, maybe have seen problems when apply stress (in case heavy disk i/o).
in case "we not support installation if vhd running vm using located on file server (served on network either cifs / smb / nfs)"
all of other storage options mentioned local, high performance disks.
here running vhd network share not solid enough.
brian ehlert (hopefully have found useful)
Windows Server > Hyper-V
Comments
Post a Comment