XPost: alt.os.linux.mint, alt.os.linux.mageia   
   From: nospam@needed.invalid   
      
   On 6/21/2023 10:34 AM, Chris Elvidge wrote:   
   > On 20/06/2023 22: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.   
   >>   
   >>   
   >   
   > As this seems to be nic-relevant, perhaps try removing all networking from   
   the vbox machine before exporting and then (if it starts) put back the   
   networking in vmware.   
   >   
      
   At the moment, it's not getting to the point where networking would matter.   
      
   The warning messages come from GTK.   
      
   Still thinking positive here.   
      
   My setup is booting, so I got that far, but the screen goes black.   
   And I'm working on it. I'm moving these VMs between two boxes (.vmdk file),   
   and the second box is running Ubuntu 22.04 with VMWare Player 17 in it.   
      
   Every operation takes its own sweet time.   
      
   ******* Two days pass... *****************   
      
   OK, I'll try and summarize and cut out some of the fat.   
      
   When I bring over a container manually, I get   
      
   1) Can ping the Guest. Network working at ping level.   
   2) Can use nbtscan (NetBIOS working). This means at least   
       two Services with the word "Function" in their name must   
       be running.   
   3) Can't remote in and use Terminal Server. Could be Firewall,   
       could be something else.   
      
   Screen remains black. Even Safe Mode doesn't work.   
      
   Machine rails on cores, and leaving it for extended periods of time   
   does not help.   
      
   This was an attempt to transplant a VM, by simply overwriting   
   the C: partition with "dd". (Take an install that was working   
   on VMWare Player, and replace the C: partition with the   
   mature C: image.)   
      
   *******   
      
   So I was forced to try it the same way as Alan (OVF appliance).   
      
   1) OVF 1.0 format on the source VirtualBox end.   
      
   2) VMWare player whines about "not OVF 1.0 compatible",   
       and then you click a button to try again, and it does it.   
       It does this, by throwing away lots of config info (metadata).   
      
   3) Your HDD corresponding to .vmdk container is present.   
       The SATA DVD, the sound card, the USB hub have to be added manually.   
       There is an "Add" button to add them.   
      
   4) Very important. In the Options part of the machine settings,   
       the Guest operating system has been set to "Other" by the automation.   
       This is bad. Set it back to Windows. Hosting softwares need to know   
       the OS, so they can "inject" stuff properly and mess around when you   
       are not looking.   
      
   The sound subsys doesn't always behave itself. The "Auto" setting   
   seems to work, but only sometimes.   
      
       [Picture]   
      
       https://i.postimg.cc/SQVP0Q4k/Transplant-To-VMWare-Player.gif   
      
   My Win10.vmx file, has this for sound. I've seen other wacky   
   lines in place of this. Third time lucky.   
      
   sound.pciSlotNumber = "34"   
   sound.present = "TRUE"   
   sound.autoDetect = "TRUE"   
   sound.virtualDev = "hdaudio"   
   sound.fileName = "-1"   
      
       Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)