Hi I had configured some test virtual machines a few months back (xpsp3, win2k3 server, Fedora 10, Fedora 11, Gobolinux rel 14 ). Although I have not used the VM's for some time (~6-8months), I have upgraded virtualbox whenever upgrades were made available. All the virtual machines were made with the 3.0 series of virtualbox running on windows xp sp3.
Just prior to the upgrade to 3.1 I attempted to start all the VM's. It seems that they were all broken. I believe the problem was the disk images. Each vm would boot initially and then there would be disk errors towards the end of the boot process (windows machine's blue screened, linux machine's gave sector read errors). I upgraded to 3.1 after uninstalling the 3.0 version thouroughly (removing devices and their inf's). Still the same problem with the disk errors (this was expected as nothing had really changed except the virtualbox version). I re-created a machine using one of the old disk images just in case this would perhaps fix any problems with the machine configuration. Still the same issue. Other types of files on the host machine's physical disk were fine so there was no general disk problem (chkdsk ran without errors). I installed a Fedora 12 vm from the live cd in a new vm fine. As these were just test machines I have been able to delete them with little impact however I would be interested in any comments on this issue. Is this a known or part of a known problem? As an aside, I am also having trouble with fedora installs recognising the DVD iso. If I test the iso prior to installing then the install can't see the dvd unless I mount another iso and then re-mount the install dvd. If I just go straight through to the install, the dvd is seen until the point where install begins and then is not seen anymore. This may be a fedora issue. Regards Rehan > -----Original Message----- > From: [email protected] [mailto:vbox-users- > [email protected]] On Behalf Of Frank Mehnert > Sent: 01 December 2009 08:00 > To: [email protected] > Subject: Re: [vbox-users] RPM for VirtualBox-3.1 will conflict with > older versions of VirtualBox > > Liang, > > On Tuesday 01 December 2009, Liang Suilong wrote: > > I update to VirtualBox-3.1 from VirtualBox yum repo. After > downloading the > > package and starting to setup, yum shows an error. all of files in > > VirtualBox-3.1 conflict with VirtualBox. I believe that the same > problem > > will appear in the SUSE and RHEL and openSUSE. > > > > Here is a log: > http://dl.dropbox.com/u/1352061/virtualbox_conflict.log > > > > The method which I slove the problem is that I install VirtualBox-3.1 > after > > removing VirtualBox. > > > > Then I suggest that virtualbox should add "Obsoletes: VirtualBox" > into RPM > > spec file. Yum will remove VirtualBox automatically before installing > > VirtualBox-3.1. > > Known problem, there is a remark about this conflict on the download > page. > Thanks for the hint. > > > Additionally, VirtualBox 3.1 is still incompatible with kvm_amd > module. > > And this will not change as the kvm_intel and kvm_amd modules enable > the VT-x resp. AMD-V mode during module initalization. This is a > bug in the Linux module (or the Linux distribution which loads these > modules by default). > > Kind regards, > > Frank > -- > Dr.-Ing. Frank Mehnert > > Sitz der Gesellschaft: > Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten > Amtsgericht München: HRB 161028 > Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel > Vorsitzender des Aufsichtsrates: Martin Häring _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
