When a snapshot is complete, so I can start to make changes to the virtual machine?

Similar Questions

• can OEM 12 c installed on the virtual machines?

  I checked the oracle about the 12 c OEM documentation and seems doesn't not accurate if we can use the virtual machines or not. But because so many components have to be installed and configured, I would like to know if anyone knows this here.
  
  Thanks in advance.

  Yes OEM12c can be installed on the virtual machines.

  You can also see URL below for more details

  https://Apex.Oracle.com/pls/Apex/f?p=44785:24:0:no:24:P24_CONTENT_ID, P24_PREV_PAGE:6432, 2

• Can I download can imagine them in the data store when the Virtual Machine is running

  or do I have to stop the Virtual Machine first and then download?

  Rgds

  Chris

  If you want to have a consistent state, Yes.

  If you just need a consistent state to the accident, you can create a snapshot, download the base vmdk files and then validate once again the snapshot operation.

  You cannot download files in use (except the read-only).

  André

• Failed to create snapshot - now I can not start the virtual machine.

  Hi guys,.

  I took a snapshot of my VM and got the error:

  Cannot open disk ' / vmfs/volumes/xxxxxxxx.vmdk' or one of the snapshot disks it depends on.

  Reason: Invalid drive string: cannot mix ESX and hosted style discs in the same chain.

  I deleted the snapshot in the Snapshot Manager, but my VM will always start (same error)

  Can anyone help? Its a vanilla install, just 1 VM on it.

  Thanks in advance

  Always pointing the Flash disk VMX configuration file. Whenever you remove the Flash disk, the drive-VMX configuraiton must be updated correctly. In your case it does not somehow. Anyway, lets get a work around.

  1 take the backup of the VMX configuration file

  2. edit the VMX file

  3 scsi0:0.fileName = "QFES_1.2.25 - RHEL52_x86.vmdk" (Please check the VMDK file name correctly it)

  4. save the file

  5. turn on the virtual machine

  Check your luck now

• AutoSave is slow when the virtual machine is not active

  When I actively use a Windows 2000 Server VM and AutoSave is triggered, it's very fast.  But if I did not use the virtual machine for a while, it takes some minutes and minutes.  If I'm trying to go back to the virtual machine, I have to wait indefinitely for the automatic backup complete.

  Is it possible to set the priority for the automatic backup feature?

  Are you talking about VMware Fusion AutoProtect feature, or something else (perhaps in the comments)? Offhand, it seems that when you have not used within a certain time, Fusion got paged out. Taking the automatic snapshot requires paging backward, which can take some time. You can test this theory by looking at activity monitor and looking at the pageout/publication numbers when you see an automatic preview slow.

  Pageouts and pageins are controlled by OS X and not something we have control over. Adding RAM to the Mac, it is more likely merger will stay in memory and avoid this situation.

• SRM 5.5 - vSphere replication - error: impossible to reverse the replication for the Virtual Machine. A snapshot operation cannot be performed

  Hi all, we have just run a test DR failover of a couple of virtual machines in our protected our failover site and all site swung perfectly, two virtual machines came online and all applications work well. However when we cam to r-eprotect machines virtual, we get some errors.

  One of the virtual machines seems to have lived the reprotect end process, it is still running, but has not moved to 89% for some time. The virtual machine has a couple of grand (a little less than 2 TB) VMDK. slow progress is just a consequence of the large VMDK?

  More worrisome is the virtual machine which don't reprotect at all. It generates an error whenever I click on the "Restore" button (error: impossible to reverse the replication for the Virtual Machine.) A snapshot operation can not be performed).

  
  Does anyone have any ideas as to the cause?

  Thanks in advance for any help.

  Andy

  Finally got to the bottom of this. The issue was that reprotect SRM work was trying to dispel any snapshots that were taken on the computer object virtual destination in VMWare, but could not clean snapshots.

  The reason why snapshots would not consolidate was because it was snapshots of temporary VEEAM who in fact any snapshot file listed in the VSAN data store. So when we looked through the browser data store, no snapshot file existed in the virtual computers folder. Trying a manual removal also failed.

  To fix this, we created a snapshot of the virtual machine in the original data center (note is the engine to the bottom of the virtual machine), this effect was to get rid of the 'fade' snapshot that was visible in the Snapshot Manager that VEEAM backup had left behind. Once this had disappeared, the reprotect back to DCA worked perfectly.

