• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Capturing Image from VirtualBox VHD VM?

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    3
    457
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tesparza
      last edited by

      Hi I created a based Master image in VirtualBox using VHD as storage option. I did all I need to do to the image and I sysprep it. I captured the image into FOG and the image is there. I tested the image by deploying to a computer but when the computer finishes imaging and it reboots. It does no boot. I look in the BIOS and I see that the Boot Option are just ipv4 and ipv6 no hard drive is there, the image deletes the HDD boot option? What can be causing this issue?

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @tesparza
        last edited by

        @tesparza Well we need to get a few things straight here.

        I assume you are building a uefi golden image? When deploying it to a target computer (vm) is that VM in uefi mode? For the uefi firmware, if it detects a uefi boot disk it will add that boot disk into the boot manager. If it can’t locate a valid uefi boot disk, it will only display uefi pxe booting options. Remember that you can only deploy a uefi source image to a uefi target computer, the same holds true for a bios source image, it can only go to a bios based target computer.

        I would start out by making sure your source and target VMs are setup the same way, bios, memory, disk and such. If they are then you can start to debug this issue by scheduling another deploy task to the target VM but before you tick the schedule task button, check the debug checkbox. Now pxe boot the target computer. After a few screens of text on the target computer you should be dropped to a fos linux command prompt. Understand where you should be is on the target computer where you just previously deployed the image, but now you are in debug mode. Key in the following command, lets see what the existing disk structure looks like lsblk

        Once we know that we can debug this issue a bit more.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        T 1 Reply Last reply Reply Quote 2
        • T
          tesparza @george1421
          last edited by

          @george1421 Target is UEFI, image was captured in Legacy VM. Will try again with VM in UEFI mode

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          181

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project