Discussion:
How to move an XP guest from a 32-bit virtualbox 4.1 host to a 64-bit 4.3 host?
Chris Green
2014-07-17 17:36:53 UTC
Permalink
As per the subject...

I have a 32-bit Windows XP guest running on a 32-bit Linux box
currently with VirtualBox 4.1. I want to move this to a 64-bit Linux
box running VirtualBox 4.3. What's the procedure?
--
Chris Green
e***@public.gmane.org
2014-07-17 18:20:04 UTC
Permalink
Chris, i think you can move it without any problem.

You can't move a 64bit guest to 32bit host.


Best regards.


P.S. If i'm wrong please let me know!

Emiliano



Enviado desde mi BlackBerry de Personal (http://www.personal.com.ar/)

-----Original Message-----
From: Chris Green <cl-***@public.gmane.org>
Date: Thu, 17 Jul 2014 18:36:53
To: <vbox-users-community-5NWGOfrQmneRv+***@public.gmane.org>
Reply-To: Community mailing list of VirtualBox users
<vbox-users-community-5NWGOfrQmneRv+***@public.gmane.org>
Subject: [VBox-users] How to move an XP guest from a 32-bit virtualbox 4.1
host to a 64-bit 4.3 host?

As per the subject...

I have a 32-bit Windows XP guest running on a 32-bit Linux box
currently with VirtualBox 4.1. I want to move this to a 64-bit Linux
box running VirtualBox 4.3. What's the procedure?
--
Chris Green

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
VBox-users-community mailing list
VBox-users-community-5NWGOfrQmneRv+***@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe: mailto:vbox-users-community-request-5NWGOfrQmneRv+***@public.gmane.org?subject=unsubscribe
Chris Green
2014-07-17 19:36:52 UTC
Permalink
Post by e***@public.gmane.org
Chris, i think you can move it without any problem.
You can't move a 64bit guest to 32bit host.
Er, but what do I move to where? I have an empty VirtualBox
installation on the new system, what files do I need to copy across
from the old system and where do I put them? ... and how do I copy
them? Do I need to use VirtualBox to copy them in or can I just copy
them across with any old utility?
--
Chris Green
Gregory Nowak
2014-07-17 19:43:50 UTC
Permalink
Post by e***@public.gmane.org
Chris, i think you can move it without any problem.
You can't move a 64bit guest to 32bit host.
Best regards.
P.S. If i'm wrong please let me know!
Emiliano
Last time I checked, the xml/vbox files weren't compatible between the
GNU/Linux version, and windows version. If that's still correct, your
best options as far as I can tell are to export as an appliance, and
import on the windows box, or to make note of how the guest is
configured, create a new guest on windows with the same config, and
transfer the vdi file over.

BTW, not on topic for this thread, but did you manage to solve your
boot problems from vmdk Emiliano?

Greg
--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager-iDweQDFWK/***@public.gmane.org
Leonardo Carneiro
2014-07-17 19:51:13 UTC
Permalink
yeah. use export appliance and you're good. just be sure to double-check
the path of the files on the destination. by default, it will try to create
the files in the same folder as the source.
Post by Gregory Nowak
Post by e***@public.gmane.org
Chris, i think you can move it without any problem.
You can't move a 64bit guest to 32bit host.
Best regards.
P.S. If i'm wrong please let me know!
Emiliano
Last time I checked, the xml/vbox files weren't compatible between the
GNU/Linux version, and windows version. If that's still correct, your
best options as far as I can tell are to export as an appliance, and
import on the windows box, or to make note of how the guest is
configured, create a new guest on windows with the same config, and
transfer the vdi file over.
BTW, not on topic for this thread, but did you manage to solve your
boot problems from vmdk Emiliano?
Greg
--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.
--
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
VBox-users-community mailing list
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
?subject=unsubscribe
Chris Green
2014-07-18 08:24:10 UTC
Permalink
Post by Leonardo Carneiro
yeah. use export appliance and you're good. just be sure to double-check
the path of the files on the destination. by default, it will try to
create the files in the same folder as the source.
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.

Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.

How can I diagnose this? As I said it's exported from a 4.1.x
VirtualBox and I'm importing it into a 4.3.x one.
--
Chris Green
Chris Green
2014-07-18 08:49:49 UTC
Permalink
Post by Chris Green
Post by Leonardo Carneiro
yeah. use export appliance and you're good. just be sure to double-check
the path of the files on the destination. by default, it will try to
create the files in the same folder as the source.
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
How can I diagnose this? As I said it's exported from a 4.1.x
VirtualBox and I'm importing it into a 4.3.x one.
It can be booted in Safe Mode, so it's not completely dead! :-)
--
Chris Green
Giles Coochey
2014-07-18 09:03:19 UTC
Permalink
Post by Chris Green
Post by Chris Green
Post by Leonardo Carneiro
yeah. use export appliance and you're good. just be sure to double-check
the path of the files on the destination. by default, it will try to
create the files in the same folder as the source.
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
How can I diagnose this? As I said it's exported from a 4.1.x
VirtualBox and I'm importing it into a 4.3.x one.
It can be booted in Safe Mode, so it's not completely dead! :-)
You should troubleshoot what is happening to the guest in the same way
you would if it were a physical box. Review the logs within the guest
(now that you have Safe mode).
For a start I would try uninstalling (in Safe mode) the Virtual Box
additions, rebooting in safe mode again and re-installing the Guest
Additions.

You should also review the logs for Virtualbox, but if you're getting an
error in the guest, as opposed to a Virtualbox / host error then
troubleshooting should be done in the guest.
--
Regards,

Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 8444 780677
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
giles-***@public.gmane.org
Chris Green
2014-07-18 09:56:26 UTC
Permalink
Post by Giles Coochey
Post by Chris Green
Post by Chris Green
Post by Leonardo Carneiro
yeah. use export appliance and you're good. just be sure to double-check
the path of the files on the destination. by default, it will try to
create the files in the same folder as the source.
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
How can I diagnose this? As I said it's exported from a 4.1.x
VirtualBox and I'm importing it into a 4.3.x one.
It can be booted in Safe Mode, so it's not completely dead! :-)
You should troubleshoot what is happening to the guest in the same
way you would if it were a physical box. Review the logs within the
guest (now that you have Safe mode).
I'm not a Windows person at all (background is Sun Solaris and always
Linux on home computers) so it took me a while to unravel things a
bit. I found the minidump file and a utility to read it, the BSOD
says (abbreviated):-

Problem caused by HAL.DLL

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Post by Giles Coochey
For a start I would try uninstalling (in Safe mode) the Virtual Box
additions, rebooting in safe mode again and re-installing the Guest
Additions.
How? I always have trouble with these. I've downloaded them from
virtualbox.org, what do I do with the file?


Thanks for all the help so far.
--
Chris Green
Giles Coochey
2014-07-18 10:08:46 UTC
Permalink
Post by Chris Green
How? I always have trouble with these. I've downloaded them from
virtualbox.org, what do I do with the file?
Uninstalling the existing one can be done via Start --> Settings... -->
Control Panel --> Add / Remove Programs

Locate the Virtualbox Guest Additions and the list and select to Uninstall.

Once the uninstall has completed reboot (again into Safe mode) for good
measure.

I would discourage installing any Virtualbox additions that you have
downloaded, the Virtualbox Guest Additions are provided with the
Virtualbox that you have installed. You install them via Devices -->
"Insert Guest Additions CD image..." then run (double-click) the
VBoxWindowsAdditions.exe that appears on your virtualbox guest CD drive.

Please note that for Windows XP you must install the Guest Additions in
Safe Mode, which is just as well, as it appears that is all you have at
the moment.
--
Regards,

Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 8444 780677
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
giles-***@public.gmane.org
Cliff
2014-07-18 13:42:44 UTC
Permalink
Pardon me for jumping in here, but I question why you say that the Guest Additions must be installed in Safe Mode with XP. I am running XP in VBox on OSx and never have needed to use Safe Mode. They install just fine in normal mode.

Cliff
Post by Chris Green
How? I always have trouble with these. I've downloaded them from
virtualbox.org, what do I do with the file?
Uninstalling the existing one can be done via Start --> Settings... --> Control Panel --> Add / Remove Programs
Locate the Virtualbox Guest Additions and the list and select to Uninstall.
Once the uninstall has completed reboot (again into Safe mode) for good measure.
I would discourage installing any Virtualbox additions that you have downloaded, the Virtualbox Guest Additions are provided with the Virtualbox that you have installed. You install them via Devices --> "Insert Guest Additions CD image..." then run (double-click) the VBoxWindowsAdditions.exe that appears on your virtualbox guest CD drive.
Please note that for Windows XP you must install the Guest Additions in Safe Mode, which is just as well, as it appears that is all you have at the moment.
--
Regards,
Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 8444 780677
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds_______________________________________________
VBox-users-community mailing list
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Giles Coochey
2014-07-18 14:11:48 UTC
Permalink
Post by Cliff
Pardon me for jumping in here, but I question why you say that the Guest Additions must be installed in Safe Mode with XP. I am running XP in VBox on OSx and never have needed to use Safe Mode. They install just fine in normal mode.
Cliff
Well, specifically it is the following advice, taken from:
https://www.virtualbox.org/manual/ch14.html

"For *basic Direct3D support in Windows guests* to work, the Guest
Additions must be installed in Windows "safe mode". Press F8 when the
Windows guest is booting and select "Safe mode", then install the Guest
Additions. Otherwise Windows' file protection mechanism will interfere
with the replacement DLLs installed by VirtualBox and keep restoring the
original Windows system DLLs. "

If you are not using 3D support, then I suppose it doesn't apply, but to
be safe, use safe mode, unless you want to get into a discussion whether
they have Direct3D support enabled or not, and whether they had it
enabled before they migrated or not.
--
Regards,

Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 8444 780677
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
giles-***@public.gmane.org
Cliff
2014-07-18 14:37:19 UTC
Permalink
Ok. I didn’t realize that restriction, but since I’m not using 3D I’ve never run into problems.

Cliff
Post by Cliff
Pardon me for jumping in here, but I question why you say that the Guest Additions must be installed in Safe Mode with XP. I am running XP in VBox on OSx and never have needed to use Safe Mode. They install just fine in normal mode.
Cliff
Well, specifically it is the following advice, taken from: https://www.virtualbox.org/manual/ch14.html
"For basic Direct3D support in Windows guests to work, the Guest Additions must be installed in Windows "safe mode". Press F8 when the Windows guest is booting and select "Safe mode", then install the Guest Additions. Otherwise Windows' file protection mechanism will interfere with the replacement DLLs installed by VirtualBox and keep restoring the original Windows system DLLs. "
If you are not using 3D support, then I suppose it doesn't apply, but to be safe, use safe mode, unless you want to get into a discussion whether they have Direct3D support enabled or not, and whether they had it enabled before they migrated or not.
--
Regards,
Giles Coochey, CCNP, CCNA, CCNAS
NetSecSpec Ltd
+44 (0) 8444 780677
+44 (0) 7983 877438
http://www.coochey.net
http://www.netsecspec.co.uk
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds_______________________________________________
VBox-users-community mailing list
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Chris Green
2014-07-19 09:35:04 UTC
Permalink
Post by Cliff
Pardon me for jumping in here, but I question why you say that the Guest
Additions must be installed in Safe Mode with XP. I am running XP in VBox
on OSx and never have needed to use Safe Mode. They install just fine in
normal mode.
Yes, I (the OP) have always found this too.
--
Chris Green
Gregory Nowak
2014-07-18 19:27:53 UTC
Permalink
Post by Chris Green
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
Keep in mind that when you export to an ova file, the hardware that
the guest sees changes. This is why I suggested you just move the vdi
file, and recreate the config from scratch on the new host.

Greg
--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-manager-iDweQDFWK/***@public.gmane.org
Chris Green
2014-07-19 09:36:23 UTC
Permalink
Post by Gregory Nowak
Post by Chris Green
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
Keep in mind that when you export to an ova file, the hardware that
the guest sees changes. This is why I suggested you just move the vdi
file, and recreate the config from scratch on the new host.
Ah, so I can copy the vdi file and create a new Windows XP guest
specifying that file? OK, I'll try that next.
--
Chris Green
Chris Green
2014-07-19 12:36:52 UTC
Permalink
Post by Chris Green
Post by Gregory Nowak
Post by Chris Green
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
Keep in mind that when you export to an ova file, the hardware that
the guest sees changes. This is why I suggested you just move the vdi
file, and recreate the config from scratch on the new host.
Ah, so I can copy the vdi file and create a new Windows XP guest
specifying that file? OK, I'll try that next.
... and exactly the same thing happens. :-(

I think I had better try installing XP from a CD and then copying the
important bits of user data from the old system.
--
Chris Green
e***@public.gmane.org
2014-07-19 12:48:33 UTC
Permalink
Chris, do you have set a W-xp with 32bit in the new guest?

Do you have any external adapter on this host? Maybe you're getting this problems because of this.

I recently move a vdi file to another host without any problems. I only create a new guest and use the vdi file instead of create one.

Best regards.
Emiliano


Enviado desde mi BlackBerry de Personal (http://www.personal.com.ar/)

-----Original Message-----
From: Chris Green <cl-***@public.gmane.org>
Date: Sat, 19 Jul 2014 13:36:52
To: <vbox-users-community-5NWGOfrQmneRv+***@public.gmane.org>
Reply-To: Community mailing list of VirtualBox users
<vbox-users-community-5NWGOfrQmneRv+***@public.gmane.org>
Subject: Re: [VBox-users] How to diagnosse a BSOD? (was Re: How to move an
XP guest from a 32-bit virtualbox 4.1 host to a 64-bit 4.3 host?)
Post by Chris Green
Post by Gregory Nowak
Post by Chris Green
OK, I did that, exported to a .ova file on the old system, copied the
file to the new system and imported it.
Sadly it BSOD's just as the Windows XP welcome screen appears and
immediately reboots so I can't see what the BSOD says.
Keep in mind that when you export to an ova file, the hardware that
the guest sees changes. This is why I suggested you just move the vdi
file, and recreate the config from scratch on the new host.
Ah, so I can copy the vdi file and create a new Windows XP guest
specifying that file? OK, I'll try that next.
... and exactly the same thing happens. :-(

I think I had better try installing XP from a CD and then copying the
important bits of user data from the old system.
--
Chris Green

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
VBox-users-community mailing list
VBox-users-community-5NWGOfrQmneRv+***@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe: mailto:vbox-users-community-request-5NWGOfrQmneRv+***@public.gmane.org?subject=unsubscribe
Chris Green
2014-07-20 08:32:16 UTC
Permalink
Post by e***@public.gmane.org
Chris, do you have set a W-xp with 32bit in the new guest?
Yes.
Post by e***@public.gmane.org
Do you have any external adapter on this host? Maybe you're getting this problems because of this.
It's a laptop and the original host was a laptop too, though very
different makes/hardware. The XP guest comes from a Dell Vostro, it
was running xubuntu 12.04 but I've upgraded it to 14.04 and brought
the VirtualBox up to date as well. The XP guess still runs OK on that
system.

The destination system is an IBM Lenovo x201i also running xubuntu but
64-bit rather than 32-bit (which the Dell was running).
Post by e***@public.gmane.org
I recently move a vdi file to another host without any problems. I only
create a new guest and use the vdi file instead of create one.
I don't think I've ever had this much hassle before either.

The only thing I can think of is that it doesn't like moving the guest
from a 32-bit host to a 64-bit host though that shouldn't be a problem
I know.

I have another XP guest running on my 64-bit desktop machine, I'll
maybe try the VDI file from that.
--
Chris Green
Continue reading on narkive:
Search results for 'How to move an XP guest from a 32-bit virtualbox 4.1 host to a 64-bit 4.3 host?' (Questions and Answers)
6
replies
Will I be able to work with my Windows files, while using Ubuntu Linux?
started 2010-01-04 04:57:12 UTC
software
Loading...