Hide Forgot
Description of problem: selecting nat (virtual networking) when installing a fully virtualized domain results in an impared network for the new domU. The ip forwarding is not set up on dom0 to allow domU to get out of the guest network. Version-Release number of selected component (if applicable): rhel5.1 prebeta How reproducible: It happens the first time you try to set up a fully virtualized domU. After it's fixed (by hand: "echo 1 > /proc/sys/net/ipv4/ip_forward") it works fine. I haven't seen this issue when installing para-virtual domains, but I was doing direct networking on those. Steps to Reproduce: 1. in virt-manager, create a new domU 2. select virtual networking for it's network 3. After you boot (good luck with that :) ping any outside server or try to ssh anywhere outside of dom0. Actual results: pings result in long waits with no responses as do ssh attempts. Expected results: pings succeed, ssh succeeds. Additional info: see above for fix.
A new Xen dom0 install and a reinstall of a fully virtualized domU on the same machine and I find that this is set correctly. I'm not sure why this wasn't set the first time.
Closing as NOTABUG w/o any reproducer. Please reopen if this issue persists w/ add'l information.