virtual disk shared in win 7 64

Similar Questions

• Replicate the VMS with FTP and VM with virtual disk shared by: SRM with vSphre replication

  I have a VM and FT is configured on it. Now I can reproduce the virtual machine with SRM with replication of vSphere. I have not configured array based replication. Similarly, I have two DB VMs cluster, but they share a virtual disk between them. Can I replicate these VMs DB with vSphere replication?

  Your valuable contribution is much appreciated.

  I got the answer, for the virtual machine with FT and shared virtual disk replication, to do SRM with array based replication. vSphere replication cannot replicate virtual machine with FT or shared disk.

• How to create disk shared across virtual machines on different hosts

  Hello

  We implement Oracle RAC on two virtual machines, one on each of the two armies for redundancy. For our installation:

  • The two ESXi hosts two SAN access a logical unit number.
  • Two virtual machines on the hosts must have access to a single virtual disk on this LUN (or unit number logic itself) at the same time.

  We tried the following:

  • Creation of a data store associated with the LUN, and then creating a new hard drive on each virtual machine using the same virtual disk on the data store. This operation failed because as soon as a virtual computer runs, the other virtual computer cannot run since the first has a lock on the file from the disk.
  • Creation of a new hard drive on the virtual machine through RDM. This operation failed because only the first virtual machine has this option of disc. Once the ROW has been assigned to the LUN, the other virtual computer cannot create its own RDM for the LUN.

  I'm learning just VMware so I can miss a fundamental method to accomplish this, or perhaps, it is not possible at all. You know a way to create the installer I described?

  Welcome to the community,

  I can not specifically help with the Oracle RAC, however, I would recommend that you take a look at MSCS documentation for how to configure shared disks. There is a difference in the way in which you have installed the VM, for example all VMs on an ESXi host or on different hosts. Please keep in mind that MSCS is a cluster without sharing, which means that only one node at a time has access to a shared virtual disc/RDM.

  André

  PS: I forgot to add the link: http://kb.vmware.com/kb/1004617

• Sharing a virtual disk?

  I am looking for a way to share a virtual disk between two hosts...

  host1 requires read/write access

  host2 requires only read access

  Is it possible without clustering software and without having to back up the disk every time host2 would want to read the new data written by host1?

  Technically would only be possible with Linux (or Unix) where you can choose to mount a read-only file system.

  On Windows, this is not possible, and NTFS is not a distributed file system: have the same drive on both machine (whitout clustering) will be generare a corruption of data (or metadata).

  André

• Machines Windows does not start with 2 virtual disks different on 2 different

  Hello

  With the help of esx.3.5.0 update 3

  I have a problem where if I have a new VM to win 7 or Win 2008 r2 with or without vmtools.

  If I reboot it up to 10 times without having to install anything, whether he'll join the black windows loading screen, then restart and then restart and try to start in safe mode, it still does not start.  the machine rendering it useless.

  The single element only on these virtual machines is as follows.

  Windows machines have 2 different virtual disks 1 on a lun, VMFS (vmfs version 3.21 c:) and a RDM VMFS (d :))

  3 questions

  Is it a problem to have 2 different discs with 2 different stores file types?

  Would this questions we see above?

  Also, I thought that you might not? VMotion/clone? a virtual machine if she drives in 2 different places?

  I tested and I can vmotion live VM with records stored on 2 different LUN.

  Hello.

  With the help of esx.3.5.0 update 3

  I have a problem where if I have a new VM to win 7 or Win 2008 r2 with or without vmtools.

  If I reboot it up to 10 times without having to install anything, whether he'll join the black screen windows loading and then restart and then restart and try to start to > safe mode, it will not even start.  the machine rendering it useless.

  Windows 7 and 2008 R2 are not supported in this version.  5 update brings support for these two operating systems.  Go to U5, maybe it's the solution.

  3 questions

  Is it a problem to have 2 different discs with 2 different stores file types?

  Laughing out loud

  Would this questions we see above?

  It is unlikely.

  Also, I thought that you might not? VMotion/clone? a virtual machine if she drives in 2 different places?

  I tested and I can vmotion live VM with records stored on 2 different LUN.

  VMotion requires shared storage.  Local storage would be a problem if you tried to change hosts.

  also would it be a problem if 1 store was running 3.2.1 vmfs and other store runs 3.31 and a v on each disc is used for the VM 1?

  Lol this is explained in KB 1005325.

  Good luck!

• Virtual disk expansion

  I've added four new hard drives at 8 on my ax100 and configured ' DISK POOL 1, include 11 records. A drive is configured as a hot spare. Then, I have expanded the "Virtual Disk 1' to include all the"POOL1 DISC' again. I was expecting the SAN will appear as a 6 to drive in Win2003. However, it proved that I need to format the 4 additional disks and set up as a new partition. I need a shared 6 to disk, not two separate 4TB and shared 2 TB drives. I plugged a different server in the same San using the switch, but it also shows the SAN as two separate partitions.

  Is there an operation that is not destructive to consolidate all readers, both old and newly added, in a huge partition/drive and see it as such in Win2003? It would be difficult to make two backups one 6 to SAN, destroy the virtual disk, recreate a large drive virtual and end of restoration. Help, please. Thank you.

  
  

• MD3000 cannot change virtual disk ownership / preffered path - ERROR 29

  Current configuration

  PowerVault MD3000 (deleted by the moderator) - attached to two servers PowerEdge R610 using Dell SAS 5/e card in each r610. The R610s act as a host ESX VMWare ESXi 5.5.0

  We have created multiple LUNS on the storage array and noticed that traffice all happening through a RAID controller or another module (and it seems to me not change without prompting when you look at the storage Bay). I turned off a two different virtual machines to try to change the path and had an error with a certain delay - I stuck this error below. I also tried to redistribute virtual disks tab the MDSM software nothing works support.

  By reading, it seems that the LUN should be attributed to a particular raid controller before all I / 0, but I still feel like're missing us something as to why we cannot distribute the traffic properly.

  According to some records for a MD3200 -.

  "If the host has a path of data unique to the MD, the virtual disk storage array.
  must be owned by the controller to which the host is connected.
  That's what we're trying to accomplish. I don't know if the hosts are to be physically detached from the SAN, or if there is a bit of software to fail us.
  Thank you in advance! If I failed to provide all the details, please let me know and I'll try to gather the information.
  Here's the error output:

  OPERATING ENVIRONMENT DATA

  Name of the client system: FLMGMT01
  Client OS: Windows Server 2008 R2

  Application version: 03.35.G6.88
  Storage management of version table: 03.35.G6.88
  Name of storage array: VAB-NAS-01
  Firmware version: 07.35.39.64
  Management class: devmgr.v1035api01.Manager

  **************************************************

  DATA ERROR

  Command sent to the RAID controller module to the location: 0
  Host name: 192.168.19.233
  IP address: 192.168.19.233

  Return code: error 29 - this operation cannot complete because there was a failure of authentication of security on a parameter in the command sent to the RAID controller module.

  Try the operation again. If this message persists, contact your Technical Support representative.
  Operation when the error occurred: PROC_assignVolumeOwnership
  Timestamp: August 25, 2014 16:18:59

  DATA BATTERY

  devmgr.v1035api01.Sam.JAL.ManagementOperationFailedException:
  at devmgr.v1035api01.sam.jal.SYMbolClient.dispatchOperation (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.issueCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommandCommon (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.sendCommand (unknown Source)
  at devmgr.v1035api01.sam.jal.StorageArrayFacade.assignVolumeOwnership (unknown Source)
  at devmgr.v1035api01.sam.configuration.controller.ChangeControllerOwnershipDialogPanel.performCommitAction (unknown Source)
  to devmgr.v1035api01.shared.wizard.DialogPanel$ NotifyBackgroundTaskAdapter.performOp (unknown Source)
  at devmgr.v1035api01.shared.AbstractTaskAdapter.run (unknown Source)

  THREAD DATA

  Thread [reference Manager 10, System]
  Thread [finalizer, 8, System]
  Thread [dispatcher Signal, 9, System]
  Thread [attach auditor, 5, System]
  Thread [Java2D grinder, 10, System]
  Thread [TimerQueue, 5, System]
  Thread [Swing-Shell, 6, System]
  Thread [AWT-closure, 5, main]
  Thread [AWT-Windows, 6, main]
  Thread [EventQueueMonitor-ComponentEvtDispatch, 5, main]
  Thread [Thread-3, 5, main]
  Thread [AWT-EventQueue-0, 6, main]
  Thread [DestroyJavaVM, 5, main]
  Thread [SwingWorker-pool-2-wire-1, 5, main]
  Thread [ChangeDetector, 6, main]
  Thread [PreferenceStoreChangeDetector, 6, main]
  Thread [LogMsgThread, 6, main]
  Thread [Np_Link_Monitor0, 6, main]
  Thread [DMVGarbageCollectorThread, 6, main]
  Thread [RecoveryProfile-27, 6, main]
  Thread [NEA-28, 6, main]
  Thread [RecoveryProfile-30, 6, main]
  Thread [NEA-31, 6, main]
  Thread [Timer 0, 6, main]
  Thread [RecoveryProfile-35, 6, main]
  Thread [NEA-36, 6, main]
  Thread [RecoveryProfile-38, 6, main]
  Thread [NEA-39, 6, main]
  Thread [Timer 1, 6, main]
  Thread [Timer 2, 6, main]
  Thread [Timer-3 6, main]

  
  Thread [RecoveryProfile-48, 6, main]
  Thread [NEA-49, 6, main]
  Thread [Timer-4 6, main]
  Thread [RecoveryProfile-53, 6, main]
  Thread [NEA-54, 6, main]
  Thread [Timer-5 6, main]
  Thread [SwingWorker-pool-2-wire-2, 5, main]
  Thread [RecoveryProfile-69, 6, main]
  Thread [NEA-70, 6, main]
  Thread [Timer-14, 6, main]
  Thread [Timer-91, 6, main]
  Thread [host 2.3, principal of the Image]

  Hello MrRedPants,

  Since you are using a configuration not redundant you will have problems trying to modify the paths between the controllers since the two hosts have only a single connection to the MD3000.  What you could do if possible is to get 2 more SAS cables & connect ports second on the MD to RAID opposite that the host is currently connected to.

  Now, if this isn't an option so that you can make is to have 2 disk groups and assign the virtual disks / LUNS that are connected to each host in their own disk group.  If you go to each host their own groups of disks, then you will need to stop the e/s as you move the Ramdisk to the new group of disks so that you want to discard any data loss.

  Please let us know if you have any other questions.

• Together open disk management and DiskPart will cause hang Virtual Disk Service

  Hello

  The issue I'm having is with the Diskpart tool and the disk management opening at the same time, the disk management GUI flashes 10 + time less than a second and then re-open or another tool will be blocked when connecting to virtual disk service.

  One please confirm, that it is a bug that is not specific to my system, but the operating system? My OS is Win7 SP1.

  Thanks in advance.

  Concerning

  Eric

  I don't seem to have the same problem.  Win 7 x 64 SP1 with updates as of April 12, 2016.

  

• VRTX - Server, fabric, PERC, Virtual Disk - understanding of the FAILURES of components

  I am trying to better understand the inner workings of the VRTX.  Here's my setup to help my question:

  Failover cluster of Hyper-V 2012 with 1 M520 as DC and 3 M620s as host servers with two cards of mezz for fabric B and C.

  Two controllers SPERCS (CSV and witness of the virtual disks controlled by SPERCS 1 and SPERCS 2 as backup/failover)

  I noticed that the SPERCs are each connected to a fabric switch (SPERCS 1--> B Switch fabric) and 2 SPERCS--> C switch fabric.

  What will happen if I pass a fabric failure?  Let's say its B fabric switch, so I have more access to the SPERCS 1 and, therefore, my virtual disks.  Because everything goes well with SPERCS 1, will my failover of virtual disks to SPERCS 2?

  And if anyone knows Hyper-V well enough, say the Mezz B PCIe card fails in one of my M620s, will be VMs on that host failover because they can't reach the CSV more?

  Any thoughts are greatly appreciated!

  Matt K

  Mattkane85,

  With sharing Perc 8 installed and configured for the fault tolerance, then it will work as you said. Perc cards are configured in an active/passive configuration, so when a Perc fails, the other Perc card takes control, which covers the controller. Now with your question, you asked in the case when a switch fails to will it still tipping? It would also be a Yes. With the active support of Multipath, which is necessary with the Fault Tolerant shared Perc 8 configuration, then uses redundant physical components, such as switches, cables and adapters to create logical paths between the server and the storage device. In the event that one of these components fails, Multipathing logic uses the controller replacing so that applications can still access their data.

  You can find more information and details on these configurations here, on page 6.

  Let me know if it helps.

• Machine virtual hard disk (virtual disk) of the upper size limit put into service

  Hi there, so I'm trying to create a hard drive or a virtual disk in a Virtual Machine in order to configure the virtual machine as a file server. The data store is a Promise VTrak M610P and I installed the vtrak as a type of VMFS5 5,46 TB of space (4 2 hard disks to each RAID 5). In the virtual machine, I added a hard drive and selected the store data vtrak and tried to set the provisioned to 5.46 TB size and type thick lazy disposition to zero, but I get an error of DiskCapControl with the range values. I changed the size set in service and 4 TB and he accepted the new hard drive. I can't find anything on the actual limit on the creation of hard disk in a virtual computer.

  
  

  I'm running a server Supermicro X7DAL-E with VMware ESXi 5.5 U2.

  Any ideas would be useful. Thank you.
  

  I forgot I asked a similar question on a different section of the forum (shame on me), but I found a solution. Please see the following post Re: SMB access using esxi host and manage with MS server 2008 storage

  Here's what I wrote on the link above:

  So it turns out that there seems to be something wrong with vClient when you add a hard disk (virtual disk) to a virtual machine of size greater than 4 TB. Article VMware KB: value of range error message when you add more than 4 TB capacity discs in vSphere Client describes this if you encounter this problem, add the hard drive via vSphere CLI, CLI power or vmkfstools. So this seems to be a known issue on vClient. What I ended up doing was using vClient, creation of hard disk, adding to the virtual machine (size of the hard drive is to 5.45) and when I would get the error message on the DiskCapControl out of reach, I would just click OK and then finalize the creation of the hard drive on the virtual machine. Once the process is complete, I selected the virtual machine and noticed that he indeed added a new HDD size 5.45 TB even if he's complained about it. I pulled to the top of the virtual machine with windows server 2008 R2 installed and was able to create a new disk under windows and set it up as a shared drive on the network. Looks like vClient must be updated by VMware and correct this bug, if it's a bug that I think. Thank you for the help vervoort!

• Converter does not have "an error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. »

  Hi all

  I'm having some trouble converting server physical windows using autonomous vConverter 5.5.

  error message:

  "An error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. "

  I have attached the bundle newspapers. Please notify.

  See you soon...

  Your error is:

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] GetManagedDiskName: Get disklib file name as vpxa-nfcssl: / / [a0110-vmgt70-001] WIN-MOVRCVCSITG/WIN-MOVRCVCSITG.vmdk@a0110tesxhyp01.datacenter.telenorservices.com: 902! 2 b 52 87 75 03 03 ff 49-67 2f 3 a 61 76 and 00 cd e1

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 WARNING 'Default'] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Failed to search for host for a0110tesxhyp01.datacenter.telenorservices.com server address: the requested name is valid, but no data of the requested type was found

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

  Check the manual on the required ports.

  HTH

