I'm refactoring and extending the autotesting suite for ovirt-node-image. But, in trying to run them on Fedora rather than RHEL, the PXE booting never seems to successfully complete. I can see the virtual bridge created, dnsmasq starts properly, and the VM is defined to use the bridge and to boot from the network. I watch it start to boot, but then never seems to finish. Instead, it sits at: Loading 192.168.136.1:tftpboot/pxelinux.0 ...... The dots come up every few minutes, but only gets to about six of them and then just stops. Any suggestions on what to look for to fix this? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Virtual Machine Management - http://www.ovirt.org/ Is fearr Gaeilge bhriste n? B?arla cliste. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20090421/e4e9839b/attachment.sig>
On Tue, 21 Apr 2009, Darryl L. Pierce wrote:> I'm refactoring and extending the autotesting suite for > ovirt-node-image. But, in trying to run them on Fedora rather than RHEL, > the PXE booting never seems to successfully complete. > > I can see the virtual bridge created, dnsmasq starts properly, and the > VM is defined to use the bridge and to boot from the network. I watch it > start to boot, but then never seems to finish. Instead, it sits at: > > Loading 192.168.136.1:tftpboot/pxelinux.0 ...... > > The dots come up every few minutes, but only gets to about six of them > and then just stops. > > Any suggestions on what to look for to fix this? >Not sure what the physical setup of this box is but I noticed that fedora sees the nics in a different order then RHEL. -Mike
On Tue, Apr 21, 2009 at 11:51:37AM -0400, Darryl L. Pierce wrote:> I'm refactoring and extending the autotesting suite for > ovirt-node-image. But, in trying to run them on Fedora rather than RHEL, > the PXE booting never seems to successfully complete. > > I can see the virtual bridge created, dnsmasq starts properly, and the > VM is defined to use the bridge and to boot from the network. I watch it > start to boot, but then never seems to finish. Instead, it sits at: > > Loading 192.168.136.1:tftpboot/pxelinux.0 ...... > > The dots come up every few minutes, but only gets to about six of them > and then just stops. > > Any suggestions on what to look for to fix this?The problem was iptables related: port 69 was not open for tftp. Once I opened that, things started working as normal. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Virtual Machine Management - http://www.ovirt.org/ Is fearr Gaeilge bhriste n? B?arla cliste. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20090421/46f1655c/attachment.sig>