<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)">  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=WordSection1> I would imagine it would be best to submit a bug report directly to redhat’s beta website.<o:p></o:p> <o:p> </o:p> <a href="https://bugzilla.redhat.com/">https://bugzilla.redhat.com/</a><o:p></o:p> <o:p> </o:p> <o:p> </o:p> Eric Conrad Senior Client Services Technician 3333 Susan Street Costa Mesa, CA 92626 714.885. Office <a href="http://www.emulex.com/">http://www.emulex.com</a> <a href="http://www.emulex.com/"><img border=0 width=175 height=39 id="Picture_x0020_1" src="cid:image001.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/logo.gif"></a> <a href="http://www.twitter.com/emulex"><img border=0 width=27 height=42 id="Picture_x0020_2" src="cid:image002.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/twitter.gif"></a><a href="http://www.friendfeed.com/emulex"><img border=0 width=34 height=42 id="Picture_x0020_3" src="cid:image003.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/friendfeed.gif"></a><a href="http://www.google.com/reader/shared/emulexinc"><img border=0 width=31 height=42 id="Picture_x0020_4" src="cid:image004.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/reader.gif"></a><a href="http://www.facebook.com/pages/Emulex-Corporation/116933412473"><img border=0 width=35 height=42 id="Picture_x0020_5" src="cid:image005.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/facebook.gif"></a><a href="http://www.slideshare.net/emulex"><img border=0 width=28 height=42 id="Picture_x0020_6" src="cid:image006.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/slideshare.gif"></a><a href="http://www.emulex.com/rss.xml"><img border=0 width=33 height=42 id="Picture_x0020_7" src="cid:image007.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/rss.gif"></a><a href="http://www.youtube.com/EmulexVideo"><img border=0 width=29 height=42 id="Picture_x0020_8" src="cid:image008.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/youtube.gif"></a><a href="http://www.emulex.com/resources/blogs.html"><img border=0 width=28 height=42 id="Picture_x0020_9" src="cid:image009.gif@01CB348F.0064BA00" alt="http://cmw3wbd1.emulex.com/files/signature/blog.gif"></a><o:p></o:p> <o:p> </o:p> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: rhelv6-beta-list-bounces@redhat.com [mailto:rhelv6-beta-list-bounces@redhat.com] On Behalf Of gregwm Sent: Thursday, August 05, 2010 11:05 AM To: rhelv6-beta-list@redhat.com Subject: Re: [rhelv6-beta-list] rhel6 remote installs not working<o:p></o:p> </div> <o:p> </o:p> should i consider items sent to this list to be adequately brought to redhat's attention? fine with me to consider rhel6 unready for prime time and just not worry about it personally, but i am curious if the problems i've reported on this list get to the developers attention in due time, or if that will only happen if i report them via some other channel?<o:p></o:p> <div> On Sun, Aug 1, 2010 at 6:55 PM, gregwm <<a href="mailto:rhelv6-beta-list@greatlakedata.com">rhelv6-beta-list@greatlakedata.com</a>> wrote:<o:p></o:p> i'm trying to do remote installs onto 2 sun x2100 m2's and a sun x2100 in a datacenter. both m2's get stuck "Waiting for NetworkManager to configure eth0"(or eth1)..."There was an error configuring your network interface." the x2100 does not get caught there, it asks for the nfs server information, but it can't seem to find the server nfs directory. when retrying, it seems images/install.img always gets appended to the directory name, but adding those names at the nfs server doesn't help (lacking a LOM the x2100 is thus stuck until human hands are available). here's what i give via either grub or pxe:<o:p></o:p> <ul type=disc> <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto; mso-list:l0 level1 lfo1'>r6.vmlinuz initrd=r6.initrd.img lang=en_US keymap=us ksdevice=eth1 netmask=255.255.255.240 gateway=192.168.0.245 dns=192.168.0.244 ip=192.168.0.246 hostname=bleep quiet panic=30 vnc vncpassword=foo askmethod<o:p></o:p></li> </ul> if there's a better way for me to be trying to do this please let me know. however running rhel5 remote installs on the same machines in the same environment and with the same inputs does not encounter any of these problems.<o:p></o:p> </div> <o:p> </o:p> </div> </body> </html>