Migrating VM fails with DUPLICATE_VM error part2

AndreS

OK, the underlying disk has problems. I found the kernel.log and it is filling up with read errors. That part is clear now.

So what lead me to try and migrate the vm (slow boot/response) uncovered a mac_seed duplication and we fixed that. Not sure if this was already fixed in the code last year.

On to this prblem; could I have seen the disk issue somewhere in the XO interface? In the logs I only see the higher level issue of failed migrations. It's a learning experience anyway; maybe a mirrored disk could be an answer. Need to investigate.

olivierlambert

Interesting to discover that mac_seed could cause this cryptic issue

XO doesn't have any knowledge on the "state" of the virtual disk, there's no API to expose that (if we can even imagine a way to know that the virtual disk got a problem in the first place)

AndreS

@olivierlambert Indeed. Learned a lot this week. Thanks for walking me through this.

Should I register anything for mac_seed duplication that is obviously caused by the export from esxi/import into xcp-ng? The MAC address duplciation issue was fixed earlier if I am not mistaken.

olivierlambert

I'd like to see if we can reproduce this. If yes, then we need to be careful on this parameter on OVA import, indeed. Ping @Darkbeldin so we can discuss on how to reproduce the problem first.

Darkbeldin

@olivierlambert Will take a look at it tomorrow morning

AndreS

@darkbeldin Thanks! If I can test anything let me know. Do note that I have removed the degraded disk from the host and said goodbye to three vm's that I could not copy/migrate/clone anymore. Not a big loss, this is a home lab but I could not even copy them away to preserve them for later. I do have the other vm (I imported two last year from esxi).

Darkbeldin

@andres Hi Andres,

Still working on it at the moment i keep you updated when i have more infos.

Darkbeldin

@andres Ok after discussing with XAPI team about that apparently the behavior is intended, you should not have VMs with the same MAC_SEED on the same host.

Dev team will take a deeper look at this to see if at least the error could be clearly reported.
To go further could you please provide us with the means you used to migrate your VMs from VMWare?
Did you do it manually? did you export from VMware to import to XCP?

AndreS

@darkbeldin We are talking 15-18 months ago ... What I remember is a fairly standard export from esxi into (I believe) an OVA format and I imported that directly into xcp-ng. I don't remember anything complex other than having to redo the export a few times to get properly rid of vmware tools and some drivers.

Edit: I checked a few articles and it was probably the OVF format.

Darkbeldin

@andres Thanks will do some testing on my side.

AndreS

@darkbeldin For the record, both vm's were running on the same esxi host when exported. This may or may not be a factor (I suspect it is).