XPost: alt.os.linux.mint, alt.os.linux.mageia   
   From: TJ@noneofyour.business   
      
   On 2023-06-20 17:05, pinnerite wrote:   
   > Virtualbox with Windows 10 over Linux Mint was so slow as to be useless   
   > but I need it.   
   >   
   > I decided to export the Windows 10 virtual machine to an ova file and   
   > import into VMware player 17.0.2.   
   >   
   > There were several slips but eventually it was imported.   
   > BUT it would start and then exit after the Windows 10 virtual machine   
   > was started.   
   >   
   > Starting it from a terminal as /usr/bin/vmplayer caused it to start   
   > then stop after producing the following warnings: (I have removed the   
   > repetitive prefixes).   
   >   
   > removable-device-0: missing action removable-device-0   
   > removable-device-0-connect: missing action removable-device-0-connect   
   > removable-device-0-nic-bridged: missing action   
   > removable-device-0-nic-bridged removable-device-0-nic-nat: missing   
   > action removable-device-0-nic-nat removable-device-0-nic-host-only:   
   > missing action removable-device-0-nic-host-only   
   > removable-device-0-edit: missing action removable-device-0-edit   
   > removable-device-0: missing action removable-device-0   
   > removable-device-0-connect: missing action removable-device-0-connect   
   > removable-device-0-nic-bridged: missing action   
   > removable-device-0-nic-bridged removable-device-0-nic-nat: missing   
   > action removable-device-0-nic-nat removable-device-0-nic-host-only:   
   > missing action removable-device-0-nic-host-only   
   > removable-device-0-edit: missing action removable-device-0-edit   
   >   
   > I have ensured all three virtual network connections (Bridged, Host   
   > only and NAT) were enabled but that made no difference other than to   
   > add additional ertor messages gfor device-1 and device-2.   
   >   
   > Frustrating.   
   >   
   >   
   I've never used VMware, so I really know nothing about it, but at a   
   guess I would think the trouble might be that the Windows VM is set up   
   to use the VirtualBox simulated devices, and is confused because VMware   
   is using different ones.   
      
   I would think it would be like pulling a Windows hard drive from one   
   machine and plugging it into another with different hardware. Linux   
   might work, but Windows won't. The installed drivers are all wrong.   
      
   TJ   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)