On 24/11/2011 20:16, Raphael Paiva wrote:
My scenario is this: I have two virtual machines. The first one is an ubuntu server with two network interfaces (eth1 and eth2). The eth1 interface is connected to the Internet and is it's running NAT, the eth2 interface is running multiple services (PXE, TFTP, DNS, SSH) and it's configured as internal network. The second virtual machine (node1) is an ubuntu desktop that has access to the Internet through the server. I'm trying to boot node1 via network (PXE), but only appear a black screen and nothing happen. I read the VirtualBox tutorial and I discovered the PXE only work in NAT mode, but I don't understand the file named "vmname.pxe". Is necessary to create it? How? Which the content of it? Do I have to put it into witch directory? Server Virtual Machine directory or physical machine directory? The file "VirtualBox.xlm" refers to physical machine, right? Is there some tutorial that explains this process?



The VirtualBox tutorial only says:
"PXE booting is now supported in NAT mode. The NAT DHCP server provides a boot file name of the form vmname.pxe if the directory TFTP exists in the directory where the user's VirtualBox.xml file is kept. It is the responsibility of the user to provide vmname.pxe."


It is _not_ to say that PXE is _only_ supported by NAT mode. You can PXE boot a virtual host on any active network interface. However, the DHCP options for PXE would need to be provided to the PXE host that is booting up - so you might need to use your own DHCP server where you can support those DHCP option parameters.

Hope this helps.

--
Best Regards,

Giles Coochey
NetSecSpec Ltd
UK Mobile: +44 7983 877 438
ES Mobile: +34 639 362 546
Business Email: [email protected]
Email/MSN/Live Messenger: [email protected]
Skype: gilescoochey

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to