Page 5 of 10 FirstFirst ... 34567 ... LastLast
Results 41 to 50 of 95

Thread: Boot an existing Vista/Windows 7 (Physical HD) install with VirtualBox

  1. #41
    Join Date
    Feb 2007
    Beans
    Hidden!

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Quote Originally Posted by run1206 View Post
    riskomt:
    post up your menu.lst output
    type this code into a terminal (Applications -> Accessories -> Terminal),
    Code:
    sudo gedit /boot/grub/menu.lst
    here is mine...
    Code:
    ## ## End Default Options ##
    
    title		Ubuntu 8.10, kernel 2.6.27-11-generic
    uuid		c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5
    kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5 ro splash 
    initrd		/boot/initrd.img-2.6.27-11-generic
    quiet
    
    title		Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
    uuid		c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5
    kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5 ro  single
    initrd		/boot/initrd.img-2.6.27-11-generic
    
    title		Ubuntu 8.10, kernel 2.6.27-7-generic
    uuid		c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5
    kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5 ro quiet splash 
    initrd		/boot/initrd.img-2.6.27-7-generic
    quiet
    
    title		Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
    uuid		c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5
    kernel		/boot/vmlinuz-2.6.27-7-generic root=UUID=c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5 ro  single
    initrd		/boot/initrd.img-2.6.27-7-generic
    
    title		Ubuntu 8.10, memtest86+
    uuid		c6853b2c-6e0b-40b2-ba6a-92ed9b86c6d5
    kernel		/boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title		Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista (Acer Recovery partition)
    root		(hd0,0)
    savedefault
    makeactive
    chainloader	+1
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda2
    title		Windows Vista (Main Partition)
    root		(hd0,1)
    savedefault
    makeactive
    chainloader	+1
    check if the windows section to your menu.lst is similar (savedefault,makeactive, and chainloader)

    (Acer made two partitions, this is why i have a recovery partition and the main partition)
    You didnt specify witch one you want to see. Here is my original menu.lst

    Code:
    # menu.lst - See: grub(8), info grub, update-grub(8)
    #            grub-install(8), grub-floppy(8),
    #            grub-md5-crypt, /usr/share/doc/grub
    #            and /usr/share/doc/grub-doc/.
    
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default		0
    
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout		10
    
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu
    
    # Pretty colours
    #color cyan/blue white/blue
    splashimage=(hd0,4)/boot/grub/splash.xpm.gz
    
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line)  and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    #      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    
    #
    # examples
    #
    # title		Windows 95/98/NT/2000
    # root		(hd0,0)
    # makeactive
    # chainloader	+1
    #
    # title		Linux
    # root		(hd0,1)
    # kernel	/vmlinuz root=/dev/hda2 ro
    #
    
    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ##      kopt_2_6_8=root=/dev/hdc1 ro
    ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ##      alternative=false
    # alternative=true
    
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ##      lockalternative=false
    # lockalternative=false
    
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ##      lockold=true
    # lockold=false
    
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ##      altoptions=(recovery) single
    # altoptions=(recovery mode) single
    
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ##      howmany=7
    # howmany=all
    
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ##      memtest86=false
    # memtest86=true
    
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    
    ## ## End Default Options ##
    
    title		Ubuntu 8.10, kernel 2.6.27-11-generic
    uuid		3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro splash
    initrd		/boot/initrd.img-2.6.27-11-generic
    quiet
    
    title		Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
    uuid		3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    kernel		/boot/vmlinuz-2.6.27-11-generic root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro  single
    initrd		/boot/initrd.img-2.6.27-11-generic
    
    #title		Ubuntu 8.10, kernel 2.6.27-7-generic
    #uuid		3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    #kernel		/boot/vmlinuz-2.6.27-7-generic #root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro quiet splash 
    #initrd		/boot/initrd.img-2.6.27-7-generic
    #quiet
    
    #title		Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
    #uuid		3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    #kernel		/boot/vmlinuz-2.6.27-7-generic #root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro  single
    #initrd		/boot/initrd.img-2.6.27-7-generic
    
    #title		Ubuntu 8.10, memtest86+
    #uuid		3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    #kernel		/boot/memtest86+.bin
    #quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title		Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista
    root		(hd0,0)
    savedefault
    chainloader	+1
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda3
    #title		Windows Vista/Longhorn (loader)
    #root		(hd0,2)
    #savedefault
    #chainloader	+1
    And here is my menu.lst for the virtual machine

    Code:
    # menu.lst - See: grub(8), info grub, update-grub(8)
    #            grub-install(8), grub-floppy(8),
    #            grub-md5-crypt, /usr/share/doc/grub
    #            and /usr/share/doc/grub-doc/.
    
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default		0
    
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout		10
    
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu
    
    # Pretty colours
    #color cyan/blue white/blue
    
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line)  and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    #      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    
    #
    # examples
    #
    # title		Windows 95/98/NT/2000
    # root		(hd0,0)
    # makeactive
    # chainloader	+1
    #
    # title		Linux
    # root		(hd0,1)
    # kernel	/vmlinuz root=/dev/hda2 ro
    #
    
    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ##      kopt_2_6_8=root=/dev/hdc1 ro
    ##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80 ro
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=3a5446b9-3612-4c1d-93bc-f3e4d0db1e80
    
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ##      alternative=false
    # alternative=true
    
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ##      lockalternative=false
    # lockalternative=false
    
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=splash
    
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ##      lockold=true
    # lockold=false
    
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ##      altoptions=(recovery) single
    # altoptions=(recovery mode) single
    
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ##      howmany=7
    # howmany=all
    
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ##      memtest86=false
    # memtest86=true
    
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    
    ## ## End Default Options ##
    
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista
    root		(hd0,0)
    makeactive
    map                (hd0) (hd1)
    map                (hd1) (hd0)
    chainloader	+1
    
    title		Windows Vista
    root		(hd0,1)
    chainloader	+1
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda3
    #title		Windows Vista/Longhorn (loader)
    #root		(hd0,2)
    #savedefault
    #chainloader	+1
    As you see I tried many things. Changing partition, swaping drives. But so far nothing helped. The savedefalut is in the manual written I should remove for safety of my original grub.

  2. #42
    Join Date
    Dec 2006
    Location
    Perth Amboy, NJ
    Beans
    141
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Quote Originally Posted by riskomt View Post

    Code:
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title		Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista
    root		(hd0,0)
    savedefault
    chainloader	+1
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda3
    #title		Windows Vista/Longhorn (loader)
    #root		(hd0,2)
    #savedefault
    #chainloader	+1



    And here is my menu.lst for the virtual machine

    Code:
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda1
    title		Windows Vista
    root		(hd0,0)
    makeactive
    map                (hd0) (hd1)
    map                (hd1) (hd0)
    chainloader	+1
    
    title		Windows Vista
    root		(hd0,1)
    chainloader	+1
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda3
    #title		Windows Vista/Longhorn (loader)
    #root		(hd0,2)
    #savedefault
    #chainloader	+1
    As you see I tried many things. Changing partition, swaping drives. But so far nothing helped. The savedefalut is in the manual written I should remove for safety of my original grub.
    why is your Vista partition commented out?
    unless (hd0,2) doesn't map directly to your Windows partition....

    i don't recall having 2 menu.lst files when i virtualized
    Welcome to the world of Open Source!!!
    Linux User #471120 Ubuntu User #21997
    Jaunty Jackalope 9.04

  3. #43
    Join Date
    Feb 2007
    Beans
    Hidden!

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Quote Originally Posted by run1206 View Post
    why is your Vista partition commented out?
    unless (hd0,2) doesn't map directly to your Windows partition....

    i don't recall having 2 menu.lst files when i virtualized
    Its probably because the second menu.lst is burned in the grub.iso that is mounted in the vbox cd rom. The second one is disabled because in my original grub I use the first one to boot to Vista so I expected the second one is only a partition without any system on it. Its the data partition of mine.

  4. #44
    Join Date
    May 2008
    Beans
    99
    Distro
    Ubuntu Karmic Koala (testing)

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Made a couple edits and confirmed it works the same with Windows 7.

  5. #45
    Join Date
    Dec 2006
    Location
    Perth Amboy, NJ
    Beans
    141
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Quote Originally Posted by canabal View Post
    Made a couple edits and confirmed it works the same with Windows 7.
    nice
    do you still have the reactivation problems in Windows 7, or is that cleared up in the new version?
    Welcome to the world of Open Source!!!
    Linux User #471120 Ubuntu User #21997
    Jaunty Jackalope 9.04

  6. #46
    Join Date
    May 2008
    Beans
    99
    Distro
    Ubuntu Karmic Koala (testing)

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    So far no issues, but on vista mine did not pop up for a couple weeks. If it does appear I will update.

    Also I am running this from Jaunty and it is working fine.

  7. #47
    Join Date
    Jan 2009
    Beans
    7

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    Hi guys this has been a great walkthrough. I followed everything and seem to stumble upon the last bit.... which is to boot Vista in VB.

    The funny thing is there is no error messages whatsoever, it simply got STUCK in the Vista splash screen, the one that appears just before the desktop is being loaded and shown.

    If anyone have any idea what might be the problem?

    I'm guessing its related to my hardware.... but no idea what and why.

  8. #48
    Join Date
    Jan 2009
    Beans
    7

    Re: Boot an existing Vista (Physical HD) install with VirtualBox

    I discovered that my vmdk file is not classed as Writethrough, its just Normal.

    Would this be the cause? I have been searching for methods to create or modify the vmdk to make it "Writethrough" but I couldn't find anything useful.

    Would be great if someone can help out a bit.

    Edited:

    I notice that Vista (VM) loads the vmdk hardisk for a short while, about 2 seconds, then all activities stopped. And since Vista is not able to load whatever files it needs, its just stuck at the splash screen forever.

    It seems very weird to me that the disk can load everything it needs right up to the splash screen, coz I assume being able to get to the splash screen means VirtualBox already have access to the actual partition of my physical hardisk via vmdk.
    Last edited by GapToN; April 22nd, 2009 at 03:56 PM.

  9. #49
    Join Date
    Nov 2008
    Beans
    12

    Re: Boot an existing Vista/Windows 7 (Physical HD) install with VirtualBox

    I am glad I found this tutorial. I think it is great and I am happy to see so many people are getting this to work. Hopefully I will soon join the ranks of the successful. In the mean time...

    When I run the second command in step two, I am greeted with,

    "Error opening the raw disk '/dev/sda': VERR_ACCESS_DENIED
    The raw disk vmdk file was not created"

    My vista partition is actually on /dev/sda1, but I get the same message when running that.

    "Error opening the raw disk '/dev/sda1': VERR_ACCESS_DENIED
    The raw disk vmdk file was not created"

    I have two 250 gig hd's with windows on the first and Ubuntu on the second. I have made the ntfs file system writable and can write to it. Any ideas what I might be lacking???

    BTW, the command as I ran it was,

    Code:
    VBoxManage internalcommands createrawvmdk -filename ~/.VirtualBox/WinHD.vmdk -rawdisk /dev/sda1 -partitions 2 -relative -register
    UPDATE: Oops! I seem to have skipped over "Log out and log back in here... " Now the message has changed. See below.
    Last edited by flabbergasted; May 2nd, 2009 at 12:59 AM.

  10. #50
    Join Date
    Nov 2008
    Beans
    12

    Re: Boot an existing Vista/Windows 7 (Physical HD) install with VirtualBox

    OK, I have now successfully gone through the entire setup, but now when I try to start the virtual Vista I am greeted with,

    "Error 15, file not found


    Press any key to continue....."

    What file? All of the steps 1 thru 4 went well. Step 6 is now my first hickup and I am now stuck. Any help?

Page 5 of 10 FirstFirst ... 34567 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •