Attributing a problem to virtualization can only be substantiated when the problem is resolved and root cause determined. Until then, you can throw around suppositions but have no significant leverage behind your point of view.
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Maybe you should READ the article
In at least one case, the vendor (you know, the people who WROTE THE PROGRAM) said the problem is with virtualization. Here's a thought for you, unless it's too much for your brain to handle: Both products work fine WHEN NOT VIRTUALIZED, and don't work WHEN VIRTUALIZED. Normally, I'm not into ad hominem attacks, but you're a moron. Try reading, then commenting.
You're still weak
A vendor saying that someone else's software (in this case the virtualization platform) is questionable, regardless of how convinced you are of the symptom. Of course, it can't be ruled out, but to blame virtualization before having root cause, you are being irresposible.
NAT issue
One "gotcha" with some operations via Internet and VM's has to do with NAT. If you use a router that serves NAT (DHCP server) and also have the VM set to connect via NAT (on the host), you have 2 layers of NAT and some operations (like ipsec) don't "survive" the double layer. I always use VMWare VM's in bridged mode. I would be curious about some application installs trying to "phone home" during the install.
Under what?
hey Mark....
You are running it "under VMware" -- that's like saying you opened a file "in Microsoft". What product? Workstation? Server? ESX? They're totally different beasts; my humbly submitted two cents is that you don't use the company name and assume people know what product, you use the product name (as you did with the other virtualization product when you spelled out "Parallels Virtuozzo Containers".
Thanks man! Always read your stuff.
Workstation
Thanks -- good point -- it was Workstation but I was under the impression that the hypervisor is identical in all versions of VMware and it is just the HAL that changes. If there are other differences that mean that a VM will run on one VMware product but not on another that would be a really serious issue. If you know of such a problem please let me know.
Yeah, glad to hear it wasn't just me
I have also experienced odd things with virtualization. I have tried to create a VM desktop with VMWare 5.0 Workstation. I found that graphic intensive apps and audio apps tended to not like running in VM land. If you have any other sites, resouces, etc. that address testing VM apps, please post!
Post new comment