On 11/03/2010 02:25 PM, Alexey Eromenko wrote:
> On Wed, Nov 3, 2010 at 11:11 AM, Satz Klauer<[email protected]>  
> wrote:
>> Hi,
>>
>> I use following configuration and have set it up according to the
>> VirtualBox manual:
>>
>> - my host system is Fedora 13 with latest VirtualBox (including kernel
>> dirvers) successfully installed
>> - the computer itself is a dual boot system with grub
>> - from the Fedora system on /dev/sda2 I want to boot the Windows
>> partition on /dev/sda1 (and have created the related .vmdk files that
>> do not act as virtual filesystem but point to /dev/sda)
>>
>> Now when I boot into /dev/sda1 with my Windows system VirtualBox hangs
>> with nearly no CPU usage. I get a 0% progress bar in front of the
>> black window that shows the VM where Windows should start and an other
>> progress bar in VirtualBox window which shows me "step 2/2" - but
>> nothing happens.
>>
>> I'm running VirtualBox as root so that there is access to /dev/sda.
>>
>> What could be the reason for these problems?
>>
>> Mike
>
> 1. Where from you installed ?
>
> 2. Please attach / upload VBox.log, if this gets created at all.
> Since your problem happens very early, it may not happen.
>
I have tried this before also.
I had a currently installed windows XP (update 3) from
CD. I also followed similar steps of creating a vmdk for
sda1. When I booted the vmdk on VBox, it hung.
You must know that windows detects change of hardware
(VBox != Real Hardware of currently installed windows on sda1).


------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to