tom11011
Contributor
Contributor

Strange Migration issue

Hi all, running a cluster of esx 3.01 servers.

I have one vm out of a dozen that will not migrate for some reason. It seems to have something to do with the cdrom.

Upon trying, I get the following error:

Unable to migrate from host01.domain.com to host02.domain.com: Virtual machine is configured to use a device that prevents migration: Device 'CD/DVD Drive 1' is a connected device with a remote backing.

I made up the host01.domain.com part.

I have removed and than re-added the cdrom.

I have confirmed that the boxes are not checked to connect the device, but after the device is started, the box is checked and greyed out. The first box says 'Connected - client unknown'. The other box is unchecked (connect at power on).

When the vm is shut off, it will migrate.

Any help appreciated!!

0 Kudos
11 Replies
esiebert7625
Immortal
Immortal

So you have the CD-ROM set to Client Device instead of host/datastore? Are you sure there are no other clients connected to that VM that may have their Client CD-ROM connect to that VM.

0 Kudos
Eddy
Commander
Commander

you could try removing VM and reregistering...

Go Virtual!
0 Kudos
tom11011
Contributor
Contributor

I'm not sure I understand. All of my vm's have there cdrom set to client device, that's the only way any of them will migrate.

Do you mean other clients attached to the esx host? I'm not sure I understand what you mean.

tom

0 Kudos
esiebert7625
Immortal
Immortal

Do you have anyone else running the VI Client that may be connected to that VM via remote console and have their CD-ROM mapped to that VM.

0 Kudos
surferdave
Enthusiast
Enthusiast

Could someone have remote desktop open or a session that has a mapped drive, CD ROM, printer, etc. that has become disconnected?

0 Kudos
tom11011
Contributor
Contributor

Thanks everyone for responding. I have completely removed the cdrom from the vm.

When I try to migrate, I get the following message.

Unable to migrate from host01.domain.comi to host02.domain.com: Currently connected device 'Floppy Drive 1' uses backing '/dev/fd0', which is not accessible.

0 Kudos
esiebert7625
Immortal
Immortal

Sounds like your floppy is mapped to your Host Device, map it to Client Device instead and it should work.

0 Kudos
tom11011
Contributor
Contributor

Hi both the floppy and cd were mounted to client device.

With both floppy and cdrom removed from the system, it will migrate ok. As soon as I move one back, it breaks.

I'm not sure what else to try.

0 Kudos
Texiwill
Leadership
Leadership

Hello,

You floppy and cdrom are really still connected for some reason. That is the only answer.

You can look at the VMX file for the VM.

If you show all the cdrom/floppy lines you can tell how it is connected or if it is present. Sounds like VC may be a little confused. Check the VMX to be sure. YOu want the .present options to be FALSE.

Best regards,

Edward

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
tom11011
Contributor
Contributor

Ok, I have removed the cd and floppy from the config in vcenter. Here is my vmx after adjusting vcenter. Seems confusing as some are false, some are true?

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

floppy0.present = "false"

nvram = "devserv1.nvram"

powerType.powerOff = "default"

powerType.powerOn = "default"

powerType.suspend = "default"

powerType.reset = "default"

displayName = "devserv1"

extendedConfigFile = "devserv1.vmxf"

numvcpus = "1"

scsi0.present = "true"

scsi0.sharedBus = "none"

memsize = "1024"

scsi0:0.present = "true"

scsi0:0.fileName = "devserv1.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

ide0:0.present = "false"

ide0:0.fileName = ""

ide0:0.deviceType = "cdrom-raw"

floppy0.fileName = ""

ethernet0.present = "true"

ethernet0.startConnected = "true"

ethernet0.wakeOnPcktRcv = "false"

ethernet0.networkName = "vlan_10"

ethernet0.addressType = "vpx"

ethernet0.generatedAddress = "00:50:56:9d:28:af"

usb.present = "false"

serial0.present = "false"

serial0.yieldOnMsrRead = "true"

serial0.fileName = "/dev/ttyS0"

guestOS = "winnetstandard"

uuid.bios = "50 1d 10 84 ad 0c 3c ed-26 f7 02 92 07 b8 50 be"

sched.cpu.shares = "normal"

sched.cpu.affinity = "all"

sched.mem.shares = "normal"

sched.mem.affinity = "all"

log.fileName = "vmware.log"

workingDir = "."

sched.cpu.min = "0"

sched.cpu.units = "mhz"

sched.mem.minsize = "0"

vmware.tools.requiredversion = "7201"

sched.mem.max = "unlimited"

scsi0:0.redo = ""

uuid.location = "56 4d 58 20 6c 19 30 8d-fd 66 08 4e a5 09 c7 9c"

sched.swap.derivedName = "/vmfs/volumes/4649d759-6ee2f76c-8702-0019b9b692aa/devserv1/devtrax1-b729bf81.vswp"

tools.syncTime = "TRUE"

ide0:0.clientDevice = "true"

ide0:0.startConnected = "false"

sched.cpu.max = "1024"

ethernet1.present = "true"

ethernet1.networkName = "vlan_5"

ethernet1.addressType = "vpx"

ethernet1.generatedAddress = "00:50:56:9d:3d:e5"

floppy0.clientDevice = "TRUE"

floppy0.startConnected = "FALSE"

Message was edited by:

tom11011

0 Kudos
esiebert7625
Immortal
Immortal

You might try powering off the VM and deleting these lines...

floppy0.fileName = ""

floppy0.clientDevice = "TRUE"

floppy0.startConnected = "FALSE"

0 Kudos