Upgrade of OES11sp2 XEN VM

Hi,

Running SLES11sp3 with OES11sp2 as a XEN virtual machine on a SUSE12 server. This VM server is my main DNS and DHCP server.

I have created FTP on the host server (SUSE12) and copied the upgrade software for SLES11sp4 and OES 2015sp1 onto the server
and the FTP://127.0.0.1 works correctly.

I then run "vm-install" and try the "I need to upgrade the existing operating system". The system seems to get to about 75% and
then fails at the point "Sending DHCP request to Eth0" (mmmh, it is not going to get an answer cos it is the DHCP server that is being upgraded)

My other VM's upgraded perfectly so now I am a bit stuck...

Any help in this regard will be appreciated.
John
Parents
  • mmmh, both the Host and the VM have hard coded IP's. The issue is that during the boot of the VM,
    a request is sent to the DHCP (who knows why) server, but the VM being upgraded is the DHCP server ...
  • John Gill wrote:

    >
    > mmmh, both the Host and the VM have hard coded IP's. The issue is
    > that during the boot of the VM,
    > a request is sent to the DHCP (who knows why) server, but the VM being
    > upgraded is the DHCP server ...


    Hi John,

    I'm still running OES as a DomU with a static IP address. Over the
    years I've encountered similar issues. I don't know why SUSE assumes a
    server will be using DHCP but they do and this has been a royal pain in
    my ***.

    I've open several SRs which have resulted in new bugs being opened.
    Sure, the problem is eventually identified and a workaround developed
    but it may take a while.

    The real issue is the assumption that a DHCP server is available. My
    workaround is to make one available. Perhaps you can install DHCP on
    your Dom0 and only enable it when upgrading VMs or use a home router?
    Use your DomU's MAC address to ensure you get the same IP address as
    you have statically assigned.

    Good luck...

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
Reply
  • John Gill wrote:

    >
    > mmmh, both the Host and the VM have hard coded IP's. The issue is
    > that during the boot of the VM,
    > a request is sent to the DHCP (who knows why) server, but the VM being
    > upgraded is the DHCP server ...


    Hi John,

    I'm still running OES as a DomU with a static IP address. Over the
    years I've encountered similar issues. I don't know why SUSE assumes a
    server will be using DHCP but they do and this has been a royal pain in
    my ***.

    I've open several SRs which have resulted in new bugs being opened.
    Sure, the problem is eventually identified and a workaround developed
    but it may take a while.

    The real issue is the assumption that a DHCP server is available. My
    workaround is to make one available. Perhaps you can install DHCP on
    your Dom0 and only enable it when upgrading VMs or use a home router?
    Use your DomU's MAC address to ensure you get the same IP address as
    you have statically assigned.

    Good luck...

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.
Children
No Data