Unfortunately, it seems like it did effect the KVMs. Probably even the VMs but I am not sure yet. Can anyone give me suggestions why the KVM Ethernet bridge is not working while Proxmox can ping Google and it's portal is working?<div>
<br></div><div>I actually added a second NIC card to the KVM but it still doesn't obtain DHCP.</div><div><br></div><div>Thanks,<br><br><div class="gmail_quote">On Sat, May 21, 2011 at 3:07 AM, Bruce B <span dir="ltr"><<a href="mailto:bruceb444@gmail.com">bruceb444@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Thanks. So, it did break the vmbidge and the whole GUI for proxmox.<div><br></div><div>/etc/udev/rules.d/70-persistent-net.rules was the file I edited and commented all the e1000 and igb lines. Restarted and now I can ping and see the Proxmox GUI. I checked the persistent-net file again but there are no lines added and my commented lines are still there. Hope this doesn't change anything in the short or long run.</div>
<div><br></div><div><br></div><div>Much thanks for all the great tips I got here.</div><div><div><br></div><div><br><br><div class="gmail_quote"><div class="im">On Wed, May 18, 2011 at 4:34 AM, Felix Krohn <span dir="ltr"><<a href="mailto:felix.krohn@ovh.net" target="_blank">felix.krohn@ovh.net</a>></span> wrote:<br>
</div><div><div></div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Bruce B <<a href="mailto:bruceb444@gmail.com" target="_blank">bruceb444@gmail.com</a>> [2011-05-17 17:54]:<br>
<div>> So, if I take out the HDDs and attach to the new board, should I expect<br>
> Proxmox to come up fine and all the KVMs and VMs to run smoothly after it<br>
> finds the new board?<br>
<br>
</div>In my experience yes, although udev might rename your network<br>
interfaces, thus breaking vmbridge connectivity.<br>
Cleaning up /etc/udev/rules.d/*persistent-net.rules (removing the lines<br>
with the old MAC address) should be enough to fix or prevent this (be<br>
careful, this line will be re-created during boot-up)<br>
<br>
About the raid thing: don't use fakeraid :)<br>
<br>
As Martin says, real hardware RAID is the best option, but that doesn't<br>
mean that regular Linux SoftRaid (mdadm) won't work - it does work, but<br>
isn't supported officially.<br>
<br>
Best regards,<br>
<font color="#888888">Felix<br>
</font></blockquote></div></div></div><br></div></div>
</blockquote></div><br></div>