Bug 476732

Summary:	fully automated qemu install fails at Network Manager
Product:	[Fedora] Fedora	Reporter:	Michael DeHaan <mdehaan>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	berrange, clalance, crobinso, markmc, veillard, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-20 10:16:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael DeHaan 2008-12-16 20:06:03 UTC

Description of problem:

qemu installs through python-virtinst for F10 guests seem to be having a DHCP timeout issue.  

Installing a kickstart that is proven to work on a /dev/kvm system with virtio or a PXEd physical host using cobbler/koan does not yield the same results for a regular qemu install.

Network Manager fails to configure the network interface on the first try and hitting "retry" in Anaconda solves the problem and the install continues normally.

Criteria:
-- host does not matter
-- guest must be running F-10
-- guest must be created using qemu

Version-Release number of selected component (if applicable):

(0.5.0-1.fc10.i386)  F-10 latest everything at the time, non-testing


How reproducible:

seems 100% Consistent



Steps to Reproduce:
1.   See description
2.
3.
  
Actual results:

NetworkManager in Anaconda fails to configure the interface requiring the user to hit retry


Expected results:


Fully automated install is successful

Additional info:

Comment 1 Michael DeHaan 2008-12-16 20:06:43 UTC

Talked with this on IRC with crobinson in #virt/OFTC, said to file against libvirt and it could be triaged to other components as needed.

Comment 2 Mark McLoughlin 2009-01-21 09:46:33 UTC

Does this still happen?

If you "virsh net-stop default; virsh net-start default" before starting the install, does that help?

Attach output from:

  $> brctl show
  $> iptables -L -v -n
  $> ps -ef | grep dnsmasq
  $> ifconfig -a
  $> cat /proc/sys/net/ipv4/ip_forward

Comment 3 Mark McLoughlin 2009-04-20 10:16:06 UTC

Missing info from reporter, closing

Comment 4 Michael DeHaan 2009-04-20 14:31:38 UTC

This seems to have been better lately, at least when using real bridges.  I'll let you know if it happens again.