Announcement

Collapse
No announcement yet.

VMWare Image with debian/Etch

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    It is a german keyboard layout.......

    Try to edit the vmx-file.
    ethernet0.vnet = "/dev/vmnet2"

    should be there, edit to
    ethernet0.vnet = "/dev/vmnet0

    sorry for the inconvenience

    Comment


    • #17
      Tried that edit.
      Still not finding eth0

      Did you use a special driver from vmware in the build?
      I think you mentioned you built this on the vmware beta?

      I fixed the keyboard issue by issuing the loadkeys -d command which looks to load a keymap that works OK with my US 101 keyboard.

      Comment


      • #18
        Not really a special drive on the guest side.

        You can try to do the following:
        lspci
        and have a look at the device if it is listed there.

        If not, you have to do something with the VMX file.
        If you find the network interface then try to unload the vmxnet driver.

        I installed the VMWare driver into the guest system.

        Thanks for the issue about the keyboard map.

        Comment


        • #19
          To set the NW Card to etho and enable DHCP:
          edit /etc/mactab
          Code:
          eth0 00:11:22:33:44:55
          change 00:11:22:33:44:55 to your mac-adresse (type ifconfig -a)

          edit /etc/init.d/networking
          add add case start and at case force-startup a new line, calling "nameif"

          reboot your maschine

          btw: ATM I'm seeding the image with up to 1,5 Mbit/s until 50 GB transfer ratio has been reached.

          Comment


          • #20
            Suggestions?

            Might be better to use the generic nic driver for the NIC rather than the vmware supplied driver. Looks like the version your using is not compatible with Vmware WS 5.5.

            Is anyone else running this on VM Workstation?
            If not what flavor are you running and is NIC is working?

            Another suggestion is the keyboard map and language.
            Maybe a startup script which will prompt for lang and location to select the end user language and keymap.

            Comment


            • #21
              Might be better to use the generic nic driver for the NIC rather than the vmware supplied driver. Looks like the version your using is not compatible with Vmware WS 5.5.

              Is anyone else running this on VM Workstation?
              If not what flavor are you running and is NIC is working?
              I'll do a test with VMWare Server 1.0 and VMWare Player 1.0 this evening.

              Another suggestion is the keyboard map and language.
              Maybe a startup script which will prompt for lang and location to select the end user language and keymap.
              Ok, I'll keep that in mind and change my VM to your suggestions. I'll create a new when the CVS install runs smoothly.

              Yesterday I get into trouble with the DB setup. (missing table sequence_uid_number)

              Comment


              • #22
                Originally posted by exrace View Post
                Is anyone else running this on VM Workstation?
                If not what flavor are you running and is NIC is working?
                Running on VM Workstation as described in my post.

                Comment


                • #23
                  What version of workstation?

                  Originally posted by toby View Post
                  Running on VM Workstation as described in my post.
                  What version of workstation?
                  I am thinking the VMware beta vmtools is not backward compatible.

                  Comment


                  • #24
                    At first: Thanks for this VMWare Image!

                    I am using:
                    open-xchange_community-edition_build-6048_20070309
                    VMware Player 1.0.3 build-34682
                    Host OS: Microsoft Windows XP Professional 5.1.2600, Service Pack 2

                    I tried ethernet0.vnet = "VMnet4", "VMnet0", "VMnet1", "/dev/vmnet0", "/dev/vmnet1", "/dev/vmnet4"

                    But in every case I got this error:
                    eth0: error fetching interface information: Device not found
                    I have connected "Ethernet" in VMware Player to "Bridged".

                    Any Ideas?

                    Comment


                    • #25
                      Neo is going to do some testing as stated in his previous post.

                      Comment


                      • #26
                        Originally posted by exrace View Post
                        Neo is going to do some testing as stated in his previous post.


                        Yep, right. Tests will be finished at the weekend.

                        I'll keep you updated.

                        BTW:

                        122 times downloaded. Thanks to all seeders

                        Comment


                        • #27
                          unable to create INBOX

                          I download the hyprion ox vmware images , and run the vmware,
                          when I change user of createDefaultUser.sh and run this script to
                          create the ox user, the same erroer appeared, just like the folling:
                          Could someone encounter this case or find the solution? Thanks a lot!

                          Server response:
                          com.openexchange.admin.plugins.PluginException: com.openexchange.admin.rmi.exceptions.OXUserIMAPEx ception: unable to create INBOX

                          Comment


                          • #28
                            About your problem, look here -> http://typo3.open-xchange.com/forum/showthread.php?t=81
                            Open-Xchange - Community Edition User

                            Comment


                            • #29
                              Is it also possible to run the Image at a Windows host system ?

                              Main problem is the mentioned ethernet problem.

                              Comment


                              • #30
                                You can run the vmware image on every host system you want - it is virtualized, that does the trick ;D

                                Comment

                                Working...
                                X