Of course I did. Not only is this "vmware 101", but vmware 4x builds will tell you what to do if you don't (at least it will according to the vmware site). I will say that it would appear to be an AMD-related issue since I am running an Athlon XP myself. Although I would have to admit, despite the numerous times such processor-specific problems have been reported, this would be the first time I've ever run into any specific issues regarding AMD vs. Intel, I still believe/hope that it would be something more configuration-specific that could be edited/fixed. Otherwise I will have to return to dual-booting for this project which wouldn't make me very happy. :(Hello,
When you installed a new kernel did you do a vmware-config.pl ? This allows the appropriate modules for the vmnet to be compiled and installed against the appropriate kernel.
Make sure that you have the kernel sources and headers installed via the rpms. This is important. I have had it work with my VMWare on 2.6.8.1 !
Cheers,
Aly.
Robert Locke wrote:
On Mon, 2004-09-27 at 11:07, Craig wrote:
Jean-Marie Verdun wrote:
Hi,
I am willing to use VmWare Workstation as a development platform on my R3140US laptop ( AMD64 ). I am facing right now an issue with the 2.6.8.1 kernel ( 64 bits ) which I just have updated on my Fedora Core 2/
I am running the demo version of vmware which was running fine with 2.6.5 kernel.
So, the vmnet bridge between vmnet0 and eth0 seems to be broken.
Does any body have soon meet this issue ? Is there a fix somewhere available for the kernel or from VmWare. There software is very good and I am willing to acquire it ....
Jm
I can only add my voice to yours in knowing that you're not alone. I have encountered the same problem and it exists with both the 2.6.8 and 2.6.7 kernels I have tried. There response is that they are having software interaction troubles with fc2 because the kernel is too new (read bleeding edge). That was from a call on Friday to see how I liked the demo. Have not gotten around to contacting support yet (that is what I intend to do today).
Craig
Craig,
I have VMWare Workstation 4.5.2 Build 8848 (stock, no vmupdates) running just fine on FC2, updated to the latest kernel (2.6.8-1.521). The reason I did not jump in on the earlier post, is that mine is on a Pentium M processor and he was having problems on the AMD64.... So the problem would seem to point to processor architecture, unless he has a configuration problem....
Remember to re-run vmware-config.pl each time you install a new kernel to copy the modules into the new /lib/modules/<kernel-version>/ directory structure....
HTH,
--Rob
Craig
-- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.5 (GNU/Linux)
mQGiBECyQJQRBACLIa2u3u3/F8Pm+g5QD4K8eCgIC6RX1oXmtI9ALe9NhbNDZrcy hYhInCwCifi1zhxZZ/Xu4zyavk8n96USoXylfVg2hAM/P3qLarbqMDvfVPyjtUFd 8lg+NV4SgJ1F0jtqebrXu76AjCIBmLybQ1BYMTWDxB4xSW8lYlJT9+/QDwCg3f0z 9knFKiyZbzp4gpJvl4wH8lMD/0iB5t4VQr0jkQ1R1nVFx8sL9DwDogJZ0SJHnHrq fiBb+rx4lCLyz00VHlxxNSFsYRnpmefqC4ywfFnyQ9WpVxt3sqJ18ncxW04X3+cc DHLwqLdW2IKjT9CY4buDqyV8dcOdvYbHR1qQ1dcecYq9fyGHlHYCOr2X5frAmRF4 RcoRA/4oBXGKFhf2Q5ptguLHOce/2pzt2qoEL37IbSEATd2sjYE+HsDANzk+WXo9 j4Cwwepio9JOJ1kQXeVo7D07HIIZyJuk/RAIh1ztQALk0sFFj2SPiurcRpze4gH0 sn//CwlzY0swWaEoV0Jd/hALDvJvRQ+WZ+SVfJ5vfFKlGCowfrQxQ3JhaWcgU2hl cndvb2QgKFByaW1hcnkgS2V5KSA8Y3MwMDdsakB3b3d3YXkuY29tPoheBBMRAgAe BQJAskCUAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEOl3KJXc2eK43coAoIC+ wnag2QF02yUMshL5jI4jyywbAJ4yDt9aacCfwTVPNXkkoU9kamjwZbkCDQRAskCp EAgA8PmuinHlAukukL99OvbZ+eQusvrPACuvOxgNr8seDiJ1OTI5XfrUjgbJHNV2 K6x69vyui3j3BIKjyo1nq/AY6qrl4R39XuDylnvLr/I7P2tuUHDjy831E+S0suCz bEhRPxv42BnLkZP0ZdQteQn/bvDAHDJ0hMl21lau4PqU/sjQ7/yTGTUVGQhRQD1p 8RLbcnSsNbVrQvymBOLfzAC/jZn3EQ4pEm2qMrNXM4IRpcDrrOpkoMYyuBs4JkJ6 0jpZ9SVabCZU3ceGGs8JrB4Sdm9omHKeIrBzCs5QnyYVVCY//bJTAp7inLYYRj6g MmmLY4v35UXiCNmYfDYtYvLPFwAEDQgAz1aOHCkni2Vc62DIJJiYy9dQ+ZNxJH4y QBVAJ69HFLHwTfDpyIHCedKwQnTc/wFYghtypXCJkyBE1AsQispArtux2gXADc9C y6MR3pdOfCBNPf9152oNTYwaPFzUIm/OJfhyxT1gHRuGjb2F697YnlVEP5SKA7E5 FeaZcg+d9FtBH/BUYpXzWvvE4mh3mfDJ/qwRJpK4qjhZncNSoiT7ZjX8LaNtvkK6 aYQczNYV36pPGAe2GZ3MNWxtOYjLZJvmUw76ARPZn7Rt1jYdbXZJ3C0H+0BPEg+e 1MsA3z3xO7Y+20fQLBqQC+sUyQWzURv+sme3go7A4/XnfP35OzCnAohJBBgRAgAJ BQJAskCpAhsMAAoJEOl3KJXc2eK4WTQAnRX+0D+aIUSLYQ18xtqKUPQQQyphAJ0Z WmPi4ubVkt7NDFm0rIVJza2IRQ== =NGxD -----END PGP PUBLIC KEY BLOCK-----
Attachment:
signature.asc
Description: OpenPGP digital signature
