You are currently browsing the VDI Ready weblog archives for the day 12. August 2008.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | Sep » | |||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
- Citirx (47)
- event (1)
- General Virtualization (18)
- Green Computing (4)
- Microsoft (5)
- Pandemic (1)
- Products (5)
- Uncategorized (26)
- VDI (68)
- VMware (19)
- XenApp (4)
- Xendesktop (10)
- XENserver (9)
- 13. January 2012: Top 10 Free Citrix support Tools
- 11. January 2012: New VDI interface for Ipad from Citrix
- 10. November 2011: Citrix Acquires ShareFile, The “Dropbox For Enterprises”
- 4. November 2011: VDI Optimizer
- 5. October 2011: Some Old School Citrix tools:
- 7. April 2011: Remember that VDI project that performed well in the lab, but once out in the enterprise, its performance left something to be desired?
- 11. February 2011: The future of Virtual desktops
- 1. February 2011: Terminal Services versus VDI: Brian's presentation from VMworld Europe
- 28. January 2011: Virtual desktops: The Future is Now
- 27. January 2011: Connecting to VM Pool using Windows Server 2008 R2 VDI infrastructure
- January 2012
- November 2011
- October 2011
- April 2011
- February 2011
- January 2011
- October 2010
- September 2010
- August 2010
- July 2010
- May 2010
- April 2010
- January 2010
- December 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
Archive for 12. August 2008
Date/Time Issue With VMware Update 2
12. August 2008 by Tony.
This problem seems to affect both ESX and ESXi.
The problem is that as soon as the date hits August 12, 2008, all VMs refuse to power on and an error is logged indicating that the product’s license has expired. If VMs are already running, they should be fine; the problem, as I understand, only prevents users from powering on new VMs or performing VMotion operations.
If you are being affected by this bug, then your only real option at this point is to disable NTP (if it is being used) and set your date back a couple of days.
There’s no firm word yet on when a fix will be available from VMware.
Rince, thanks for the heads-up!
Update as of 9AM ET August 12, 2008 Updated ISOs and TARs for Update 2 (let’s call them Update 2 v2) will be available by noon PT tomorrow, August 13. In the meantime, the following workaround should help:
- Disable NTPd on the ESX hosts.
- Set the date on the ESX hosts back to some point prior to August 12, 2008. Some people have suggested using the same day and month but a completely different year in the past; this will make it easier to repair ESX log files using search/replace.
- Set the VM to boot into the BIOS.
- Boot the VM. In the BIOS, set the date and time properly. This will be incorrect because it gets inherited from the host. This is independent of the time sync functionality in VMware Tools. If you don’t fix this, VMs will boot up with the wrong date and/or time and that will cause additional problems (like Kerberos authentication within Active Directory).
- After the VM has booted, ensure that time sync within VMware Tools has been disabled. Configure time sync to a reliable source. Active Directory usually handles this for Windows-based systems in a domain.
This workaround is only necessary to power on a VM, resume a suspended VM, or perform a VMotion operation. If all your VMs are currently up and running, just disable DRS/HA.
Hopefully this information will help. I’ll post more information as it becomes available.
According to the VMWare phone support this is being tracked as KB 1006716.
Looks like tomorrow will be a busy day….
From
http://blog.scottlowe.org/2008/08/11/apparent-datetime-issue-with-update-2/
Posted in VMware, General Virtualization | No Comments »