Red Hat Bugzilla – Bug 172498
Network does not start on Xen kernel
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7
Description of problem:
Networking fails to start. The system correctly transmits DHCP packets, but does not see the replies.
Ethernet interrupts are not being received.
1: 65 Phys-irq i8042
8: 1 Phys-irq rtc
12: 476 Phys-irq i8042
15: 4295 Phys-irq ide1
16: 0 Phys-irq eth0
20: 1 Phys-irq libata
21: 0 Phys-irq ehci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, uhci_hcd:usb5
256: 41600 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Network does not start.
OK with 2.6.11-1.1369_FC4.
Created attachment 120756 [details]
Created attachment 120781 [details]
Does current rawhide work? We just committed a fix to the xen tools which allow
bridged network traffic to run when iptables firewalling is active; this fixes
networking for me.
Yes, networking now works for me with rawhide Xen.
I still can't actually use Xen because
ââââââââââââââââââââ¤ Package Installation ââââââââââââââââââââ
â Namâââââââââââ¤ Error running transaction ââââââââââââ â
â Sizâ â â
â Sumâ There was an error running your transaction, â â
â â probably a disk space problem. For now, â â
â â exiting on this although we should diagnose â â
â â and then let you go back. â â
â â â â
â â ââââââ â e â
â Toâ â OK â â â
â Coâ ââââââ â â
but there doesn't seem to be a disk full condition:
Type <exit> to return to the install program.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev 131964 0 131964 0% /dev
2985408 2985408 0 100% /mnt/source
/tmp/loop0 67264 67264 0 100% /mnt/runtime
1523568 35660 1409268 3% /mnt/sysimage
/tmp/xvda1 101086 5664 90203 6% /mnt/sysimage/boot
/dev 131964 0 131964 0% /mnt/sysimage/dev
Should I file another bug?
That may still be a disk space problem: I've seen this before and had it cured
by installing to a larger disk image. RPM tries to estimate disk space usage
before starting the transaction so if it knows that the transaction will take
more space than there is available, it can fail early even before the disk
starts to fill up.
If a larger device works for you, then it would probably be worth reporting this
as an installer problem as the error message could do with being more informative.