|
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. thanks in advance. Em 16-12-2011 20:54, Reindl Harald escreveu: 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 -- Lucélio Gomes de Freitas ETFCSF-> U.G.F.-> P.U.C.(RJ) Engº, Analista Suporte(Free Mind). Email: aa.lucelio@xxxxxxxxx Tel: 55 0XX 21 85964911 |
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx 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