• Unable to start the virtual machine and snapshots are missing from snapshot Manager.

  Hello

  I'm new here in the VMWARE communities and I don't know if I'm posting this survey in the right place. I am currently using VMWARE Workstation 9. The issue I'm having is that I can not start my VM. The error that says:

  

  This is an overview of my settings:

  

  When I try to get a snapshot I can go back, I get this snapshot Manager screen:

  

  I checked the files on the directory of the virtual machine. The snapshot files are still there.

  I tried to solve the problem by editing the configuration of virtual machine file to use another vmdk. I got an error saying something about the parent and the child are not synchronized. Sorry I don't have a screenshot of that. I also tried to make a copy of one of the other VMDK and rename it to match with the name of the missing file. That also made me anywhere I tried looking on the net but I get answers to other vmware ESXi and vSphere products. So I don't know if they apply to my current situation.

  At this point, I'm hoping to recover my machine or at least be able to use snapshots. Please notify.

  I think that the restoration was the best way to solve this problem. I actually checked the different files, but it looks like I missed something. In any case, create snapshots with the virtual machine in a state engine is my personal preference. It is not only to save disk space (since there is no need to preserve the current state of memory), but also provides a consistent state. As for the number of snapshots, you're always on the stop side, and if you are not having issue of performace with small changes you make you should be ok. In case there is a performance problem, you may consider to store the computer virtual on an SSD that will certainly help.

  Since the Center of Documentation of VMware Workstation 10

  To the premises of the virtual machines, you can take more than 100 snapshots for each linear process. For shared virtual computers and remote, you can take a maximum of 31 snapshots for each linear process.

  André

  Post edited by: a.p. corrected fault, "SSD" instead of "SD".

• Method to move the virtual machines in the data store temporary so I can rebuild pool recommended NFS

  Our current data store is a mounting NFS on Nexenta (zfs), which has a pool, I need to rebuild (migration of raidz2 to mirror striped for performance). Initially, I was relying on the judgment of all virtual machines, create a new pool, copy (cp - r) of the Nexenta console all virtual machines to the new pool, recreating the pool mirror and then copy (cp - r) all the data back.

  I have seen several discussions on this topic and seems like the simplest method would be to use the feature to "Migrate" so that the virtual machines are not fragmented. However in some of my pre-test when I copy a virtual machine between the basins of the Nexenta console it appears (from the data store Explorer) to initially create the vmdk provisioned and then once completed it copy looks too thin.

  I hope that I can simply copy the Nexenta console, using the option "Migrate" in vCenter on each of my 40 MV looks like it would be * quite * tedious compared to the simple issuance of an order of 'cp - r' and leave all the copies of VMs (1.5 to) during the night and then adding them to each host.

  Does anyone have experience with this? Or maybe a way to generate scripts easily (?) the option "migrate" in vCenter?

  Thank you all!

  You can select multiple VMs in vCenter regularly using CTRL + click or shift + click and both migrate them as long as they have the same storage destination.  You can also schedule it as a task.    Add manually each computer virtual back in hand is not less painful than migrating individually, anyway.

• 'Create a snapshot of the Virtual Machine' suspended the process - how to kill?

  I tried to rename a virtual machine when I received a message from VCenter that "another task is already underway."

  I did some research and found that the virtual machine, I am trying to rename is currently creating a snapshot of the Virtual Machine.  Or - at least the host thinks Yes.

  The snap was initiated by vpxuser about 20:00 in the night a few days - and is still ongoing.  I can't kill him since the VIC when it is directly attached to the host.

  Looking to my data warehouses - I don't see that he actually created the snap, because I see no 0000001 or something like that.   At this point, I don't like, I don't know why he even launched the snap in the first place.

  Is there a way I can kill that process with the help of the console?   It's hosted on vSphere 4.

  Sven

  You have restarted these services on the host computer?

  service mgmt-vmware restart

  restarting the service vmware-vxpa

  • Kyle

• Take a snapshot of a lun SAN: How do I disassemble the virtual machine?

  SAN is FC 9958E Hitachi, ESX 3.5 update 2.

  I try to take a snapshot of a lun (with a virtual machine in this regard) san and must turn off the virtual machine and disassemble the VMFS virtual machine so I can do that there is no I/O will the lun when I take the snapshot.

  How can I (of) a virtual machine of the VMFS without making the other virtual machines running in the same cluster? I know that the VMFS is a system of shared files grouped campaigns, exclusive property of vmware. Does anyone know the command to use?

  If anyone has any info on this subject, it would be great.

  This is the documentation is 1.5 ESX, released in 2002.

  The command no longer exists in recent versions.

  -Matt

  VCP, vExpert, Unix Geek

