straight advise how to update 1.5.4 to newest version?

[Xenia]

Hi all,

even after searching through forum and FAQ I am not clear as how to exactly update vb on my windows vista host.

What I already know: please correct me if I am wrong:

I need to resolve the saved state of any guest system before updating.
I need to uninstall vb 1.5.4 first

What I do not know for sure:

1. I remember there was an issue regarding ACPI and IO APIC, just can't remember which one. Do both have to be activated during install?

2. Will the guest systems work after updating, including os and all applications? (I would not want to have to activate the windows guest os and applications. Some of the application setups are complicated as well.)

3. Will the shared folders be still available?

If I should have overlooked a place with instructions for updating please link me there.

Thanks in advance,

Xenia

[Sasquatch]

The upgrade is pretty straight forward. Just install the new version, but as always, a backup is advised. Check the VM settings after the upgrade, especially the PIIX setting on the Advanced tab. The GA should be the same version as the VB version you are running, so upgrade them too. SF should work from the beginning though, but it not guaranteed.

[Xenia]

Thanks a lot for your reply! Unfortunately I read the notifying message only now, as it had gotten caught up in the mail providers quarantine.

Just install the new version, but as always, a backup is advised.

Sorry if it sounds stupid, but what exactly should I backup. Is it sufficient to back up the user/.virtualbox folder or do I have to backup the program files/innotek virtualbox folder also? (shared folder info seems to be located there?)

The GA should be the same version as the VB version you are running, so upgrade them too.

I remember having read sth. about issues of not having uninstalled the old GA version and resulting trouble of CPU usage. Do I have to uninstall the old GA first and how do I do that?

Check the VM settings after the upgrade, especially the PIIX setting on the Advanced tab

Ehhm, what is PIIX? Again so sorry, it is probably obvious but I just cannot guess, even after consulting the manual. Same is true for the abbreviation SF (science fiction? )

Thanks for caring,

Xenia

[mpack]

Ehhm, what is PIIX?

He means, check the IDE Hard Disk Controller setting in the Advanced tab. The default selection for this changed between versions and some already created guests (eg. XP) don't like that at all (you get BSOD during boot). Make sure the selection is the same as the old VM, and don't enable SATA. Look in the old .xml file for the correct setting.

[Xenia]

@mpack

Thanks for translation

The default selection for this changed between versions and some already created guests (eg. XP) don't like that at all (you get BSOD during boot).

Good point, I actually do have a WinXP Pro VM. So far it is the only guest present and the vdi that contains it is marked as primary master. Will the default in the new version be different?

[mpack]

Will the default in the new version be different?

I can't say for sure, since I've never used your old VBox version. However, from comments on these forums I believe the IDE controller type default did change sometime around v1.6.0. Note that the default is only relevant when creating new VMs - existing VMs are not affected.

The important thing is to not rely on the default: instead you should explicitly ensure that it is the same as in the old VM. Unlike me, you are in a position to check precisely what the old value was, since you are able to look inside the old VMs .xml settings file.

[Xenia]

Ok, I think I got that one.

I was able to open the vm.xml (first time I opened xml )
I guess the mentioned hard disk specification are these:

Code: Select all

HardDiskAttachment bus="ide0" device="master" hardDisk="{fef1e74b-f7e4-4263-b4e6-880d64c782b1}"

"ide0" is probably equal to primary master. Will I be asked for it during installation? Probably not for already existing vms? - Means I only have to check the settings in the advanced tab of the old vm after installation is completed. (No tampering with the xml-file. I would not know how to change an xml-file anyway, so far I can only read it.) Please tell me if I am wrong.

Thanks again,
Xenia

[mpack]

I guess the mentioned hard disk specification are these:

No, that's the wrong section I'm afraid. Look instead for the <IDEController type="PIIX4"> line (yours might have a different name in the quotes). Whatever it is, that's what to need to select in the IDE Controllers list in the advanced tab.

[Xenia]

Look instead for the <IDEController type="PIIX4"> line (yours might have a different name in the quotes)

I start a little bit like moving in a fog... as I can't find any mentioning of the above.

