Page 1 of 1

Issue with PXE inside of virtualbox

Posted: 4. Jun 2010, 19:56
by apastsuzak
Since I upgraded to VirtualBox 3.2 and later to 3.2.2. I have been unable to PXE my VM off of a Novell Zenworks Imaging server.

With 3.1.8 I had no issues at all. The error I am getting is:

Error: 72 - The Universal Network Driver (UNDI) could not be started.

I have attached a screenshot.

Has anyone else seen this error?

Re: Issue with PXE inside of virtualbox

Posted: 15. Jun 2010, 10:26
by pcjohn
I have the exact same problem, but no solution :(

Re: Issue with PXE inside of virtualbox

Posted: 16. Jun 2010, 11:29
by Technologov
open bug report in bugzilla.

Re: Issue with PXE inside of virtualbox

Posted: 16. Jun 2010, 15:24
by Lelik
Unable to reproduce this UNDI driver problem, downloaded ZENworks evaluation copy and I can boot images successfully. Can you attach the failing VM xml config please?

Re: Issue with PXE inside of virtualbox

Posted: 21. Jun 2010, 09:57
by frank
There is one response to the public ticket saying that this was due to a broken PXE version of Fedora.

Re: Issue with PXE inside of virtualbox

Posted: 23. Jun 2010, 09:56
by pcjohn
I'm using ZENworks 7 imaging under Novell Netware, so I can't see how an update to Fedora could possibly help me, any other suggestions? or do I have to downgrade?

Re: Issue with PXE inside of virtualbox

Posted: 23. Jun 2010, 10:18
by pcjohn
Lelik wrote:Unable to reproduce this UNDI driver problem, downloaded ZENworks evaluation copy and I can boot images successfully. Can you attach the failing VM xml config please?
See the attached file. The VM is used to maintain a template for a universal image that I use in a ZENworks environment, it worked perfectly before I upgraded to version 3.2 just like what apastsuzak says, but now I can't use PXE-boot to make the image anymore I've been forced to use the ZENworks bootcd.iso instead that works but it's not ideal.

Re: Issue with PXE inside of virtualbox

Posted: 29. Jun 2010, 10:19
by frank
We were finally able to reproduce and fix this problem. The fix will be included in the next maintenance release. Thanks for this report!