• Replacement of one virtual disk with one another in a virtual machine

  I am running VMware 10 on a host of Win 7 x 64.  I have two Win 7 x 64 VMs that I created on this host.  Each is set up with the SCSI LSI/drivers disc.  Call them A - VM and VM - B.  Each works fine.  I added the virtual disk from VM - A VM - b.  Then, I made the VM - A drive the first boot device to VM - B.  However, VM - B and then a blue screen with Stop error message 0x7B, which usually means a boot disc/driver problem.  Yet once, each virtual computer boots good on its own.  If I did something similar to a physical machine, that it should work fine, so there's something on virtual systems that is at issue here.  It makes no difference if I do the disk from VM - A persistent or not persistent.  Thank you.

  Well, seems the blue screen caused by VM - A disk, maybe you can attached to an another Guest(VM-B) to give it a try.

• Best practices for large virtual disk

  I would add a large virtual disk (16 TB) to use as a backup storage and ideally thin to allow potential available use of, at least initially, a lot of free space.  Headache is the limit of 2 TB for virtual disks in ESXi 5.

  I know that you can extend 2 TB virtual disks in the operating system (win 2008 r2, in this case).  But is it a good idea?  The underlying array is raid 6, so I guess it's safe, but it sounds at least potentially worriesome me on 8 discs.  Not a matter of concern?

  Performance?

  RDM is less flexible and might be impossible (matrix raid is local).

  Anyone have any suggestions on the best practices here?  What would you do?

  I do not recommend the use of the plan span for the file VMDK disks a bad 2 TB and its all parties (several ways that I saw - snapshot problems, corruption etc.)

  Because they are still local drives, you lose flexibility everything that I recommend using RDM.

  A huge ROW for this virtual machine.

  http://blog.davidwarburton.NET/2010/10/25/RDM-mapping-of-local-SATA-storage-for-ESXi/ This departure to configure it.

  As for what I would do, I've done this before and I used RDM, just for 8TB but still.

