Don't include cd-roms

M

mike.spragg

New Member
May 19, 2024
23
2
3
Not sure if this is possible but a couple of initial attempts failed with a failure surrounding the mounted cd-rom devices. Would be great to exclude those by default as I can't see a reason why you'd ever need to include those in the migration.

(With thanks to tscret for offering a script to do exactly this in advance !)
 
I tend to think that's the system administrators screwing up, not the software. ESXi has the same challenge.
If your admin has mounted an ISO present only on that host and then left it that way, well vmotion to another host that does not have that ISO is not possible.
Tell your admins not to do that.
 
  • Like
Reactions: Johannes S
tcabernoch said:
I tend to think that's the system administrators screwing up, not the software. ESXi has the same challenge.
If your admin has mounted an ISO present only on that host and then left it that way, well vmotion to another host that does not have that ISO is not possible.
Tell your admins not to do that.
Click to expand...
Yes, I agree - but this isn’t vMotion - it’s more akin to vCenter Data Transfer - and that didn’t present the cds for transfer. Either way, of course this is a training thing but, also, if the software is always going to fail then you could always simply stop it from doing so by excluding it to begin with.
 
Hello everyone,
Is there a way to automatically exclude CD-ROMs during data transfer in Proxmox, or would a script be the best solution to handle this?
 
It errors only if the disk image isn't available on the other side. Put the disk image on shared storage and it will transfer. You'll get errors with ANY other hardware that can't transfer state, CD (the physical thing) are ancient in comparison and were never meant for multi-host access unlike regular disks.
 
  • Like
Reactions: Johannes S
guruevi said:
It errors only if the disk image isn't available on the other side. Put the disk image on shared storage and it will transfer. You'll get errors with ANY other hardware that can't transfer state, CD (the physical thing) are ancient in comparison and were never meant for multi-host access unlike regular disks.
Click to expand...
It is - it’s not physical but an image uploaded. That’s the issue, but not to worry
 
tcabernoch said:
The VMware answer to this would be to make the disk available in the remote location, so there's no error.

So either
have a copy of the disk in the remote location,
or put the disk itself on shared storage that both hosts have identical mapping to.
Click to expand...
Either I'm not explaining this right or there is other confusion. What happens is this: VMWare vCenter Converter Standalone connects to both servers. You pick the server to be copied from and the server to be copied to. It ignores any mounted CD Drives and *poof* after a while you have the original server on the new server.

With PDM you pick the source and the destination and *poof* it errors right off the bat. The reason is - in the source server you have a mounted/referenced cd-drive. When you pick the source/destination it only offers the vdisks to be copied but immediately errors because the source has a cd-drive mounted and referencing, say, an ISO. The ISO isn't relevant to the running of the system at all - perhaps it's a copy of SQL Server install for example. The issue is - it tries to open/copy it - and fails. You then go back, delete the original CD disk and it's perfectly happy to then transfer. So, it's not like you get a choice to remove during transfer - even if you pick the advanced options - you don't see the CD as a drive - it physically fails until you go back and remove it from the source. So, I don't see how you can have identical mappings when you get no choice on the 2nd (not yet created) destination server. Now I know this - I'm happy to remember that - it's not a big issue. But, suspect others will get caught on something that is, mostly, fairly irrelevant - you can always mount it after the copy if you need it. My, admittedly simple, idea was for it to do the same - just ignore the CD drives as, real world, you'd never want it to try an image a CD (which is what it seems to want to do) but create a reference to it (or ignore it altogether and you, as admin, re-attach it later). It's no big deal but I'm unsure in what you mean about identical mappings when, in actuality, you don't have any choice as the destination server isn't imaged at the point you use PDM to make a copy of the original. Maybe my misunderstanding but see image - no option not to include CD at time of migration.
2025-01-10_20-49-45.png


If you compare that with VMWare Converter - you'll notice no offer to copy the CD at all, just physical/OS disks.

2025-01-10_20-49-45-2.png

But, as I say, offer this here as a suggestion, not proving one of the other - VMWare is dead to me due to Broadcom ! Long live Proxmox.
 
guruevi said:
It errors only if the disk image isn't available on the other side. Put the disk image on shared storage and it will transfer. You'll get errors with ANY other hardware that can't transfer state, CD (the physical thing) are ancient in comparison and were never meant for multi-host access unlike regular disks.
Click to expand...
Hmm, I have a Samba share on which the problematic ISO is sitting. The same share is available on the target node as well. The names are identical. And yet, it errors out.

I believe that in my situation (at least), it should not error out but transfer the VM.

And I agree that there should be an option to exclude from the transfer a drive that would otherwise block the transfer.

Just my two cents.
 
  • Like
Reactions: mike.spragg
You must log in or register to reply here.
Top Bottom