Bug 218275 - Can't install guest from locally exported media
Can't install guest from locally exported media
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Xen Maintainance List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-12-04 06:40 EST by David Juran
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-04 10:36:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
virt-manager.log (1.88 KB, text/plain)
2006-12-04 10:15 EST, David Juran
no flags Details
ifconfig -a (4.99 KB, text/plain)
2006-12-04 10:18 EST, David Juran
no flags Details

  None (edit)
Description David Juran 2006-12-04 06:40:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20061105 Red Hat/ Firefox/ pango-text

Description of problem:
Installing a paravirtualised guest from a media exported by the same machine that the hypervisor is running on doesn't seem to work. I tried exporting the install tree both NFS and HTTP and neither works. Exporting the install tree(via HP) from a different system works just fine.

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

How reproducible:

Steps to Reproduce:
1. Copy the FC6 install tree off the DVD to somewhere accessible by apache.
2. In virt-manager, create a new paravirtualised guest.
3. Point virt-manager to use the install tree at the IP# of either eth0 or lo using http.
4. Anaconda in the guest starts up, asks you for you language, keyboard and network settings.
5. Anconda then complains that it can't find the installation media on this server.
6. Looking at the apache logs will show you that it didn't even try to access stage2.img.

Actual Results:

Expected Results:

Additional info:
Comment 1 Daniel Berrange 2006-12-04 08:41:28 EST
What iptables firewall rules are active ?  Traffic between DomU & Dom0 gets
processed by same firewall rules are traffic between the public network & Dom0,
so it could well be that HTTP traffic is getting dropped. Can you upload output
of '/root/.virt-manager/virt-manager.log', 'ifconfig -a' in the Dom0, and
'iptables -L -n' in Dom0.

Comment 2 David Juran 2006-12-04 10:15:50 EST
Created attachment 142738 [details]
Comment 3 David Juran 2006-12-04 10:18:05 EST
Created attachment 142739 [details]
ifconfig -a
Comment 4 David Juran 2006-12-04 10:21:44 EST
Output of iptables below and output from ifconfig and the virt-manager log
attached. Do note that when I try to install from the same tree exported by
another computer in the lab it works fine... Also pinging the guest domain from
Dom0 works fine.

[root@sepeteus ~]# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
RH-Firewall-1-INPUT  all  --  
ACCEPT     all  --             PHYSDEV match
--physdev-in vif1.0

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain RH-Firewall-1-INPUT (2 references)
target     prot opt source               destination
ACCEPT     all  --  
ACCEPT     icmp --             icmp type 255
ACCEPT     esp  --  
ACCEPT     ah   --  
ACCEPT     udp  --           udp dpt:5353
ACCEPT     udp  --             udp dpt:631
ACCEPT     tcp  --             tcp dpt:631
ACCEPT     all  --             state
ACCEPT     tcp  --             state NEW tcp dpt:22
REJECT     all  --             reject-with
Comment 5 Daniel Berrange 2006-12-04 10:26:07 EST
The abouve iptables output shows your Dom0 is not configured to allow incoming
HTTP (port 80)  requests. Please run system-config-securitylevel, toggle the
checkbox to allow HTTP access through the firewall, and then retry your install.

Comment 6 David Juran 2006-12-04 10:36:13 EST
Thanks... guess I should have been able to figure this out on my own )-:

Note You need to log in before you can comment on or make changes to this bug.