Member Avatar for Dani

I use VMWare 3.2 on a RedHat Linux 8 host. I compiled the module locally, as opposed to using one of the pre-configured modules (as I don't believe official support for RedHat 8 has been released yet).

In any case, I use a Windows 2000 guest OS. However, regardless of which OS I use, I get the following error upon shutting down the virtual machine:

VMware Workstation Unrecoverable error: (VMX)
AIO: NOT_IMPLEMENTED F(831):654
Please request support and include the contents of the log file: 'win2000Pro.log'.

Can anyone help by any chance? The contents of the .log file it says to include is incredibly long. However, after it gives all of this configuration info, it keeps repeating the following 3 lines thousands of times, as if in a loop:

Jan 01 14:54:49: VMX|COWDisk_OpenFromP(win2000Pro.vmdk) flags 0x0= diskNum=0
Jan 01 14:54:49: VMX|FILEIO: Reverting to buffered IO for file win2000Pro.vmdk
Jan 01 14:54:49: VMX|COWDISK: Disk win2000Pro.vmdk Granularity = 128

Thanx in advance!

  • 3 Contributors
  • 7 Replies
  • 746 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by Dani

Dani AI

Generated

Short expert summary tied to the thread: the VMX panic you saw (AIO: NOT_IMPLEMENTED) is the VMX I/O subsystem trying to use native asynchronous/direct I/O and hitting a host-side mismatch so it panics or falls back; the repeated "FILEIO: Reverting to buffered IO" lines show VMX falling back from direct/AIO to buffered I/O while it struggles with the disk backend. This exact symptom was widely reported when newer Red Hat 8 kernels and libc/glibc changes made VMware Workstation 3.x’s shipped modules incompatible until the host-side compatibility patch or rebuild was applied. (osnews.com)

What to know about the logs and ’s ide1 note: when the log shows AIO threads and then NOT_IMPLEMENTED (and ideX or scsiX thread names), it means the VMX AIO worker tried to create or use native async I/O for that virtual device and failed. That can happen because the kernel ABI changed, because the vmdk lives on a filesystem that does not support the direct I/O flags VMX expects (NFS, FUSE, certain mount options), or because the vmmon/vmnet modules were built for a different kernel. (vmware-forum.de)

Practical checklist (what actually fixed this class of problems in 3.x-era reports):

  1. Note host kernel (uname -r) and VMware version; install matching kernel-headers/kernel-devel, gcc/g++, then rebuild VMware modules (run the VMware configuration script).
  2. If rebuild fails because VMware source expects older kernel APIs, apply the appropriate “any-any” compatibility patch for your VMware release (run the patch’s runme.pl, then re-run vmware-config). Many users solved AIO panics this way.
  3. Short-term fallback: boot an older kernel that the shipped modules support, or move the VM files to a local filesystem if they were on NFS/FUSE. (blog.creonfx.com)

Context from this thread: pointed to the update referenced above and confirmed the patch resolved the panic — that mirrors the public reports and how the any-any style patches were used to restore module compatibility on newer kernels. If still troubleshooting, collect the full vmx log and the host uname/kernel-devel versions and look for the AIO/FILEIO lines shown here before requesting further help. (vmware-forum.de)

Member Avatar for mylogin

post a linux to the log file (or the file itself)

Member Avatar for mylogin

a problem with ide1, "No DMA invalidation"

It's treating your hard drive as scsi and there were communication errors afaik

Member Avatar for Dani

Hmm ... I think that the virtual machine is always supposed to emulate my IDE hard drives and cd drives as SCSI (it always did before, anyway? and I've been using VMWare for quite awhile w/ no probs)

This problem just decided to start when I switched from RedHat 7.3 to RedHat 8

any ideas 4 a fix? VMWare *works* it just gives me this error when it *exits* ?

thanx!!
- dani

Member Avatar for mcgd

Hi Dani,

There is a 3rd party patch for this bug. VMware references it but doesn't support it. You can find vmware's reference here:

http://www.vmware.com/support/kb/enduser/std_adp.php?p_sid=JHN_XjAg&p_lva=&p_faqid=873&p_created=1034809585&p_sp=cF9ncmlkc29ydD0mcF9yb3dfY250PTEmcF9zZWFyY2hfdGV4dD1yZWRoYXQgOCZwX3NlYXJjaF90eXBlPTMmcF9wcm9kX2x2bDE9MSZwX3Byb2RfbHZsMj1_YW55fiZwX2NhdF9sdmwxPX5hbnl_JnBfY2F0X2x2bDI9fmFueX4mcF9zb3J0X2J5PWRmbHQmcF9wYWdlPTE*&p_li=

if that link works, or else go to http://www.vmware.com/support/
then click on the "Linux" link under "Workstation" on the left-hand side of the screen, and search for "redhat 8".

Cheers

-Matthew

Member Avatar for Dani

woo hoo! :)
very cool

I'm at school now so I don't have access to my Linux computer. But as soon as I can I'll try it out and let you know if it worked.

I'll get back to ya in a few days ...

Member Avatar for Dani

Whoa ... weird but it took me a whole month to get around to this one. (I've been really busy).

In any case, it worked! yay!! :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.