I found 2 VB xml-files:

1. user/.VirtualBox/VirtualBox.xml
2. user/.VirtualBox/Machines/Windows XP Pro SP2/Windows XP Pro SP2.xml

Maybe I do not see the obvious, so I copy both below.

The nearest I found was the part in the first xml of global configuration that says

Code: Select all

HardDisk type="normal"

This is however not specific of the guest system.

Will I have to change the newly created xml after new installation or just check the details from within the program in the Advanced tab? However, within VB the tab Advanced/Harddisks shows no such choice either .

1. user/.VirtualBox/VirtualBox.xml:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> 
- <!--  innotek VirtualBox Global Configuration 
  --> 
- <VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.2-windows">
- <Global>
- <ExtraData>
  <ExtraDataItem name="GUI/RegistrationData" value="triesLeft=0" /> 
  <ExtraDataItem name="GUI/LastWindowPostion" value="438,79,770,541" /> 
  <ExtraDataItem name="GUI/SuppressMessages" value="remindAboutMouseIntegrationOn" /> 
  <ExtraDataItem name="GUI/Input/HostKey" value="163" /> 
  <ExtraDataItem name="GUI/Input/AutoCapture" value="false" /> 
  <ExtraDataItem name="GUI/LastVMSelected" value="{c5d61d9c-0b78-4125-bc30-182531a54a0e}" /> 
  </ExtraData>
- <MachineRegistry>
  <MachineEntry src="Machines\Windows XP Pro SP2\Windows XP Pro SP2.xml" uuid="{c5d61d9c-0b78-4125-bc30-182531a54a0e}" /> 
  </MachineRegistry>
- <DiskRegistry>
- <HardDisks>
- <HardDisk type="normal" uuid="{fef1e74b-f7e4-4263-b4e6-880d64c782b1}">
  <VirtualDiskImage filePath="VDI\Windows XP Pro SP2.vdi" /> 
  </HardDisk>
  </HardDisks>
- <DVDImages>
  <Image src="C:\PROGRA~1\INNOTE~1/VBoxGuestAdditions.iso" uuid="{d679ec91-e024-4fa6-8414-f45f86bf083c}" /> 
  </DVDImages>
  <FloppyImages /> 
  </DiskRegistry>
  <USBDeviceFilters /> 
  <SystemProperties HWVirtExEnabled="false" LogHistoryCount="3" defaultMachineFolder="Machines" defaultVDIFolder="VDI" remoteDisplayAuthLibrary="VRDPAuth" /> 
  </Global>
  </VirtualBox>

2. user/.VirtualBox/Machines/Windows XP Pro SP2/Windows XP Pro SP2.xml:

Code: Select all

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> 
- <!--  innotek VirtualBox Machine Configuration 
  --> 
- <VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.2-windows">
- <Machine OSType="winxp" currentStateModified="false" lastStateChange="2008-11-10T12:58:34Z" name="Windows XP Pro SP2" stateFile="Snapshots\{c5d61d9c-0b78-4125-bc30-182531a54a0e}.sav" uuid="{c5d61d9c-0b78-4125-bc30-182531a54a0e}">
- <ExtraData>
  <ExtraDataItem name="GUI/SaveMountedAtRuntime" value="no" /> 
  <ExtraDataItem name="GUI/LastCloseAction" value="save" /> 
  <ExtraDataItem name="GUI/LastWindowPostion" value="0,0,1260,734" /> 
  <ExtraDataItem name="GUI/Fullscreen" value="off" /> 
  <ExtraDataItem name="GUI/Seamless" value="off" /> 
  <ExtraDataItem name="GUI/AutoresizeGuest" value="off" /> 
  <ExtraDataItem name="VboxInternal/PDM/HaltOnReset" value="1" /> 
  </ExtraData>
- <Hardware>
- <CPU>
  <HardwareVirtEx enabled="false" /> 
  </CPU>
  <Memory RAMSize="512" /> 