• Turn off the virtual machine to remove the snapshot?

  I discovered that, even though my Snapshot Manager says that there are no photos, I have several virtual machines with the snapshot files. I tried to create a new snapshot and then remove it, but it does not work. I tried to shut down the VM, and then create a snapshot and remove - that works. What is the difference? Why would it works when the virtual computer is disabled but does not work when the virtual machine is turned on?

  And even if you go to snapmgt you can not delete them?

  Download rvtools tool, there is an instant writer and see if there's trully snaps and might send a screnn for me!

• Crash when the instant withdrawal: State of the virtual machine is 'unknown (invalid) '.

  Hi all

  Currently, I'm in the middle of a nightmare: a few moments I tried to delete a snapshot that has been there for a while on one of my virtual machines. Of course, it can take a loy of time for this kind of operation to achieve, so I waited patiently so that it reaches its end.

  But in the middle of it my host had a kernel panic (I'll have to diagnose this one).

  When I got to new host, the virtual machine was not the webui, try saving it shows the machine as being "unknow (invalid)"...

  I scoured Suur intrenet for a while, but everything I have read until knowledge is quiet frightneging.

  Currently, the directory that stores all the files of the virtual machine is looking as follows:

  drwxrwxrwx 2 root root 4096 12 October 2008 564d583c-363e-0c7a-96e0-cd07d5b1a8e1.vmem.lck

  -rw - 1 root root 2147221504 2 May 20:31 colossus2_2new - f001.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_2new - f002.vmdk

  -rw - 1 root root 1074266112 Jan 11 22:27 colossus2_2new - f003.vmdk

  -rw - 1 root root 528 2 May 20:31 colossus2_2new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f003.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_3new - f004.vmdk

  -rw - 1 root root 2147221504 Jan 11 22:35 colossus2_3new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:35 colossus2_3new - f006.vmdk

  -rw - 1 root root 661 2 May 20:32 colossus2_3new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_4new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:34 colossus2_4new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:35 colossus2_4new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:42 colossus2_4new - f006.vmdk

  -rw - 1 root root 661 2 May 20:35 colossus2_4new.vmdk

  -rw - 1 root root 1868365824 2 May 22:13 colossus2_5new-000001 - s001.vmdk

  -rw - 1 root root 1637482496 2 May 22:13 colossus2_5new-000001 - s002.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s003.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s004.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s005.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s006.vmdk

  -rw - 1 root root 2096824320 2 May 22:13 colossus2_5new-000001 - s007.vmdk

  -rw - 1 root root 554369024 2 May 22:13 colossus2_5new-000001 - s008.vmdk

  -rw - 1 root root 1728839680 2 May 22:13 colossus2_5new-000001 - s009.vmdk

  -rw - 1 root root 2114191360 2 May 22:13 colossus2_5new-000001 - s010.vmdk

  -rw - 1 root root 1659371520 2 May 22:13 colossus2_5new-000001 - s011.vmdk

  -rw - 1 root root 1527775232 2 May 22:13 colossus2_5new-000001 - s012.vmdk

  -rw - 1 root root 1578958848 2 May 22:13 colossus2_5new-000001 - s013.vmdk

  -rw - 1 root root 1611792384 2 May 22:13 colossus2_5new-000001 - s014.vmdk

  -rw - 1 root root 1602945024 2 May 22:13 colossus2_5new-000001 - s015.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s016.vmdk

  -rw - 1 root root 2085617664 2 May 22:13 colossus2_5new-000001 - s017.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s018.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s019.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s020.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s021.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s022.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s023.vmdk

  -rw - 1 root root 132055040 2 May 22:13 colossus2_5new-000001 - s024.vmdk

  -rw - 1 root root 327680 2 May 22:13 colossus2_5new-000001 - s025.vmdk

  -rw - 1 root root 65536 2 May 22:13 colossus2_5new-000001 - s026.vmdk

  -rw - 1 root root 1582 Mar 8 17:53 colossus2_5new - 000001.vmdk

  drwxrwxrwx 3 root root 4096 2 May 22:14 colossus2_5new - 000001.vmdk.lck

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:37 colossus2_5new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:38 colossus2_5new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:39 colossus2_5new - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:41 colossus2_5new - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f007.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f008.vmdk

  -rw - 1 root root 2147221504 2 May 20:43 colossus2_5new - f009.vmdk

  -rw - 1 root root 2147221504 2 May 20:45 colossus2_5new - f010.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f011.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f012.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f013.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f014.vmdk

  -rw - 1 root root 2147221504 2 May 20:48 colossus2_5new - f015.vmdk

  -rw - 1 root root 2147221504 Feb 11 13:19 colossus2_5new - f016.vmdk

  -rw - 1 root root 2147221504 8 Mar 17:17 colossus2_5new - f017.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:02 colossus2_5new - f018.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f019.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f020.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f021.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_5new - f022.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:04 colossus2_5new - f023.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f024.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f025.vmdk

  -rw - 1 root root by 6553600 Jan 11 23:05 colossus2_5new - f026.vmdk

  -rw - 1 root root 1562 2 May 20:35 colossus2_5new.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f007.vmdk

  -rw - 1 root root 1075576832 2 May 20:31 colossus2 - f008.vmdk

  -rw - 1 root root 8684 2 May 20:19 colossus2.nvram

  -rw - 1 root root 714 2 May 20:31 colossus2.vmdk

  -rw - 1 root root 821 2 May 20:31 colossus2.vmsd

  drwxrwxrwx 2 root root 4096 2 May 22:13 colossus2.vmsd.lck

  -rwxr-xr-x 1 root root 2680 may 2 21:35 colossus2.vmx

  -rw - 1 root root 264 Jan 11 22:25 colossus2.vmxf

  -rw - rr 1 root root 98347008 1 October 2008 gparted-live - 0.3.9 - 4.ISO

  -rw - rr 1 root root 1581428 Jan 13 11:53 0.log - vmware

  -rw - rr 1 root root 771239 19 Dec 12:59 vmware - 1.log

  -rw - rr 1 root root 76388 Jan 11 23:21 vmware - 2.log

  -rw - rr 1 root root 10161063 2 May 20:18 vmware.log

  The vmx file contains the following:

  #! / usr/bin/vmware

  . Encoding = 'UTF-8 '.

  config.version = '8 '.

  virtualHW.version = "7".

  floppy0. Present = "FALSE".

  MKS. Enable3D = 'TRUE '.

  pciBridge0.present = 'TRUE '.

  pciBridge4.present = 'TRUE '.

  pciBridge4.virtualDev = "pcieRootPort"

  pciBridge4.functions = '8 '.

  pciBridge5.present = 'TRUE '.

  pciBridge5.virtualDev = "pcieRootPort"

  pciBridge5.functions = '8 '.

  pciBridge6.present = 'TRUE '.

  pciBridge6.virtualDev = "pcieRootPort"

  pciBridge6.functions = '8 '.

  pciBridge7.present = 'TRUE '.

  pciBridge7.virtualDev = "pcieRootPort"

  pciBridge7.functions = '8 '.

  vmci0. Present = 'TRUE '.

  NVRAM = "colossus2.nvram."

  virtualHW.productCompatibility = "hosted".

  FT.secondary0.enabled = 'TRUE '.

  Tools.Upgrade.Policy = "useGlobal".

  powerType.powerOff = 'soft '.

  powerType.powerOn = "hard."

  powerType.suspend = "hard."

  powerType.reset = 'soft '.

  displayName = "colossus2."

  extendedConfigFile = "colossus2.vmxf".

  scsi0. Present = 'TRUE '.

  scsi0.sharedBus = 'none '.

  scsi0.virtualDev = "free".

  memsize = "4096".

  scsi0:0. Present = 'TRUE '.

  scsi0:0. FileName = "colossus2.vmdk".

  IDE1:0. Present = "FALSE".

  IDE1:0. FileName = ' / vmachines/colossus2/gparted-live-0.3.9-4.iso '.

  IDE1:0. DeviceType = "cdrom-image".

  IDE1:0.allowGuestConnectionControl = "FALSE".

  ethernet0. Present = 'TRUE '.

  ethernet0.allowGuestConnectionControl = "FALSE".

  ethernet0. Features = "1".

  ethernet0.wakeOnPcktRcv = "FALSE".

  ethernet0.networkName = "Bridged".

  ethernet0. AddressType = 'generated '.

  guestOS = "rhel3.

  UUID. Location = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  UUID. BIOS = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  VC. UUID = "52 88 6f 19 b2 66 ae 20-28 5 c 6 b 8 b 96 a1 15 6 d.

  scsi0:1.present = 'TRUE '.

  scsi0:1.filename = "colossus2_2new.vmdk".

  scsi0:1.writeThrough = 'TRUE '.

  scsi0:2.present = 'TRUE '.

  scsi0:2.filename = "colossus2_3new.vmdk".

  scsi0:2.writeThrough = 'TRUE '.

  scsi0:3.present = 'TRUE '.

  scsi0:3.filename = "colossus2_4new.vmdk".

  scsi0:3.writeThrough = 'TRUE '.

  scsi0:4.present = 'TRUE '.

  scsi0:4.filename = "colossus2_5new - 000001.vmdk".

  scsi0:4.writeThrough = 'TRUE '.

  IDE1:0.startConnected = 'TRUE '.

  IDE1:0.clientDevice = "FALSE".

  ethernet0.generatedAddress = "00: 0C: 29:b1:a8:e1.

  tools.syncTime = "TRUE".

  scsi0:0. Redo = «»

  scsi0:1.redo = «»

  scsi0:2.redo = «»

  scsi0:3.redo = «»

  scsi0:4.redo = «»

  vmotion.checkpointFBSize = "16777216.

  pciBridge0.pciSlotNumber = "17".

  pciBridge4.pciSlotNumber = "21".

  pciBridge5.pciSlotNumber = "22".

  pciBridge6.pciSlotNumber = "23".

  pciBridge7.pciSlotNumber = "24".

  scsi0.pciSlotNumber = "16".

  ethernet0.pciSlotNumber = "32".

  vmci0.pciSlotNumber = "33".

  ethernet0.generatedAddressOffset = '0 '.

  vmci0.ID = "-709777183".

  sched.mem.pshare.Enable = "FALSE".

  mainMem.useNamedFile = "FALSE".

  MemTrimRate = '0 '.

  MemAllowAutoScaleDown = "FALSE".

  Could someone point me to a solution if there is? I have Saturday night here and I would not spend my Sunday to rebuild the server from scratch and have to explain Monday morning I lost 2 months of work for users little by relying on this virtual machine.

  Thank you very much in advance!

  bugjargal,

  In the past if I had a VM that is displayed as invalid when you try to add it to the inventory, I usually just created a new virtual machine based on the original settings & attached the existing VMDK.  Not sure how that will work with a virtual machine that has snapshots, but can be worth (nothing to lose)?

  Doug.

• When capturing installation - if I saw the virtual machine is it captured as well?

  All right, let's assume that I am ThinApping an application and I'm in the middle of the installation of the main application and a few children and updates applications.

  If something goes wrong, I don't want to start from the beginning.  So after that I installed can the first main application I take a snapshot of the virtual machine?  Well, I know I can, but my question is will be captured by thinapp and packed to the top in the final exe file this snapshot?  Something I want to happen.

  If so, how would I exclude in the build?  If the snapshot is not captured, so it's perfect.

  Snapshots of workstation are stored on the host computer. ThinApp scans the guest and will not see the snapshots of work stations. So you can take snapshots of work when you want, they are included in the package.

• I can't make changes to the settings of Firefox - none of this works

  As usual, when I allow an update firefox Win Desktop, more things gets sacked. God I wish there was an alternative to that shit from ff!

  I can't make changes to the settings of Firefox - none of this works

  It was theme Aeon 7.5 - this is obviously totally redesigned the appearance of the settings options and caused my mouse does not work.

  Thanks for your help - and I'm sorry for the insults.

• I've set up the virtual machine in win 7 Ultimate and put some data. Now when I try to connect it asks password and does not accept any password.

  Default password Machine virtual XP Mode

  I've set up the virtual machine in win 7 Ultimate and put some data. Now when I try to connect it asks password and does not accept any password. Please giveme the default password

  If you're talking about XP Mode the default password is XPMUser.  In general you can not use Windows without a password in Windows Virtual PC that you can with Virtual PC 2007 and before.  XPMUser is used only with the XP Mode virtual machine.  All other virtual machines requires a user created password.  If you have changed the password in XP Mode and forgotten, then you have to start over.

  Windows Virtual PC is based on virtual server rather than VPC and all virtual machines need a password.  If necessary, uninstall the integration features, start the virtual machine and create a password for the admin user.  Restart the virtual machine, and then reinstall the integration features.  You will not be able to access a virtual machine created by the user that has no password, while the integration features are installed.  Once you have everything right, that a virtual machine will not be asked a password if you are the admin user in Windows 7.

  @george1009,.

  Everything got?  :)