Tracker item #3297924, was opened at 2011-05-05 06:49 Message generated for change (Comment added) made by mvanzin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3297924&group_id=204462
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Timo Gurr (tgurr) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong "Guest OS" information in vSphere client displayed Initial Comment: The guest is configured as "Other 2.6x Linux (64-bit)", attached screenshot (vmware-tools_stopped.png). # uname -a Linux wwwproxy 2.6.38.5 #2 SMP Wed May 4 12:33:49 CEST 2011 x86_64 Six-Core AMD Opteron(tm) Processor 2425 HE AuthenticAMD GNU/Linux After starting open-vm-tools-2011.04.25-402641 the information in vCenter changes to "Other (32-bit)", attached screenshot (vmware-tools_started.png) which is obviously wrong. VMware vSphere vCenter Client/Server is Version 4.1.0 Build 345043. ---------------------------------------------------------------------- >Comment By: Marcelo Vanzin (mvanzin) Date: 2011-07-22 07:45 Message: Gentoo and many "Other" distros will probably show as their original configured OS. There's no point in adding every single distro out there to our UI, when only a few of them require tweaks at the hypervisor level. (I'd argue that the current list is already too long, but that's a separate discusssion.) As for the Fedora problem; unless you add some log statements to GuestInfoGather() in services/plugins/guestInfo/guestInfoServer.c (after the call to Hostinfo_GetOSName()), there's not much I can figure out from logs or anything else, because we don't log the raw data anywhere. "osName" and "osNameFull" are the strings provided to the UI to identify the OS. ---------------------------------------------------------------------- Comment By: Greg Emerick (gemerick) Date: 2011-07-22 07:00 Message: I tried hardcoding lsb_release to return "Fedora release 8 (Werewolf)" and my image is still 32 bit. I've been looking at the code where lsb_release is called and it would seem that uname is also involved. Although command line uname appears to return very similar information as what I found online for FC 8. I sure don't see any issues with it. ---------------------------------------------------------------------- Comment By: Timo Gurr (tgurr) Date: 2011-07-22 05:02 Message: So what's the deal on Gentoo or (m)any other "Other" Linux distributions? # lsb_release -sd "Gentoo Base System release 2.0.3" Issue on the open virtual machine tools side, or time to open a vmware bug? ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-07-21 11:44 Message: I just tried with Fedora 8 (which has a very similar output of "lsb_release -sd") and the code seems to detect Fedora correctly. I'll close this as an issue with the vCenter / VI client code (they may be missing the mapping to show Fedora correctly), but I shouldn't worry much because this is mostly a cosmetic issue. ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-07-21 10:56 Message: In general, the OS would be reported as "Other (32-bit)" if the code completely failed to recognize that output. The interesting bit is that we do have a check for Fedora in the code, and it should recognize that output. I'll need to try it out to see what's going on. As for what if affects, there are a couple of vCenter features that will look at that value and decide whether they'll run against the VM or not. But I think those features do not support Fedora anyway, so you should be safe. In your case it's probably just a cosmetic thing. ---------------------------------------------------------------------- Comment By: Greg Emerick (gemerick) Date: 2011-07-20 18:21 Message: lsb_release -sd returns: "Fedora release 9 (Sulphur)" I can see where that would get me Other (32-bit). Could you give me some idea of what tools are looking for in the response to indicate 64 bit? If I have to, I'll make this return what's necessary, since it's not used by our appliance for any other purpose. Also, would there be any side-effects to just allowing this to happen? The vmx file is still set to Other (64 bit). ---------------------------------------------------------------------- Comment By: Marcelo Vanzin (mvanzin) Date: 2011-07-20 16:36 Message: Tools will generally use the output of "lsb_release -sd" to figure out the OS information. Fedora 9 should have that; what's the output of that command in your VM? If lsb_release is not available, then that's probably the cause. ---------------------------------------------------------------------- Comment By: Greg Emerick (gemerick) Date: 2011-07-18 19:44 Message: I'm seeing this on Fedora 9 as well with open-vm-tools-2011.06.27-437995. Anything I can provide to assist? vSphere 4.1.0 Build 260247 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=989708&aid=3297924&group_id=204462 ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