- <Boot>
  <Order device="Floppy" position="1" /> 
  <Order device="DVD" position="2" /> 
  <Order device="HardDisk" position="3" /> 
  </Boot>
  <Display MonitorCount="1" VRAMSize="8" /> 
  <RemoteDisplay authTimeout="5000" authType="null" enabled="false" port="3389" /> 
- <BIOS>
  <ACPI enabled="true" /> 
  <IOAPIC enabled="true" /> 
  <Logo displayTime="0" fadeIn="true" fadeOut="true" /> 
  <BootMenu mode="messageandmenu" /> 
  <TimeOffset value="0" /> 
  <PXEDebug enabled="false" /> 
  </BIOS>
- <DVDDrive passthrough="true">
  <HostDrive src="F:" /> 
  </DVDDrive>
  <FloppyDrive enabled="true" /> 
- <USBController enabled="true" enabledEhci="false">
  <DeviceFilter active="false" name="USB Token [0004]" product="USB Token" productid="0300" remote="no" revision="0004" vendorid="04B9" /> 
  </USBController>
- <Network>

- <Adapter MACAddress="080027354E7F" cable="true" enabled="true" slot="0" type="Am79C973">
  <NAT /> 
  </Adapter>
  <Adapter MACAddress="0800276FE831" cable="true" enabled="false" slot="1" type="Am79C973" /> 
  <Adapter MACAddress="0800279C1A54" cable="true" enabled="false" slot="2" type="Am79C973" /> 
  <Adapter MACAddress="080027FF29E1" cable="true" enabled="false" slot="3" type="Am79C973" /> 
  </Network>
- <Uart>
  <Port IOBase="0x3f8" IRQ="4" enabled="true" hostMode="Disconnected" slot="0" /> 
  <Port IOBase="0x3f8" IRQ="4" enabled="false" hostMode="Disconnected" slot="1" /> 
  </Uart>
- <Lpt>
  <Port IOBase="0x378" IRQ="4" enabled="false" slot="0" /> 
  <Port IOBase="0x378" IRQ="4" enabled="false" slot="1" /> 
  </Lpt>
  <AudioAdapter driver="null" enabled="true" /> 
- <SharedFolders>
  <SharedFolder hostPath="C:\DATEIEN" name="DATEIEN" /> 
  </SharedFolders>
  <Clipboard mode="Bidirectional" /> 
  </Hardware>
- <HardDiskAttachments>
  <HardDiskAttachment bus="ide0" device="master" hardDisk="{fef1e74b-f7e4-4263-b4e6-880d64c782b1}" /> 
  </HardDiskAttachments>
  </Machine>
  </VirtualBox>

[mpack]

VirtualBox.xml is for global vbox settings applying to all VMs. For example, the list of all registered virtual disk IDs is stored here. Nothing about the prescription for any particular VM should be found here.

Ok, now looking at the XP .xml - you are right, I can't see the IDE controller type setting either. I guess that means that the choice was hardcoded in v1.5.4 days (no option to store). Perhaps a look at the VBox release history will tell you what the option used to be.

Have you actually tried just creating a VM with one of the older IDE controllers (definitely not SATA), and see if it boots? You can see the other major required settings (eg. MAC address, ram size) there in the XML. It's important to get these right, otherwise XP will ask for reactivation.

[Xenia]

It's important to get these right, otherwise XP will ask for reactivation.

That is why I stick to this until it gets clear and why I am extremely thankful for any help on this. It sounds as if you had experienced some difficulties in this area yourself. For me, I just hate to call MS and explain why I want to use a program I bought

Also - I use some pretty exotic professional software with hardware dongles that I have to get working and others where you have to call the owner for each new install, again not really elegant solutions...

Have you actually tried just creating a VM with one of the older IDE controllers (definitely not SATA), and see if it boots? You can see the other major required settings

Are you talking about doing so in VB 1.5.4 or in the latest version? I have not yet installed 2.0.4. Before I proceed I want to be absolutely sure not to mess up things.

How would I try to create a VM with one of the older IDE controllers? Is this depending on the actual hardware I use (which is modern) or would this be virtual? Sorry, the borderline between virtual and real sometimes blurs a little for me when it comes to VMs...

