VMware vSphere

 View Only

  • 1.  convert Slackware Linux or just copy-move?

    Posted Jun 22, 2016 08:00 PM

    i have a 2003 server that runs Vmware Server 2.0 and host 2 VMs running Slackware 12 on a pretty old piece of HW.

    I have tried a couple different times/ways using a converter, but says "Re: "Unable to Obtain Hardware information for the selected machine"Unable to Obtain Hardware information for the selected machine". 

    Logs don't give me much to go on. 

    Tried with vm off/on

    Tried with older converter I could find 5.5 and newest 6.

    Maybe I'm going about it the wrong way.  What am I missing?

    can I copy/move the folder with some hacks?



  • 2.  RE: convert Slackware Linux or just copy-move?

    Broadcom Employee
    Posted Jun 23, 2016 07:52 AM

    Could you upload log bundle? The logs should contain some results of execution of sysinfo utility.



  • 3.  RE: convert Slackware Linux or just copy-move?

    Posted Jun 23, 2016 03:27 PM

    here's the logs from 2 different machines.

    I also tried to converting from a copy of the VMs.   The screenshot is of the 2003 server of the services.

    thanks



  • 4.  RE: convert Slackware Linux or just copy-move?
    Best Answer

    Broadcom Employee
    Posted Jun 24, 2016 07:37 AM

    Both errors are similar: FILE: FileIO_Lock on '....\NS1-000001.vmdk' failed: Lock timed out

    Are you trying to convert running machines? This is not possible, you should treat them as powered on sources or shutdown and then convert.

    HTH



  • 5.  RE: convert Slackware Linux or just copy-move?

    Posted Jun 24, 2016 09:46 PM

    My method was to turn off the machines and copy the directory(s) to test the process.  I did this several times to no avail.   Maybe it was the copy process, This time it worked.

    Although for a Ubuntu machine you need to do this also -- to get the eth0 adapter to connect.

    thanks

    Networking fails after cloning an Ubuntu virtual machine (1032790)

    Symptoms

    • After cloning an Ubuntu virtual machine, networking no longer functions.
    • The ifconfig command does not show the network interface (for example, eth0), but may show a new one (for example, eth1).
    • Restarting networking within the GuestOS with the command sudo /etc/init.d/networking restart shows the error:

      SIOCSIFADDR: no such device
      eth0: ERROR while getting interface flags: No such device
      Bind socket to interface: no such device
      Failed to bring up ethX
    • Reviewing the dmesg log with the command dmesg | grep eth may show a message similar to:

      udev: renamed network interfaces ethX to ethY

      Cause 

    This occurs because cloning a virtual machine creates a new MAC address for each network adapter. The guest operating system detects this is a new network adapter that has been inserted, but retains configuration for the previous network adapter.

    Resolution

    This issue is resolved in Ubuntu 10.10. For more information, see the Ubuntu bug 341006.

    Note: The preceding link was correct as of July 17, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

    To work around this issue, change the persistent udev rules for the network interfaces:

    1. In the Ubuntu guest, open a command prompt. For more information, see Opening a command or shell prompt (1003892).
    3. As root, open the file /etc/udev/rules.d/70-persistent-net.rules in a text editor:

      sudo vim /etc/udev/rules.d/70-persistent-net.rules
    5. The file consists of a line for each udev rule, associating MAC addresses with ethN interface names. For example:

      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
      SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xy", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
    7. Identify the old and new interfaces by their MAC address in the ATTR{address}=="" field. For example:

      ATTR{address}=="xx:xx:xx:xx:xx:xw" ... NAME="eth0"  # old
      ATTR{address}=="xx:xx:xx:xx:xx:xz" ... NAME="eth1"  # new
    9. Copy the ethN name from the old interface to the new interface line. For example:

      ATTR{address}=="xx:xx:xx:xx:xx:x1" ... NAME="eth0"  # old
      ATTR{address}=="xx:xx:xx:xx:xx:x2" ... NAME="eth0"  # new
    11. Delete the line for the old ethN interface. For example:

      ATTR{address}=="xx:xx:xx:xx:xx:x3" ... NAME="eth0"  # new
    13. Save the udev configuration file.
    15. Reboot the Ubuntu virtual machine.

    When the system is rebooted, the network configuration for the previous network interface is applied to the new interface.

    Note: If you are unable to reboot the virtual machine, you can manually restart the networking service using this command:

    service networking restart

    If this command fails with an unknown instance error, run this command:

    /etc/init.d/networking restart