• understand the average physics to share the virtual disk

  Hello

  I wanted to understand the physical way to share a virtual disk by configuring the scsi controller.

  

  As you can see in the image as an attachment, I chose the option - "physical - virtual disks can be shared between virtual machines on a server any."

  So, I have a scenario and please let me know if the above applies or not?

  I have 2 ESX host. I have created a virtual machine on ESX host1 and now I want the virtual disk of the virtual machine to be shared and eventually used by the virtual machine on the other ESX host2. can I use the option above to satisfy my need?

  Also on a special note, 2 ESX hosts are not on the shared storage. they run with their own local disk.

  Still, I'll be able to do what I want?

  Thanks in advance.

  No storage shared or using the storage equipment. The 2nd esxi host does not see the local storage on the original host.

  Discover will have on the creation of a Cluster of Mirosft see how you can share disks. You can create a cluster in a box on the same host or use of RDM with shared storage to allow multiple vm' hosts aces acros the same storage.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1004617

• Is it possible to reduce a virtual disk in Fusion 3.1.1

  I brought on a Windows XP-based computer by using the tool of migration (Fusion 3.1.1) for the Mac, and it works fine.  However, the XP machine had a 750 GB with only 135 GB disc, and the process still led to a virtual disk of 698 GB (160 GB on the Mac file system).  My Mac has only a 500 GB drive, and although not currently a problem, I wouldn't let the virtual disk to grow without limit.  Thus, using the partition EASYUS tool, I have reduced the size of the XP partition in the virtual machine to 160 GB.  It resulted in my virtual drive, from about 160GB to 220 GB on the Mac.  I then ran the VMware tools on the XP VM to reduce the virtual disk, which went very well and found with the virtual disk, from 220 GB to 240GB on the Mac.  Not exactly what I expected. Are there tools that I can load it on the Mac for this clean?  Seems kind of silly to have a 240 GB housing file a 160 GB XP partition.  The virtual disk is configured as a single file (not the 2 GB strips) and is NOT previously affected.  Any advice?  FWIW, I've already shared to the top of the original machine, so I can't he re-partition, then re - import.

  Thank you

  Kurt

  Starting with the stop of the vm.  .  .

  (1) settings: Add 2nd hard disk of smaller size

  (2) start the virtual machine

  (3) partition disk "nine."

  (4) copy the XP partition and mark it as bootable. Note that your partitioning program must be able to deal with the copy of the partition which is the current boot drive and EASEUS and others handle this very well.

  (5) judgment, does not suspend the

  (6) settings: Remove all the hard drives, but follow the files.

  (7) settings: Add once again this 2nd hard drive of the smallest size, noting that it is now the "Primary Master"

  (8) settings: Add once again the old boot drive, noting that it is now the primary slave

  (9) starting with the smaller hard disk again

  It's not very different than the steps 'real hardware.

  Message has been re-edited by: ChipMcK congratulate EASEUS for their foresight