Try to migrate hpvm to other HPVM host

[davesec]

I tried to mygrate one of my VMs to another host with the command

# hpvmmigrate -P test -h tstbl870B8.work

But I every time get the Error:

hpvmmigrate: Connected to target host using 'tstbl870B8.work'
hpvmmigrate: ERROR (host): Source and target host must differ.

Some more information to avoid unnecessary questions:

[root@tstbl870B6 ~]# host tstbl870B6
tstbl870B6.work has address 172.16.19.180

[root@tstbl870B6 ~]# host tstbl870B8
tstbl870B8.work has address 172.16.19.178

[root@tstbl870B6 ~]# cat /etc/hosts
172.16.19.180   tstbl870B6.work tstbl870B6
172.16.19.178   tstbl870B8.work tstbl870B8
127.0.0.1       localhost       loopback

[root@tstbl870B8 ~]# cat /etc/hosts
172.16.19.180   tstbl870B6.work tstbl870B6
172.16.19.178   tstbl870B8.work tstbl870B8
127.0.0.1       localhost       loopback

[root@tstbl870B6 ~]# cat /etc/nsswitch.conf 
passwd:       compat
group:        compat
hosts:        files dns 
ipnodes:      files dns 
networks:     files
protocols:    files
rpc:          files
publickey:    files
netgroup:     files
automount:    files 
aliases:      files
services:     files

[root@tstbl870B8 ~]# cat /etc/nsswitch.conf 
passwd:       compat
group:        compat
hosts:        files dns 
ipnodes:      files dns 
networks:     files
protocols:    files
rpc:          files
publickey:    files
netgroup:     files
automount:    files 
aliases:      files
services:     files

[root@tstbl870B6 ~]# swlist | grep VM
  Base-VxVM-50                  B.05.00.01     Base VERITAS Volume Manager Bundle 5.0 for HP-UX 
  BaseLVM                       B.11.31.0903   Logical Volume Manager 
  GuestAVIOStor                 B.11.31.0903.01 HPVM Guest AVIO Storage Software 
  GuestAvioLan                  B.11.31.0903   HPVM Guest AVIO LAN Software 
  HPVM-Guest                    B.04.10        Integrity VM Guest 
  HostAVIOStor                  B.11.31.0903   HPVM Host AVIO Storage Software 
  HostAvioLan                   B.11.31.0903   HPVM Host AVIO LAN Software 
  T2801AA                       B.04.10.02     Integrity VM Trial Bundle 
  VMGuestLib                    B.04.10        Integrity VM Guest Support Libraries 
  VMGuestSW                     B.04.10        Integrity VM Guest Support Software 
  VMKernelSW                    B.04.10        Integrity VM Kernel Software

[root@tstbl870B8 ~]# swlist | grep VM
  BaseLVM                       B.11.31.0903   Logical Volume Manager 
  GuestAVIOStor                 B.11.31.0903.01 HPVM Guest AVIO Storage Software 
  GuestAvioLan                  B.11.31.0903   HPVM Guest AVIO LAN Software 
  HPVM-Guest                    B.04.10        Integrity VM Guest 
  HostAVIOStor                  B.11.31.0903   HPVM Host AVIO Storage Software 
  HostAvioLan                   B.11.31.0903   HPVM Host AVIO LAN Software 
  T2801AA                       B.04.10.02     Integrity VM Trial Bundle 
  VMGuestLib                    B.04.10        Integrity VM Guest Support Libraries 
  VMGuestSW                     B.04.10        Integrity VM Guest Support Software 
  VMKernelSW                    B.04.10        Integrity VM Kernel Software

I run secconf on both hosts. ssh from one to the other works with the certificate authentication.

[Torsten.]

I could imagine the following problem:

You are using hostnames larger then 8 chars, but (most likely) only 8 are used here:

tstbl870

so just from parsing source and target may look like the same ...


Hostnames longer than 8 chars may produce problems almost everywhere.


Did you test this command with IP?

[davesec]

Yes I did:
---
[root@tstbl870B6 ~]# hpvmmigrate -P test -h 172.16.19.178
hpvmmigrate: Connected to target host using '172.16.19.178'
hpvmmigrate: ERROR (host): Source and target host must differ.
---

[Torsten.]

All hints I can find are pointing to /usr/share/doc/NodeHostNameSize.pdf but I have no access to a system.

For whatever reason IMHO the system "think" the destination is the same as the source.

[Anonymous · Accepted solution]

Most likely the underlying problem is a bogus Machine ID number shown for example by machinfo: ffffff00-ffff-ffff-ffff-ffffffffffff.

It's a BL8x0 system FW issue which should be fixed in the next FW release.

Workaround is
- shutdown system.
- unassign the VC profile
- reset the MP-iLO
- reassign the VC profile
- boot

[davesec]

That was the solution.

Thank you.

[davesec]

Case closed.