On Thu, Nov 20, 2008 at 7:57 PM, Cole Robinson <crobinso at redhat.com> wrote: > If that isn't the issue, I'd say just boot the new kvm command directly, > and remove pieces to see if there is a blatant culprit: ex. revert the > -drive line to use -hda, try with 0/1/2 nics, etc. I will try this, thanks :) raj