virtualbox.org

Good Afternoon , I have installed Virtual Box e followed step to import a old Virtual machine. The old Virtual Machine have Windows XP installed. I started the OS by VM but every Windows startup get´s system shutdown

. Which way is right to export or Vm needs to change settings to have right function?

Machineuser15 wrote:followed step to import a old Virtual machine

Import it from where? Old version of VirtualBox? VMWare? VirtualPC? OVA? OVF?
What is the error message you are getting?
What is your host?
What is your VirtualBox version?

Please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (ONLY) to a zip, and attach the zip here.

Also, make sure yours is not a duplicate of viewtopic.php?f=6&t=79183. I.e. if you just upgraded to Win10 from Win7 then it's expected that VMs which originated in "XP Mode" will fail.

I uploaded file logs. Did files help?

Now the laptop works with Windows 8.1 and the Virtual Box version are 5.1.2 r108956 . The last installation Virtual Box was in Windows 10.

No, the log doesn't really help. It shows a VM which is very short of resources (e.g. only 16MB graphics RAM), and the VM is being launched from an odd location, but I don't see any errors. I just see the VM shutting itself down. The log shows that the host is Win7, so I'm not sure what your last post is about.

Given how low this host is on resources we can't do much, but I would decrease VM RAM to 512MB, and I'd increase display RAM to 48MB. If you can reduce RAM use elsewhere on this host then that would help too.

The GAs CD is still mounted, which is not good practice.

I see the non fatal error :-

VBox.log wrote: 00:00:05.977245 SharedFolders host service: Adding host mapping
00:00:05.977275 Host path 'C:\Users\Ayrtun\Documents\pasta comp', map name 'pasta_comp', writable, automount=true, create_symlinks=false, missing=true
00:00:05.977360 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Shared folder path 'C:\Users\Ayrtun\Documents\pasta comp' does not exist on the host}, preserve=false aResultDetail=0

The main thing this tells me is that the host PC has changed, though it looks as if the complete file set has been kept together, which is good.

I'll ask my question more explicitly: is this an "XP mode" VM? Because I've seen XP mode VMs behave like this when moved to other hosts.

Machineuser15 wrote:Now the laptop works with Windows 8.1 and the Virtual Box version are 5.1.2 r108956 . The last installation Virtual Box was in Windows 10.

Yet the logs are from a Windows 7 host. What is going on???

Ah, I just double checked something.

VBox.log wrote: VirtualBox VM 5.0.20 r106931 win.x86 (Apr 28 2016 14:35:57) release log
00:00:03.772226 Log opened 2016-06-27T18:26:30.660912000Z

Log opened 27th June 2016. These are not current logs. But, even when they were current they show a VM with the problems I described above. So any impression that this VM was previously working fine doesn't seem correct.

Yes, I need to run some application in WIndows XP.This application are most old application. My laptop have Windows 8.1 installed. I have tried this Virtual machine in other laptop with Windows 7 installed. I forgot that. I upgraded Windows 8.1 to Windows 10. The Virtual Box is from Windows 10. I looking for solution to correct startup from Windows XP. Have some steps to correct errors from Virtual Machine Windows XP rebooting normaly?

mpack wrote:Ah, I just double checked something.

VBox.log wrote: VirtualBox VM 5.0.20 r106931 win.x86 (Apr 28 2016 14:35:57) release log
00:00:03.772226 Log opened 2016-06-27T18:26:30.660912000Z
Log opened 27th June 2016. These are not current logs. But, even when they were current they show a VM with the problems I described above. So any impression that this VM was previously working fine doesn't seem correct.

I have opened again Virtual Machine but Log doesn´t updated date. The Windows XP start normally in Virtual Box but after Windows XP show desktop without icon finally shutdown.

Machineuser15 wrote:Have some steps to correct errors from Virtual Machine Windows XP rebooting normaly?

No, not really.
Not until you select a host that has a problem with the WinXP VM and post the log that shows the problem. We can't be guessing, we need facts.

Where can I find log updated?
I imported today VM again but the log have the same date before. This log´s is the same log that I have shared in this post.

socratis wrote:

Start the VM. Not from a saved or suspended state. Clean start.

Take the steps required to generate/observe the error.

Shut down the VM. Not suspended, not paused. Shut down.

Right-click on the VM in the VirtualBox Manager. Select "Show Log..."

Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

00:00:02.041725 Host RAM: 3995MB total, 1378MB available
00:00:02.744498   RamSize           <integer> = 0x0000000006400000 (104 857 600, 100 MB)

Win XP will have a really hard time running with only 100MB of RAM allocated. Take it to at least 512MB. You can afford it. It's a miracle that it even runs...

virtualbox.org

Import old Virtual Box Machine

Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine

Re: Import old Virtual Box Machine