Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

VM's not bootable after upgrade vim.fault.DeviceBackingNotSupported

$
0
0

 

Hello,

 

 

I upgraded one of my 3.0.2 servers to ESX 3.5 and now some of my VM's will not boot anymore giving the eror:

 

 

Device 'Floppy Drive 1' has a backing type that is not supported. This is a general limitation of the host.

 

 

When i want to change the floppy device in the "edit settings" of the VM, i get the error: The information for device 'floppy drive 1' is inconsistent with the allowed values. This is most likely the result of manual editing of the configuration file. The device cannot be edited in this state. A synopsis of the problem will appear in the client log file.

 

 

So i went to the logfile:

 

 

-- BEGIN task-87 -- vm-173 -- Datacenter.ExecuteVmPowerOnLRO

Checking admissibility of VM id: vm-173, name: LAB-VM01 under respool id: resgroup-142, name: Resources

 

 

Unexpected Exception: vim.fault.DeviceBackingNotSupported

-- ERROR task-87 -- vm-173 -- Datacenter.ExecuteVmPowerOnLRO: vim.fault.DeviceBackingNotSupported:

(vim.fault.DeviceBackingNotSupported) {

   dynamicType = <unset>,

   device = "Floppy Drive 1",

   reason = "host",

   backing = "vim.vm.device.VirtualFloppy.RemoteDeviceBackingInfo",

   msg = ""

}

-- BEGIN task-internal-1974 --  -- vmodl.query.PropertyCollector.createFilter -- 8269893F-8285-44B9-9BEC-BA2AD903D148

-- FINISH task-internal-1974 --  -- vmodl.query.PropertyCollector.createFilter -- 8269893F-8285-44B9-9BEC-BA2AD903D148

-- BEGIN task-internal-1973 --  -- vmodl.query.PropertyCollector.Filter.destroy -- 8269893F-8285-44B9-9BEC-BA2AD903D148

-- FINISH task-internal-1973 --  -- vmodl.query.PropertyCollector.Filter.destroy -- 8269893F-8285-44B9-9BEC-BA2AD903D148

-- BEGIN task-internal-1975 --  -- vmodl.query.PropertyCollector.Filter.destroy -- 8269893F-8285-44B9-9BEC-BA2AD903D148

-- FINISH task-internal-1975 --  -- vmodl.query.PropertyCollector.Filter.destroy -- 8269893F-8285-44B9-9BEC-BA2AD903D148

 

 

The log on the ESX HOST for the VM  gives:Aug 19 08:28:18.327: vmx| SOCKET 1 client closed connection

 

 

Aug 19 08:28:18.333: vmx| vmdbPipe_Streams: Couldn't read

Aug 19 08:33:34.925: vmx| CnxAcceptConnection: Could not send the magic marker on 27: Broken pipe

Aug 19 08:37:00.187: vmx| SOCKET 4 client closed connection

Aug 19 08:37:00.192: vmx| vmdbPipe_Streams Couldn't read: OVL_STATUS_EOF

Aug 19 08:45:09.835: vmx| Caught signal 15 -- tid 101239 (eip 0x1024d783)

 

 

I did not manually edit the vmx file.. but the entry for floppy are as followed:

 

 

config.version = "8"

 

 

virtualHW.version = "3"

 

 

floppy0.present = "true"

 

 

floppy0.startConnected = "false"

 

 

floppy0.clientDevice = "true"

 

 

floppy0.fileName = "/dev/fd0"

 

 

 

 

 

Hints?

 

 


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>