ok, good. Then don't worry about the PXE part you originally brought up, Just know that it will not affect your dhcp service.
-Aaron On Fri, Apr 26, 2013 at 2:51 PM, Alanoud J <[email protected]> wrote: > Actually I don't what do you mean by PXE !!! and I don't have any > provisioning except KVM on both MN and physical computer do I need to use > any other provisioning??? > > > On Fri, Apr 26, 2013 at 9:37 PM, Dmitri Chebotarov <[email protected]> wrote: >> >> Hi Alanoud >> >> PXE is not commonly used with VCL, unless you also have xCAT configured, >> and 'filename' option may be ignored - you can have it in your dhcpd.conf >> file, but it won't be used. >> >> When you make reservation VCL clones/copies VM disks for you and new VM >> then booted from a local disk. There is no need to PXE-boot in this case. >> >> If you are provisioning physical computers with VCL/xCAT then you will >> need PXE-boot and /tftpboot/pxelinux.0 is default location for pxelinux.0 >> file, so it should work OK. >> >> -- >> Thank you, >> >> Dmitri Chebotarov >> VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & >> Messaging >> 223 Aquia Building, Ffx, MSN: 1B5 >> Phone: (703) 993-6175 | Fax: (703) 993-3404 >> >> >> From: Alanoud J <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Friday, April 26, 2013 14:06 >> To: "[email protected]" <[email protected]>, "[email protected]" >> <[email protected]> >> Subject: Re: VCL host name problem >> >> I am using KVM hypervisor. >> >> >> On Thu, Apr 25, 2013 at 4:46 PM, Aaron Peeler <[email protected]> >> wrote: >>> >>> Hello, >>> >>> Which provisioning system are you using? That appears to be a new >>> path, at least I've not seen that one before. >>> >>> Depending on what your using, pxe may not be needed. >>> >>> Thanks, >>> Aaron >>> >>> On Thu, Apr 25, 2013 at 7:18 AM, Alanoud J <[email protected]> wrote: >>> > Greetings, >>> > >>> > >>> > I want to ask you about a problem we faced it after adding a new worker >>> > to >>> > our VCL data base. >>> > After we add the machine we tryed to generate data to add the machine's >>> > information to the dhcpd.config file,the generated data was: >>> > >>> > Data to be added to dhcpd.conf: >>> > >>> > host worker2 { >>> > option host-name "worker2"; >>> > hardware ethernet 64:70:02:11:94:E6; >>> > fixed-address 192.168.1.20; >>> > filename "/tftpboot/pxelinux.0"; >>> > option dhcp-server-identifier 192.168.1.10; >>> > next-server 192.168.1.10; >>> > } >>> > >>> > >>> > >>> > The file name was missing linux-install directory. >>> > >>> > after searching this problem,we have found that the file host name must >>> > be >>> > filename "/tftpboot/linux-install/pxelinux.0"; >>> > So why the file host name does not generated correctly given that we >>> > are >>> > using using VCL 2.3.??? >>> > >>> > best regards >>> > >>> > >>> > Alanoud Aljboor. >>> >>> >>> >>> -- >>> Aaron Peeler >>> Program Manager >>> Virtual Computing Lab >>> NC State University >>> >>> All electronic mail messages in connection with State business which >>> are sent to or received by this account are subject to the NC Public >>> Records Law and may be disclosed to third parties. >> >> > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
