Summary: | vmware-server fails to run a vm - vmware-vmx causes Oops in vmware modules | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Kelly (RETIRED) <pioto> |
Component: | New packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 137424 | ||
Attachments: | /tmp/emerge-vmware-modules.log |
Description
Mike Kelly (RETIRED)
2006-07-27 22:32:08 UTC
Hi Mike I'm going to need a little more information from you. First off I'd like to know what version of vmware-server you're running, also what version of vmware-modules you're running, and finally, just in case, to check and make sure you're not using JFS. Thanks! Oops, sorry, my vmware-server is 1.0.0.28343 [same for the server-console], and vmware-modules is version 1.0.0.15. And, no, there is no JFS anywhere, just ext3. Ok, thanks for getting back to me Mike. That all sounds fine, could you please attach the emerge output for the vmware-modules just to check there are no unusual errors or warnings during compilation? Basically if you run "emerge --oneshot vmware-modules 2>&1 > /tmp/emerge-vmware-modules.log" and then return the log file created in /tmp, it'll help us rule out any unusual things in the build process of the modules, to see whether they're the cause. Thanks... 5:) Created attachment 92961 [details]
/tmp/emerge-vmware-modules.log
emerge log of vmware-modules
Wow, thanks for the quick response! 5:) Unfortunately, it shows everything's compiling just fine, which leaves me at a bit of a loss as to what could be causing it? The call trace shows some common calls, but nothing that I can find duplicates of relating directly to vmware... If you can provide any other unusual information about your setup (weird hardware, uncommon software settings, grsec applied, etc), they might provide a clue as to the oops. Otherwise, with the kernel being tainted by the vmware modules, the chances are we'll be unlikely to find much help from anywhere... 5:( Just to make sure I'm not being silly, I'll of course suggest the obvious "reboot the machine" and "check that the modules you just compiled are definitely the ones in use" etc, but I imagine you've checked all that already. I'm afraid we're out of my area of expertise, but I'll leave the bug open in case you find a solution or can post any further information about it. Sorry I can't help more... Quick response is thanks to liquidx's pybugz... There isn't anything weird installed that i can think of.. It's a standard dell desktop. I used to have vmware running well on it, too. I've done a total wipe of all vmware stuff, including everything in /etc, and all evidence of the modules and then reinstalled. Machine has been rebooted multiple times, I've upgraded the kernel. Thanks for giving it a shot. Since no one else is getting this, I'll resolve as LATER for now, and take another look at it in a few weeks or so. I've tried it again now, using the latest builds from the overlay (1.0.1.29996), and things work fine. Ok great, I'll mark this bug closed as soon as the new version of vmware goes in the tree, thanks for letting me know! 5:) The latest version (masked) just hit CVS, should be with the rsync servers in an hour or two. It'll stay masked for a few days for testing, and I anticipate unmasking it in the middle of next week. If you discover this issue comes back again, please just reopen the bug. Thanks... 5:) |