During the build (via a serial console) we get input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 running install... running /sbin/loader Sending request for IP information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain...
And there it hangs.
On the 6.3 host: Feb 8 08:28:55 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPOFFER on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPREQUEST for 10.0.0.205 (10.0.0.134) from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPACK on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPOFFER on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPREQUEST for 10.0.0.205 (10.0.0.134) from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPACK on 10.0.0.205 to 52:54:00:5a:a7:48 via br0
I wonder if this could be related to the "renew" problem I'm seeing on a pre-existing 5.9 machine:
Feb 8 07:00:11 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:00:55 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:00:55 mercury dhclient: 5 bad udp checksums in 5 packets Feb 8 07:01:02 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:01:14 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:01:49 mercury dhclient: 5 bad udp checksums in 5 packets
It eventually gets there... Feb 8 07:02:00 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:02:00 mercury dhclient: DHCPACK from 10.0.0.134 (xid=0x4e88b5e5) Feb 8 07:02:00 mercury dhclient: bound to 10.0.0.135 -- renewal in 18554 seconds.
My 6.3 new builds work just perfect; it's only 5.x that has problems!
Any ideas?
On Fri, Feb 8, 2013 at 11:04 AM, Stephen Harris lists@spuddy.org wrote:
During the build (via a serial console) we get input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 running install... running /sbin/loader Sending request for IP information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain...
Have you built any previous 5.x releases as guests? And you're not showing the "virt-install" options you're using, please publish those. In particular, can you do a simple install with a DVD image rather than DHCP or PXE, to isolate the issues from any network problems? Can you do this from virt-manager so you can track the graphical outputs more fully, since serial console tends to be pretty limited?
And there it hangs.
On the 6.3 host: Feb 8 08:28:55 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPOFFER on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPREQUEST for 10.0.0.205 (10.0.0.134) from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPACK on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPDISCOVER from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPOFFER on 10.0.0.205 to 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPREQUEST for 10.0.0.205 (10.0.0.134) from 52:54:00:5a:a7:48 via br0 Feb 8 08:28:56 penfold dhcpd: DHCPACK on 10.0.0.205 to 52:54:00:5a:a7:48 via br0
I wonder if this could be related to the "renew" problem I'm seeing on a pre-existing 5.9 machine:
Feb 8 07:00:11 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:00:55 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:00:55 mercury dhclient: 5 bad udp checksums in 5 packets Feb 8 07:01:02 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:01:14 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:01:49 mercury dhclient: 5 bad udp checksums in 5 packets
It eventually gets there... Feb 8 07:02:00 mercury dhclient: DHCPREQUEST on eth0 to 10.0.0.134 port 67 (xid=0x4e88b5e5) Feb 8 07:02:00 mercury dhclient: DHCPACK from 10.0.0.134 (xid=0x4e88b5e5) Feb 8 07:02:00 mercury dhclient: bound to 10.0.0.135 -- renewal in 18554 seconds.
My 6.3 new builds work just perfect; it's only 5.x that has problems!
Any ideas?
--
rgds Stephen _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
On Fri, Feb 08, 2013 at 11:53:24AM -0500, Nico Kadel-Garcia wrote:
On Fri, Feb 8, 2013 at 11:04 AM, Stephen Harris lists@spuddy.org wrote:
During the build (via a serial console) we get input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 running install... running /sbin/loader Sending request for IP information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain...
you do this from virt-manager so you can track the graphical outputs more fully, since serial console tends to be pretty limited?
Ah, that helped! I used a graphics console and now it reports a useful error; my kickstart file for RH5 had mistakenly coded "5.8" into the paths, rather than using the symlink I maintain. This didn't show in the text installer, but did when I used the graphics console.
Thanks!
On Fri, Feb 8, 2013 at 12:13 PM, Stephen Harris lists@spuddy.org wrote:
On Fri, Feb 08, 2013 at 11:53:24AM -0500, Nico Kadel-Garcia wrote:
On Fri, Feb 8, 2013 at 11:04 AM, Stephen Harris lists@spuddy.org wrote:
During the build (via a serial console) we get input: ImExPS/2 Generic Explorer Mouse as /class/input/input1 running install... running /sbin/loader Sending request for IP information for eth0... Determining host name and domain... Sending request for IP information for eth0... Determining host name and domain...
you do this from virt-manager so you can track the graphical outputs more fully, since serial console tends to be pretty limited?
Ah, that helped! I used a graphics console and now it reports a useful error; my kickstart file for RH5 had mistakenly coded "5.8" into the paths, rather than using the symlink I maintain. This didn't show in the text installer, but did when I used the graphics console.
So it wasn't the KVM at all, just the kickstart file and a lack of error messages from anaconda.
-
Nico Kadel-Garcia -
Stephen Harris