hpvmmigrate problem - have to use "-w" option

[sbrews]

This is an ongoing problem that doesnt seem to want to get solved...

I have a 3 nodes that are part of an HPVM setup.   Each has 4 NICs

- lan0: main NIC for connection to the network

- lan1, lan2: set up in a hot standby as lan900

- lan3: private network for 3 nodes to "talk" to each other

- vswitch: virtual switch for the VMs.

When we try to migrate a VM from one host to another, the migration fails due to vswitch communication check failures.  If the "-w" option is used on the migration, the VM will successfully move.

... lots of testing, poking and talking with HP and my network team... Still need the "-w" option on the migrate.

Have any of you that use HPVM run into this?  If so, did you resolve the issue and how?  At this point I am looking for any ideas that may help solve the issue.

[Duncan Edmonstone]

A little more information would be a good start...

version of HPVM? Any patches applied to HPVM?

Version of OS on Host? And Update release?

Version of OS on Guests? And Update release?

vSwitch configurations (hpvmnet -V)

And of course what do you actually see when you don't have the "-w" option on hpvmmigrate - what is reported by the command?

[Steven E. Protter]

This may be a release specific bug. I'm current lead in a shop that favors vpars, but played around a lot with HPVM a while back.

Did not need the -w option for hpvmigrate.

We were running HPVM 4.2 and 4.3 back then.

[Stan_M]

We have seen this with old networking drivers.

Update APA and the underlying  NIC drivers. It should resolve the problem. You can test with linkloop command, HPVM does

the same check which linkloop does.

HTH

Stan