Am 17.12.2011 19:11, schrieb Lucélio Gomes de Freitas:
> Reindl Harald,
>
> I did exactly this.
>
> I updated from Fedora14-x86_64 to Fedora16-x86_64 host, and I thought VirtualBox-4.0 was ok. When I started
> Winvista64 Guest I got the message:
>
> BOOTMGR is compressed Press Ctrl-Alt-Del to restart
>
> I did it, and the Winvista64 boot started again and stoped at the same point. In a loop. I thought that the problem
> was VirtualBox for Fedora14. I removed it. So I installed Virtualbox-4.1-4.1.6 for Fedora16-x86_64. The same thing
> is happening. Why bootmgr has changed? Anybody helps? The guest machine was working untouched in a "Production"
> more than a year. I only updated from Fedora14 to Fedora16.
>
> I got from VirtualBox forum: "we don't really support (fully) the distro branches of VirtualBox".
>
> Would you please help to solve this problem.
sorry i am a vmware-user since years and had virtualbox only
for some months on my notebook - but since we are using vmware
ESX in our company for the whole production-environment i
have no use for other virtualization-software and can not help
you here
maybe i can partially help:
my expierience with virtualbox migrationto another host was that
winxp did not start some times ago because the default-hardware
of the vm has changed for whatever reason and after figure out
the exactly settings from before it was solved
primary a windows problem but on the other hand a reason more
that i do not like vbox - configurations are seperated from
virtual machines - with vmware you have the folder with your
guest and it contains ALL including config (.vmx) and bios-settings
(.nvram) and it does not upgrade/change virtual-hardware in any
way without user-confirmation
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-17-2011, 08:17 PM
Lucélio Gomes de Freitas
VirtualBox installation question.
Michael Cronenworth,
Sorry it should be the way you said but, I had a very bad experience
doing this.
Fact:
I updated from Fedora14-x86_64 to Fedora16-x86_64 host, and I
thought VirtualBox-4.0 was ok. When I started Winvista64 Guest I got
the message:
BOOTMGR is compressed Press Ctrl-Alt-Del to restart
I did it, and the Winvista64 boot started again and stoped at the
same point. In a loop. I thought that the problem was VirtualBox for
Fedora14. I removed it. So I installed Virtualbox-4.1-4.1.6 for
Fedora16-x86_64. The same thing is happening. Why bootmgr has
changed? The guest machine was working UNTOUCHED in a
"Production" more than a year. I only updated from Fedora14 to
Fedora16.
My feeling says that the problem is Windows, but the fact is that I
have to find a solution for it.
Any help would be appreciated.
Thanks.
Em 16-12-2011 20:52, Michael Cronenworth escreveu:
Erik P.
Olsen wrote:
Is it safe to remove the current package
and install the new one? Will
my virtual machines be automatically picked up by the
installation process?
Yes, it is safe. Your virtual machines are not tied to the
package. They are XML files stored in your user's /home directory.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-17-2011, 08:24 PM
Lucélio Gomes de Freitas
VirtualBox installation question.
Germán A. Racca,
Em 16-12-2011 22:47, "Germán A. Racca" escreveu:
> On 12/16/2011 09:34 PM, Reindl Harald wrote:
>>
>>
>> Am 17.12.2011 00:17, schrieb Erik P. Olsen:
>>> On 16/12/11 23:54, Reindl Harald wrote:
>>>>
>>>>
>>>> Am 16.12.2011 23:50, schrieb Erik P. Olsen:
>>>>> I have installed VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64 and
>>>>> have been running it for quite some time. I have
>>>>> now noticed that a new version
>>>>> VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64 is available but not
>>>>> as an update only
>>>>> as a new install. Is it safe to remove the current package and
>>>>> install the new one? Will my virtual machines be
>>>>> automatically picked up by the installation process?
>>>>
>>>> this is linux not windows
>>>> rpm -Uvh "package.rpm" or better "yum --nogpgcheck update package.rpm"
>>>> to update downloaded packages
>>>
>>> My question had nothing to do with windows. I have never run windows
>>> except as virtual machines. and "yum update
>>> VirtualBox*" gets "No Packages marked for Update" so a clean install
>>> is needed.
>>
>> * download the rpm
>> * go in the folder with the rpm
>> * type "yum --nogpgcheck update filename.rpm"
>>
>> yum is not limited to repos
>> if something is installed as rpm a "clean install" is not needed
>> why? because for a rpm a "clean install" does not exist
>> a rpm-package knows which files are form the apckages, which are
>> new and which are obsoleted to remove, that is why a package-manager
>> exists
>>
>> your user-data has nothing to do with the rpm/software/package
>> a virtual machine for vbox/vmware whatever is the same as a doc for
>> openoffice
>> it is yur data and has nothing to do with install/update/uninstall
>> the software
>>
>
> It has to be a "clean install" from my point of view, because he has
> to remove one package and then install the other. Why? Because the
> newer one has a different name. In the format of
> name-version-release.arch, this is:
>
> Old package: VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64
> New package: VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64
I did exaclty this and "BOOTMGR is Compressed", Winvista64 doesn't boot
anymore. Help?
>
> so the old one is called VirtualBox-4.0 and the newer is VirtualBox-4.1.
>
> (BTW, Erik, take into account that F14 is EOL. We are in F16, and the
> same versio of VirtualBox is available).
This was the reason of the update.
>
> HTH,
> Germán.
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-17-2011, 08:31 PM
Lucélio Gomes de Freitas
VirtualBox installation question.
Marko Vojinovic,
It should be the way you say.
Em 16-12-2011 22:48, Marko Vojinovic escreveu:
> On Friday 16 December 2011 23:54:10 Reindl Harald wrote:
>> Am 16.12.2011 23:50, schrieb Erik P. Olsen:
>>> I have installed VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64 and have
>>> been running it for quite some time. I have now noticed that a new
>>> version VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64 is available but
>>> not as an update only as a new install. Is it safe to remove the
>>> current package and install the new one? Will my virtual machines be
>>> automatically picked up by the installation process?
> Yes, it is safe. Your virtual machines will be picked up by the new version if
> you haven't moved their configuration files from the default location.
Be careful..... see my others E-mail on this subject.
>
>> this is linux not windows
>> rpm -Uvh "package.rpm" or better "yum --nogpgcheck update package.rpm"
>> to update downloaded packages
> The "VirtualBox-4.1-<version>" package is not an updated version of the
> "VirtualBox-4.0-<version>", but rather a different package. Note that the "4.1"
> amd "4.0" are a part of the *basename*, rather than a version number of the
> package.
>
> IOW, you can have VirtualBox-4.1 and VirtualBox-4.0 installed simultaneously
> (which may be a bad idea, but that's beside my point). The 4.0 *does* *not*
> get upgraded to 4.1 via a regular yum update or a rpm -Uvh.
>
> As far as VirtualBox is concerned, this situation is exactly the same in both
> Linux and Windows.
>
> HTH, :-)
> Marko
>
>
>
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-21-2011, 01:30 AM
Lucélio Gomes de Freitas
VirtualBox installation question.
Michael Cronenworth,
You are right.
Problem solved. It was a Hardware problem.
I changed the Hard Drive, restored the back-up and all is working right.
Sorry for the noise.
Em 16-12-2011 17:52, Michael Cronenworth escreveu:
> Erik P. Olsen wrote:
>> Is it safe to remove the current package and install the new one? Will
>> my virtual machines be automatically picked up by the installation
>> process?
>
> Yes, it is safe. Your virtual machines are not tied to the package.
> They are XML files stored in your user's /home directory.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-21-2011, 01:36 AM
Lucélio Gomes de Freitas
VirtualBox installation question.
Marko Vajinovic,
Problem solved. It was a Hardware problem.
I changed the Hard Drive, restored the back-up and all is working right.
Sorry for the noise.
Em 16-12-2011 19:48, Marko Vojinovic escreveu:
> On Friday 16 December 2011 23:54:10 Reindl Harald wrote:
>> Am 16.12.2011 23:50, schrieb Erik P. Olsen:
>>> I have installed VirtualBox-4.0-4.0.14_74382_fedora14-1.x86_64 and have
>>> been running it for quite some time. I have now noticed that a new
>>> version VirtualBox-4.1-4.1.6_74713_fedora14-1.x86_64 is available but
>>> not as an update only as a new install. Is it safe to remove the
>>> current package and install the new one? Will my virtual machines be
>>> automatically picked up by the installation process?
> Yes, it is safe. Your virtual machines will be picked up by the new version if
> you haven't moved their configuration files from the default location.
>
>> this is linux not windows
>> rpm -Uvh "package.rpm" or better "yum --nogpgcheck update package.rpm"
>> to update downloaded packages
> The "VirtualBox-4.1-<version>" package is not an updated version of the
> "VirtualBox-4.0-<version>", but rather a different package. Note that the "4.1"
> amd "4.0" are a part of the *basename*, rather than a version number of the
> package.
>
> IOW, you can have VirtualBox-4.1 and VirtualBox-4.0 installed simultaneously
> (which may be a bad idea, but that's beside my point). The 4.0 *does* *not*
> get upgraded to 4.1 via a regular yum update or a rpm -Uvh.
>
> As far as VirtualBox is concerned, this situation is exactly the same in both
> Linux and Windows.
>
> HTH, :-)
> Marko
>
>
>
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
12-21-2011, 01:39 AM
Lucélio Gomes de Freitas
VirtualBox installation question.
Reindl Harald,
Problem solved. It was a Hardware problem.
I changed the Hard Drive, restored the back-up and all is working
right.
Sorry for the noise.
Em 17-12-2011 16:08, Reindl Harald escreveu:
Am 17.12.2011 19:11, schrieb Lucélio Gomes de Freitas:
Reindl Harald,
I did exactly this.
I updated from Fedora14-x86_64 to Fedora16-x86_64 host, and I thought VirtualBox-4.0 was ok. When I started
Winvista64 Guest I got the message:
BOOTMGR is compressed Press Ctrl-Alt-Del to restart
I did it, and the Winvista64 boot started again and stoped at the same point. In a loop. I thought that the problem
was VirtualBox for Fedora14. I removed it. So I installed Virtualbox-4.1-4.1.6 for Fedora16-x86_64. The same thing
is happening. Why bootmgr has changed? Anybody helps? The guest machine was working untouched in a "Production"
more than a year. I only updated from Fedora14 to Fedora16.
I got from VirtualBox forum: "we don't really support (fully) the distro branches of VirtualBox".
Would you please help to solve this problem.
sorry i am a vmware-user since years and had virtualbox only
for some months on my notebook - but since we are using vmware
ESX in our company for the whole production-environment i
have no use for other virtualization-software and can not help
you here
maybe i can partially help:
my expierience with virtualbox migrationto another host was that
winxp did not start some times ago because the default-hardware
of the vm has changed for whatever reason and after figure out
the exactly settings from before it was solved
primary a windows problem but on the other hand a reason more
that i do not like vbox - configurations are seperated from
virtual machines - with vmware you have the folder with your
guest and it contains ALL including config (.vmx) and bios-settings
(.nvram) and it does not upgrade/change virtual-hardware in any
way without user-confirmation
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
VirtualBox installation question.
