/build/static/layout/Breadcrumb_cap_w.png

Can't Capture VirtualBox system Image with PXE Boot

I have created a syspreped Windows 7 image as a Virtual Machine using VirtualBox and I am trying to capture the image using K2000 PXE boot. The problem I am having is that it seems not to be seeing the Hard Drive after the PXE loads the .iso to start the capture. I am getting the following:

MEMDISK 3.84 2009-12-18 .........
e820: 0000000000000000000000 0000000000000009fc00 1
.................................................................................. 2
etc

RAMDISK at 0x34b8e000
etc

then it shows
loading boot sector... booting...

That is where it stays. Any Ideas?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: horstj 12 years ago
Brown Belt
0
I am having the same exact problem. I am trying to do an install of Windows XP Pro SP3 and I know that the K2000 will send it successfully to other machines. The problem comes when I am trying to install it to VirtualBox. I am able to PXE boot and start the installations process, but it gets stuck at the same loading boot sector message described above. Does anyone know what to do?
Posted by: dunnpy 12 years ago
Red Belt
0
Sounds like you may be experiencing an issue with storage matrix drivers being incorrect or not present.
I've not had to resolve this for VirtualBox, but similar for physical machines with PXE boot a few years ago.

This link may provide you with a good starting point.

Hope that helps,

Dunnpy
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