I still do not know WHEN and WHERE to adjust the settings. During installation process, from within the program or by editing the newly created xml-file?

[mpack]

Are you talking about doing so in VB 1.5.4 or in the latest version?

I'm talking about installing the new version. In the end, the only way to find out if you have a problem or not is try it and see. As long as you keep backups (and do NOT reactivate Windows if it asks you to!), you should not have any unrecoverable problem.

How would I try to create a VM with one of the older IDE controllers?

I've already told you where the IDE Controllers selection is in the latest GUI version. One of the controller selections is correct: it is easy enough to try them all one at a time until Windows boots. Before booting you should make sure that the MAC address is per the old .xml file as this is a prime cause of reactivation messages.

Is this depending on the actual hardware I use (which is modern) or would this be virtual? Sorry, the borderline between virtual and real sometimes blurs a little for me when it comes to VMs...

It's actually very simple: the hardware and OS used by your host PC is irrelevant. The only hardware which the guest sees is the pretend hardware simulated by the VM software (VBox in this case). Ok, your host hardware must be physically capable of emulating the guest hardware (eg. you can't fill a simulated 200GB drive if the host only has a 60GB host HDD), but other than that the host hardware doesn't matter a bit.

When creating a new VM you use the Virtualbox dialogs to specify what hardware exists in this "pretend PC" - a serial port, a hard disk (or two) of this size, a network card of this type, an IDE controller of that type... etc etc. It's a bit like rolling for character traits in a dungeons and dragons game. Once you've designed the virtual machine you want, you run it for the first time - at which point it's a blank machine and you need to install an OS before you can do much. After that most problems come from the OS (eg. VBox will let you change the hardware prescription after the OS is installed, but the OS itself might object, eg. XP may require reactivation).

I suggest you start giving some of these things a try. You learn by doing, and the whole joy of VMs is that you can "do" without damaging your host.
Just (as I said before), make backups before doing anything, and ignore any reactivations requests (restore from the backup, fix the hardware change that caused the request, try again).

[Xenia]

Merci beaucoup.

In general I was aware of the virtualisation principle. Nevertheless I somehow became confused concerning IDE-controllers. And it is certainly my favorite way to learn by doing, especially when it comes to computers.

I was so hesitant here because of some possible consequences I wanted to absolutely avoid.

So your two most important advises for me seem to be:
firstly to backup not only the old version, but each and every step inbetween changes of the new one, and secondly to ignore any activation demands that might occur.

I have to apologize: I am a simple user. My creative work does not go into computers, nevertheless I am using them as an important tool ever since there are PCs available. I have a tendency to use cool tools (like VB) that are seldom used by simple users. The only disadvantage is that I have to put up with looking stupid. But it's worth it.

Thanks again for your extended patience.

[mpack]

So your two most important advises for me seem to be:
firstly to backup not only the old version, but each and every step inbetween changes of the new one, and secondly to ignore any activation demands that might occur.

The second bit of advice - yes.

The first bit - your interpretation seems slightly over the top for me. I would just keep one "known to be working" old version around as a backup. New versions you create from there will either be working or non-working. If they are working then you are done (but I'd still keep the backup for a while). If they are non-working then there's no point in making a backup of them.

[Xenia]

@sasquatch @mpack

Just wanted to report, esp. for anyone wanting to perform the same update from 1.5.4 to latest version:

Installation went smoothe.
According to sas' recommendation I looked up the tab "General/Advanced/IDE-Controler of guest" and got the choice between 2 options: PIXX3 and PIXX4. (The choice of IDE controler was not included in version 1.5.4 altogether.) I chose the default PIXX3 and the WinXP Pro guest started properly without any activation request. Dto. all software.

The only little bit that did not work out immediately was the installation of GA.
When clicking Device/Install Guest Additions nothing happend. After manual mounting and clicking VBWindowsAdditions.exe nothing happened either. After rebooting and retrying with the exe-file the installation routine finally started.

The new version seems to be a real improvement, especially regarding USB control which used to be somewhat unnerving. Great now.