Massive VMware Bug Shuts Systems Down
mattmarlowe writes "Imagine if Red Hat released a version of Linux, and after it was deployed, customers noticed that any processes with a start date of today would refuse to run? Well, that's what happened to VMware — a company that wants nearly all server applications running in virtual machines within a matter of years." Supposedly a fix will be available ... in 36 hours.
I don't get license management measures in software that is only going to be used by major corporations.
If someone wants to run virtual machines at home or in a small business, they're likely going to be more than satisfied with VMWare Virtual Server (formerly GSX) and wouldn't even consider the much more complex ESX.
In a major corporation, fear of massive fines and prosecution is enough to stop them from pirating your software. Hardware dongles, software license managers and the like only hurt your paying customers.
I'm a big tall mofo.
any processes with a start date of today would refuse to run? Supposedly a fix will be available... in 36 hours.
Good thing the fix will be available tomorrow, because if it was available today nobody would be able to run the update process
If libertarians are so opposed to effective government, why don't they all move to Somalia?
I stick to virtualbox. I'm not going to pretend I've audited the source code, but if I need to, I can.
Say YES to freedom.
Do you even lift?
These aren't the 'roids you're looking for.
How would this bug even happen? I can't think of any way except for something dealing with time how it would even have a bug.
Taxation is legalized theft, no more, no less.
A workaround is possible Turn off NTP time on the host. And manually (using the VIC) change that date to one week backwards in time. Voila all set to work.
"Never EVER mess with a jumper you don't know about, even if it's labeled 'sex and free beer'." - Dave Haynie
My head hurts reading that article. Who the fuck wrote it? A ten year old mental retard?
It's like ............... this and VM's this VM's that (Yes, notice the spelling?). Ooooh and the cyberwarfare boogeyman! You can't even find this much Hollywood scenario fear mongering from Hollywood themselves. Oh noes! Our entire infrastructure will be killed by evil cyber terrorists because it runs on VMware!
Oh and and lovely parts like 'w/' instead of 'with'. Hey douchebag, this is not SMS, is it so hard to hit another 2 keys on your keyboard? Oh and for the love of $DEITY$, please learn basic HTML and use links so I don't have to copy paste text into the address bar.
As for Slashdot editors, why the fuck did they pick the worse possible article from the Firehose when plenty others look *WAY* more professional?
But the real bug is license enforcement in the first place. Why would you run the risk of making your business depend on the whims of someone else's IP policies and enforcement?
Now, I'm somewhat realistic. I know that there isn't (yet) an adequate replacement for every piece of closed proprietary software out there. But for my own business (admittedly small) I am building with nothing but GPL/BSD/Apache license code. And it is working. I don't trust closed code. Of course my software will have bugs, some of them serious. But I won't have stuff shutting down because of "license" issues. Why do people go quietly into enforced licenses? Why do people accept remote kill switches on their servers? Why doesn't this strike everyone as a crazy thing to do?
I bought VMWare Fusion for my Mac shortly after it was released.
I've rarely seen such buggy commercial software. The VM engine itself is fine, but there are bugs galore in the GUI side of things.
Visit the VMWare Fusion "support" forum and virtually every posting is not asking how to do something, but is reporting a bug of some kind.
I think that VMWare staff ought to spend more time bug testing, and less time checking their stock tickers to see how well the company is doing.
"Temporary Maintenance - Knowledge Base
This section of the VMware website is currently unavailable while we make important user improvements and upgrades to the site. We apologize for any inconvenience this may cause."
I hope it wasn't running on a VM.
VMWare licenses for ESX server cost something like $5k apiece. My company uses VMWare and I don't quite get it. We pay for expensive blade hardware ($8k each for those, not to mention the chasis), then we pay $5k per virtual server. And for what? Adding virtualization overhead to the runtime cost.
Meanwhile, in articles like this, people are showing how to run many applications and different versions within a single container. A single node in the cluster can run any application. There are always busy, keeping the hardware fully utilized. Isn't that the promise of utility computing? Rack up a bunch of cheaper (but not cheap/shoddy) servers and let your cluster go to town.
So, my question is, why are we (as an industry) embracing virtualization when apps written for a smart container (like OSGi) give the same benefits without all the additional co$t and runtime overhead?
Your licence has expired! You're not protected from dangerous internet threats! Renew your licence now and scan your computer...
:U
VM Licence Management wants to squeeze a few more dollars out of you
Knows everything about nothing and nothing about everything.
...Says it all, I think. Perhaps you should reconsider the ramifications of making your business critically dependent on software that contains code specifically design to make it stop working.
Consider this: to a proprietary vendor the only safe failure mode for "license management code" is one where everything stops.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Um, isn't today Patch Tuesday? This could be worse than we thought.
One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
Unless something has changed dramatically, an expired license won't bring down any already deployed VMs. It simply won't allow you to deploy undeployed ones. It doesn't shut down the VMs as the headline makes it sound nor is it a bug in the hypervisor. Yes it's embarrassing that this got out but can we have a less sensationalist headline and summary?
EvilCON - Made Famous by
Virtualbox has USB support...
The Open Source Model gets a leg up again after this nonsense. A client of mine just ported all their VMs and said good bye to VMware. That's 280 VMs by the way. Thank God we had a contingency plan for switching VM providers for a DR exercise a year ago and here we go.
Management is pretty upset and I doubt we will be switching back any time soon to VMWare products after this.
On a side note this scenario did prove one thing:
Having a VM-agnostic storage makes migration easy. We changed a mount point, powered on the alternate VM host and we were off and running just that quick. We lost the ability to do live migrations for now but beyond that is was a good opporunity to see just how important an VM-agnostic disk storage array is. (I'm not the admin of those machines but I believe we are using iSCSI).
On my side though I had about 50 scripts tapping VMWare via PERL but I guess I can start building workarounds now... No more batch submission and dynamic routing for a week or two... The part I hate the most was I had a nice script to take a batch submission and if necessary migrate a utility node to bigger hardware to accomidate the batch... pisses me off but what can I do, thank you Vmware, that aquisition seems to be improving your product as much as when Symantec aquired Ghost Corp!
-=[ Who Is John Galt? ]=-
Bugs happen. What's so sad about this one, is that it's happening in some code that exists for no reason other than to harm their own customers. (Remember: pirates don't run the license-checking code.) If the intent of the code is to make the software fail, and there is a bug in that code that makes the software fail, then this borders more on malware rather than a mere bug, even though it was caused by an 'innocent'? mistake. If I were a VMWare customer, I would be furious.
Nothing gets "Shut Down". You can't power on VMs, use vmotion, or DRS.
But I'll have to wait tomorrow, as I'm on VMWare =(
I would imagine that a fix would be available in less than 24 hours... you know... wait and start your processes tomorrow? Still sucks. I'm glad I didn't bother to keep my stuff completely up-to-date.
PERL:
All of the power of Voodoo with most of the understandibility!
I'm glad that I keep true to the old methods and run a full version behind.
I'm running 3.0.1 just about everywhere and am unaffected by this bug. I work in a prototyping lab and being able to clone and boot up new VMs is a way of life.
No money wasted today =)
-- Dave
up 12 days, 22:30, 2 users, load averages: 993.20, 994.21, 994.56
*makes note to limit user processes...
That is an excellent paper. If you have not read it, please do.
I was thinking about the very problem of trusting your compiler, and the only thing I could come up with is building one from an open assembler. You would need a single (very public) file containing the base executable. This could be small enough that it could be hand disassembled and verified with a hex dump on any system. You would then feed it a table of menmonics and the equivalent instructions, followed by the code for a more powerful compiler. Since all that would be open source, you could build a system that could be verified. (There could be versions of the initial assembler made for different computers, so you could build your base compiler on, say, an Atari 600XL, or a Commodore 64.)
When our name is on the back of your car, we're behind you all the way!
VMware is suggesting setting the system time backwards to work around their license manager problem. That's a desperation move. Not only will it mess up everything from Kerberos to CVS to "make", if you're running certain licensed software, in particular software licensed via FlexLM, that software will stop working. FlexLM will disable your licenses if the clock goes backwards by more than 24 hours. Now your expensive high-end software protected by FlexLM (Rational, Avid, Matlab, National Instruments, ANSYS, Cisco Unity, Clearcase, Nokia network management, etc.) will stop working. Setting the clock forward again may not re-enable it, either; there's tamper detection.
Also, if you have server/client licensing with FlexLM, or multiple license servers, and the clocks disagree significantly, FlexLM gets suspicious and turns licenses off.
Too bad I found out about this bug in the morning before I got to slashdot. Could have saved me some googling
However, it disallows powering on VMs and using VMotion (I guess HA fails too).
And note also that previous ESX versions are NOT affected. My cluster still runs 3.5u1 and doesn't have this problem.
In a major corporation, fear of massive fines and prosecution is enough to stop them from pirating your software.
Sadly, not true in the real world, as my company has discovered on more than one occasion.
Take it w/ or w/o.
I take it you are a natural born whiner-.
Support for USB, iSCSI and RDP (along with USB-over-RDP) are only available in the closed source variants of VirtualBox.
The opensource edition of Virtual Box doesn't have them.
Also the USB support may lock the system when in fast emulation/patching/ring-2 mode, and only works flawlessly when using the slower mode with virtualisation CPU extensions (my brother tried using it to get old USB hardware accessible when moving to Vista 64 but since then he ended up buying newer hardware)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Each time I try adding a usb device virtualbox throws up it's hands and gives me an error.
I had more success when using the CPU virtualization extension (you have to both enable them in VirtualBox's preferences screen and on the virtual machine's properties). But beware this mode is much slower than the original emulation/patching/ring-2 mode.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
If a virtual machine would support something like DirectX or OpenGL so that I could have the kids running their games in a virtual machine (and being able to install them, etc.) I would have them set up with a locked down OS with a virtual system for their games. {...} But I'm sure the technology is getting closer.
Yup. Indeed. /. mentioned recently "VMGL".
The extension is open source but currently only works for X11 OSes at both end.
But as you said, a working acceleration layer is bound to be developed in the near future for Windows too.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
Mission-critical software on licence-driven systems? Houston, whe have a problem! whe ha... *radio noise*
Religion: The greatest weapon of mass destruction of all time
That's why I stuck with Windows 2000, because I expected to see this kind of thing show up in an update to XP. I'm surprised that Microsoft waited until Vista before turning on the full malware-in-the-kernel option.
Combine this with the loss of customer data in "The LinkUp" and the recent announced termination of Yahoo's "Plays-for-Sure" (or is that "Plays-for-Now"?) servers, and it should make everyone think twice about depending on licenses supported by suicide switches and strong DRM.
PS: don't forget to "MIX-BURN-RIP" your iTunes tracks when you buy 'em.
Anyone running a production environment who upgraded to ESX 3.5.0 update 2, released July 25th is impacted by this IF they are firing up new VMs, doing a live migration of a VM etc. If they want to continue to use the services provided by their running VMs however, they will not be affected by this issue. There is a 14-day leeway for running VM processes when a license expires. As VMware are going to release a fix within 36 hours, that's well covered. Planned maintenance may need to be pushed back though for example, which is about the extent of the impact. It's a nasty little issue, the impact of which has been blown out of all proportion by some posters here who prefer to evangelise for Xen, or even for Microsoft.
Bzzzzzt..."AAAAaaaaarrrgh!!!" Thud.
*sigh*
Well, it's for real. I've confirmed it here, and my whole data center is affected.
It's time like this when I wish I hadn't left the Army; at least there, you can shoot back.
This is going to be one hell of a long night. :(
Regards;
I like Mathematica. It's a wonderful tool. But dealing with Wolfram's insane licensing requirements costs our group significant money in wasted staff time and repeat relicensing. Every year we have to update license keys for the FlexLM server.
FlexLM - that should have died with Interleaf long long ago.
I have this not so fresh feeling touting the virtues of VMWare's competition, Hyper-V.
One of the things I did in the place I worked was use Windows Server 2008's Hyper-V instead of ESX for a virtualization platform. Its not production yet, but it likely will be in a couple months, as test VMs get signed off by devs and the brass after stress tests.
One of the bigger fears was the fact that VMWare's licensing could shut off a mission critical VM that physically resides on three boxes that are connected to the same SAN. With Windows Server 2008, should it fall out of licensing, it would gripe at you, and turn the desktop black. Whoopty-do. This doesn't affect production in the slightest.
Windows Server 2008's Hyper-V has the same functionality, allowing a virtual machine to be on a redundant cluster, assuming all the machines in the cluster can see the same SAN volumes. No, it doesn't have the bells and whistles as ESX, and it requires the CPU to have VM support but it works remarkably well.
Ironically, I have a really cheap Dell laptop running Windows Server 2008 and Hyper-V, and it is more than capable of running my Linux stuff at near native speeds.
Hyper-V's cost? Free. When my company did a hardware refresh, Windows Server 2008 was included in the package.
Oh... it runs Linux perfectly. VirtualPC needed to have the "noreplace-paravirt" command line entry, but Hyper-V not just runs RedHat, but runs it without any problems.
Hyper-V's disadvantage? You have to have the hardware support in the motherboard and CPU, and you need Windows Server 2008, which starts at $1000.
I have seen this happen so many times. These commercial software packages that require a license manager are a liability. They are a serious design flaw that makes commercial software less desirable, and opens up one more opportunity for open source software to compete.
ps - Well I'd run ESX over Server, because it's much faster and can do real SMP virtualization. But I'm also willing to dedicate a machine and buy compatible hardware. But most people wouldn't go through the hassle I bet.
“Common sense is not so common.” — Voltaire
I've been weighing up whether to migrate from VMware Server for our limited set of operations and move to ESXi and then ESX. This has made up my mind now. I'd rather wait for the hype of virtualisation to really settle down, use it in a pretty limited capacity and then run more stuff on technology and a host system that gets it right - KVM and Linux. I don't care too much about waiting, because as far as I'm concerned this just isn't acceptable. Many organisations will be brought to their knees by something like this, and over something that is totally unnecessary as well. I could understand pretty much any other issue, but not this. Sorry VMware.
but if I don't know what the hole looks like, I can't carve a peg to fit it
There are some I know who will put their pegs into any hole
Know your pads. One time pad: good for cryptography. Two timing pad: where to take your mistress.
Just run NTP inside the guest Virtual Machines. Also turn off VMware tools time sync in each VM guest under "edit setting" -> "options", etc.
Nothing like CVS or FlexLM will break.
You probably can do this without any downtime. Try vmware-toolbox to change the VMware tools time sync option online.
This is really depressing. The parent is totally wrong - changing the time on the ESX host will _not_ affect the clocks of the guests, provided you go back in time on the host rather than forward.
Yet the parent is modded +5 Informative as I speak, and replies pointing out the wrongness of his statement do not even show up when browsing at the default threshold.
How can you reference Ken Thompson's "Reflections on Trusting Trust" (HTML/non-PDF version) without also mentioning David A. Wheeler's "Countering Trusting Trust" (as found via Bruce Schneier's blog)? So to answer your question:
What if you can't even trust your compiler?
Well so long as I have another set of compilers AND at least one is trustworthy then there is process I can follow to build a compiler I can trust. After spotting differences in the resulting binary I would also need to (ah-ha) examine the source code of the used compilers and find out which one is mis-generating the binary and fix it.
At some point I need to be able to understand binary and read the source of the compiler that generated that binary to ensure that someone else is not jacking me.
Maybe part of the problem is that each vendor implements license management independently. If there were just a handful of license managing vendors (like the big Certificate Authorities) that all agreed to manage licensing in the same way, there would be solid support across many platforms to make it happen and fewer places for an IT manager to call to collect compliance information. Maybe even automated compliance management tools for the IT admin etc.
License management might even be of interest to open source projects (to get uptake stats, embedding information and usage information for example).
Surely someone can think up an open scheme.
Nullius in verba
"The parent is totally wrong - changing the time on the ESX host will _not_ affect the clocks of the guests, provided you go back in time on the host rather than forward."
This depends on configuration and reboot time. See this 25-page paper on how VMware timekeeping works. The default is that when the VMware host OS is booted, it reads the hardware CMOS time of day clock, the host OS keeps time from that point, and the current host time is exported to the client operating systems via the emulated CMOS time of day clock as they boot in virtual machines.
This default behavior can be modified. You can specify offsets between the host clock and the client clocks. You can change the host clock without changing the client clocks. You can run clock synchronization programs in the clients, and these can sync to some external time source. (NNTP tends to get unhappy because the simulated clock it sees isn't running at a constant speed.) VMWare offers client-side synchronization tools for Windows and Linux, and those won't set the client OS clock backwards during operation. During reboot of a VM, though, if the host time was set backwards, the client times will by default be reset on the next boot. It's possible to configure around this and have explicit clock offsets.
But if you just set the host CPU clock back, things are only OK until the next host reboot. Then everything resyncs to the bogus time.
Remember that in the original article, the issue is about host reboots. If the host doesn't reboot, you're OK with VMware licensing. If it does, then the trouble starts.
but...
If you actually know what you are doing, Access is actually a pretty good development platform. It really is what VB should have been all along. Doing it correctly isn't for the faint of heart nor the inexperienced "guy who knows computers in the department" developer though. It's a LOT of work.
The biggest issue is that MS markets it as a database app, not a dev platform.
But there are some caveats to its use.
1. Never bind controls that can be edited to any datasource. Sorry, but you really need to write code to fill them in, check them, then write them to the back end.
2. Never store any data in an MDB file. Always use a real backend server such as MSSQL, Oracle, or even Postgres or MySQL.
3. Once it works, create an MDE file and only run MDEs on clients, never the "source" MDB.
4. You are checking your db schema revision and comparing it to allowed client app revisions, right?
Still, there are newer platforms available, and quite often a web-based app will be easier to build and maintain.
The article also says that he'd recommend disabling DRS because that would remove resource pools, and goes on to say set the sensitivity to 5. What would be the more correct course of action, would be to set your DRS Cluster to Manual, which is indicating no automation, DRS will not place or move VMs.
Yep, absolutely right! I'm constantly frustrated by the "Pronest" software our company uses. We purchased a "floating license" for it, where the client checks in with the license manager on a server to "take" the available license for only as long as it's running on a particular workstation.
Ok in theory, but in practice, a nightmare! I've had PCs that run into all sorts of problems where they can't communicate with the license server, so the app won't start. The "tech support FAQ" just recommends making sure the Crypkey service is running, and to re-register a bunch of .DLL files if it won't start. That only solved the problem for me in ONE instance.
It now looks like the license file itself on the server got damaged somehow, and NONE of the PCs will authorize against it. This is going to be a HUGE hassle, because the makers of this software make you jump through all sorts of hoops to request a new license key - especially for a "floating" network license.
He's talking about the corporate version of Windows, which only requires a license serial number.
Here is an email I just got from VMware
Dear VMware Customers,
Please find the latest update about the product expiration issue. From this point on, weâ(TM)ll provide an update every two hours. Thanks.
Problem:
An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.
Affected Products:
* VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2
* Reports of problems with ESX 3.5 U1 with the following 3.5 Update 2 patch applied.
1. ESX350-200806201-UG
* No other VMware products are affected.
What has been done?
* Product and Web teams pulled the ESX 3.5 Update 2 bits from the download pages last night so no more customers will be able to download the broken build.
* VMware Engineering teams have isolated the cause of the problem and are working around the clock to deliver updated builds and patches for impacted customers.
* A Knowledgebase article has been published (http://kb.vmware.com/kb/1006716), but traffic to the knowledgebase is causing time outs. A new static page has been published at http://www.vmware.com/support/esx35u2_supportalert.html that customers and partners will be able to view.
* The phone system has been updated to advise customers of the problem
* Vmware partners have been notified of the issue.
Workarounds:
1. Do not install ESX 3.5 U2 if it has been downloaded from VMwareâ(TM)s website or elsewhere prior to August 12, 2008.
2. Set the host time to a date prior to August 12, 2008. This workaround has a number of very serious side affects that could impact product environments. Any Virtual Machines that sync time with the ESX host and serve time sensitive applications would be broken. These include, but are not limited to database servers, mail servers, & domain administration systems.
Next Steps:
VMware to notify customers who have downloaded this version and provide an update every two hours.
Resolution:
VMware Engineering has isolated the root cause and is working to produce an express patch for impacted customers today. The target timeframe is 6pm, August 12, 2008 PST.
FAQ:
1. What would this express patch do?
More information will be provided in subsequent communication updates.
2. Will VMware still reissue the upgrade media and patch bundles in the timeframe that has been communicated?
Yes. We still plan to reissue upgrade media by 6pm, August 13 PST (instead of noon, August 13 PST) and all update patch bundles later in the week. We will provide an ETA for the update patch bundles subsequently. NOTE: the "patch bundles" referred to here are for the patches listed above under "Affected Products" and the other bundles released at GA. They are not the same as the express patch which is targeted for 6pm, August 12, 2008 PST as stated above.
3. Why does VMware plan to reissue the upgrade media before the patch bundles? That is a wrong priority call!
This is not a matter of priority. Since we can get done building and testing the upgrade media before the patch bundles, we want to make that available to customers first instead of
Software vendors need to get over it and realize that all this licensing crap does nothing except make things complicated and cause things to break. It does absolutely nothing to prevent piracy, and probably costs them 10 times as more to design and implement that trash than to just allow the product to be pirated.
President/CEO Pacy World http://www.pacyworld.com
What gives me confidence from software is knowing that it will do what I tell it to do without asking for permission from somebody else. I don't expect that from people, but when it comes to software and hardware I'm a control freak that way. Perhaps there's a treatment plan for this.
Engineering in a deliberate "don't work under certain conditions" case is a first order design flaw as evidenced by this article, the Windows Genuine Advantage validator fiasco and the maintenance headaches faced by users of ESRI software among many others. It's hard enough to get rid of those type of issues that are accidentally introduced. There's no way I'd submit to one added deliberately as a "feature". But then I guess I'm lucky not to have to do the jobs those products serve so well.
Help stamp out iliturcy.
Of course, the sales droid said it was the perfect app. We suits couldn't have been duped, could we? No one wants to admit to that, because then IT would have a say over their precious domain.
Then whomever is running your IT department isn't doing their job. Wouldn't you complain to your Telecom folks if your phone randomly dropped calls constantly? In your case, it sounds like IT is, at some level, to blame for the mess. Was IT in on the purchasing process? Did IT do any beta testing? Parallel testing? Who came up with the cost-to-support for the new app?
The GP is also correct. In a wide world a piece of software that becomes popular will be audited, if for no other reason than the government agency adopting it requires it. As soon as it's discovered to be nefarious (which, think about it ... it almost never happens) it will be publicized and everybody will drop it like a hot rock.
I'm not disagreeing with you either. At some point you have to trust others not to jack you. Open fans prefer to push that down to the hardware level as frequently as possible. Sometimes software vendors need to trust you not to jack them too. Like the vendor in this fine article. They should have exercised some trust when considering whether or not to build in a retarded kill switch that might misfire and destroy the (absolutely mandatory for the product) reliability reputation of their brand in the marketplace. Now for six months we have to listen to the "VMWare is dead" flamewar because they couldn't lighten up about their preccciousssss.
Help stamp out iliturcy.
So, slashdot voting time!
Who wins epic fail of the year?
1) GNU (Encryption Bug)
2) VMWare (License Bug)
http://kb.vmware.com/selfservice/dynamickc.do?externalId=1006721&sliceId=1&command=show&forward=nonthreadedKC&kcId=1006721
-Gilson Soares
+1
Michael Jackson, is that you?
--- I am known for the ones who want to find me on the net. Is that a privacy risk or a privilege? One might wonder..
It's Y2K all over again! :-D
The complaint applies to the version of Windows most people have.
A VERY nice feature of Free, Open Source Software is that there are no license hassles.
Another VERY nice feature is that the software is not designed in such a way as to trick the user into paying more. There are 7? versions of Vista: Vista Starter*, Home Basic, Home Premium, Business, Ultimate, and Vista Enterprise. That's 6, but I think there is one more. And they are all not a new operating system, but just a new version of Windows XP.
And, even worse --> Windows XP was a huge, huge hassle for three years, until Service Pack 2 was released.
Uglier still --> --> Then, after only 3 relatively good years, Microsoft announced that it had declared the death of Windows XP!!!
More sheer ugliness: There are operating system files that the operating system won't copy, making backups a big hassle. There is the sloppiness which makes software be self-degrading and very vulnerable to attack, which helps the vendor sell more copies, because people throw away the corrupted computers and buy new ones, therefore paying for a new copy of the operating system. Another abuse: Microsoft drones attended OSCON, trying to infiltrate the Open Source Convention to sell things that require payment in more than money, in acceptance of abuse, also. There is making new versions that require far more powerful hardware, so that customers will require new computers, making it more profitable for hardware vendors, who then accept that they are being abused in other ways.
It's when you catalog ALL the abuses of commercial software vendors that it become obvious that it is good to avoid them if at all possible. Not all of Microsoft's abuses are cataloged here, of course.
(*Note from Microsoft: Windows Vista Starter is not currently scheduled to be available in the United States, Canada, the European Union, Australia, New Zealand, or other high income markets as defined by the World Bank.)
Go to the VMWare infrastructure client and set the system date to 8/1/08. Make sure you disable NTP at the same time!
"The complaint applies to the version of Windows most people have."
That's nice but not what we are talking about.
Regardless of the accuracy the rest of your post is offtopic fanboi ranting and thus I won't respond to it.
I find being offended by me offensive.
This drives me nuts with every non-Free piece of software I administer. Software breaks often enough, thank you very much, because it is inherently complex. But software with a license server is "designed to break." A license server is just a hair trigger that breaks your software whenever anything isn't "just right."
Do you work for Microsoft?
I mean how about
$ make EXPIRE=`date $BOMBDATE` world
and
#ifdef EXPIRE // don't do stuff
#endif
and for non-beta builds you omit the parameter? Talk about fscking idiots on the part of the programmers and build masters to NOT have something this simple implemented.
I've found that apps that employ license management are by far more likely to fail than those that don't and most of the failures are due to the license management screwing up.
Of course, that's to be expected when software is actually designed so that the default state is failure.
It's really offensive to have software accusing me of being a thief when, in fact, it is the thief (that is, I paid my money and now it refuses to provide the functionality. It won't work again until it has stolen my time). Whatever genius included license management should be made available to receive a punch (a natural consequence of making unfounded vile accusations) in the nose from each and every person inconvenienced by being called a thief.
It might just make the people who will be ripping their hair out supporting this crap feel a bit better.