<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE></TITLE> <META http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> <STYLE type=text/css> <!-- .message {background: white; font-size:9pt; font-family:''Arial'';} .message p { margin-top: 0em; margin-bottom: 0em; } --> </STYLE> </HEAD> <BODY class=''message'' bgColor=#ffffff> Ok, I''ve got my Domain0 networking assignments fixed I think. (I went with the HWADDR=<mac> approach, which is 2 for 2 so far). I''m not having significant luck though with my guest installation, following the instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC5.<br /><br />When I run xenguest-install.py it boots into the FC5 install program. Once that''s running it asks language, country, but it''s unable to find the files needed for the actual FC5 install though. The connection choices are nfs, http, and ftp, and I''ve tried nfs and http before deciding the problem is likely to be that networking isn''t crossing the bridge. Is there any way to check this? I''m arriving at this conclusion because I cannot see any log indications of the connection attempts (using a static IP of 192.168.2.250 for the guest; my Domain0''s eth0 is 192.168.2.1)... I also tried setting the guest to use dhcp to obtain an address during the install and it fails to get an address. What occurs to me: how would Xen know which address to bind a bridge to? Perhaps there is a step I need to do? I know nothing yet about setting up a bridge.<br /><br /><br />While the installer is running, the output of my ifconfig is as shown below. Eth0 and eth1 are the real interfaces; I find it interesting that all interfaces including xenbr0 show some activity.<br /><br /><br />Thanks again for any thoughts on this...<br />Mark<br /><br />eth0 Link encap:Ethernet HWaddr 00:10:DC:F2:70:17<br /> inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0<br /> inet6 addr: fe80::210:dcff:fef2:7017/64 Scope:Link<br /> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br /> RX packets:3024 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:3480 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:1000<br /> RX bytes:409347 (399.7 KiB) TX bytes:816956 (797.8 KiB)<br /> Interrupt:17 Base address:0x4000<br /><br />eth1 Link encap:Ethernet HWaddr 00:90:47:03:B8:63<br /> inet addr:myinternetip Bcast:myinternetbcast Mask:255.255.255.252<br /> inet6 addr: fe80::290:47ff:fe03:b863/64 Scope:Link<br /> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br /> RX packets:699 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:601 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:0<br /> RX bytes:165595 (161.7 KiB) TX bytes:170365 (166.3 KiB)<br /><br />lo Link encap:Local Loopback<br /> inet addr:127.0.0.1 Mask:255.0.0.0<br /> inet6 addr: ::1/128 Scope:Host<br /> UP LOOPBACK RUNNING MTU:16436 Metric:1<br /> RX packets:4425 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:4425 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:0<br /> RX bytes:13915749 (13.2 MiB) TX bytes:13915749 (13.2 MiB)<br /><br />peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br /> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link<br /> UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1<br /> RX packets:674 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:718 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:1000<br /> RX bytes:165738 (161.8 KiB) TX bytes:185932 (181.5 KiB)<br /> Interrupt:18 Base address:0x6000<br /><br />vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br /> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link<br /> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br /> RX packets:601 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:702 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:0<br /> RX bytes:170365 (166.3 KiB) TX bytes:165833 (161.9 KiB)<br /><br />vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br /> inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link<br /> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br /> RX packets:6 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:5 errors:0 dropped:37 overruns:0 carrier:0<br /> collisions:0 txqueuelen:0<br /> RX bytes:2052 (2.0 KiB) TX bytes:730 (730.0 b)<br /><br />xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF<br /> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link<br /> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br /> RX packets:129 errors:0 dropped:0 overruns:0 frame:0<br /> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0<br /> collisions:0 txqueuelen:0<br /> RX bytes:12722 (12.4 KiB) TX bytes:468 (468.0 b)<br /><br /><br /> </BODY></HTML>
Mark A Heilpern
2006-Apr-06 20:03 UTC
Re: [Fedora-xen] installation problem with the guest
Sorry for the re-post. It''s been pointed out to me that my original email was in HTML mode, where many people''s readers will not display properly. Repeated in plain text mode: Ok, I''ve got my Domain0 networking assignments fixed I think. (I went with the HWADDR=<mac> approach, which is 2 for 2 so far). I''m not having significant luck though with my guest installation, following the instructions at http://fedoraproject.org/wiki/FedoraXenQuickstartFC5. When I run xenguest-install.py it boots into the FC5 install program. Once that''s running it asks language, country, but it''s unable to find the files needed for the actual FC5 install though. The connection choices are nfs, http, and ftp, and I''ve tried nfs and http before deciding the problem is likely to be that networking isn''t crossing the bridge. Is there any way to check this? I''m arriving at this conclusion because I cannot see any log indications of the connection attempts (using a static IP of 192.168.2.250 for the guest; my Domain0''s eth0 is 192.168.2.1)... I also tried setting the guest to use dhcp to obtain an address during the install and it fails to get an address. What occurs to me: how would Xen know which address to bind a bridge to? Perhaps there is a step I need to do? I know nothing yet about setting up a bridge. While the installer is running, the output of my ifconfig is as shown below. Eth0 and eth1 are the real interfaces; I find it interesting that all interfaces including xenbr0 show some activity. Thanks again for any thoughts on this... Mark eth0 Link encap:Ethernet HWaddr 00:10:DC:F2:70:17 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::210:dcff:fef2:7017/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3024 errors:0 dropped:0 overruns:0 frame:0 TX packets:3480 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:409347 (399.7 KiB) TX bytes:816956 (797.8 KiB) Interrupt:17 Base address:0x4000 eth1 Link encap:Ethernet HWaddr 00:90:47:03:B8:63 inet addr:myinternetip Bcast:myinternetbcast Mask:255.255.255.252 inet6 addr: fe80::290:47ff:fe03:b863/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:699 errors:0 dropped:0 overruns:0 frame:0 TX packets:601 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:165595 (161.7 KiB) TX bytes:170365 (166.3 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4425 errors:0 dropped:0 overruns:0 frame:0 TX packets:4425 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13915749 (13.2 MiB) TX bytes:13915749 (13.2 MiB) peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:674 errors:0 dropped:0 overruns:0 frame:0 TX packets:718 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:165738 (161.8 KiB) TX bytes:185932 (181.5 KiB) Interrupt:18 Base address:0x6000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:601 errors:0 dropped:0 overruns:0 frame:0 TX packets:702 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:170365 (166.3 KiB) TX bytes:165833 (161.9 KiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:37 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2052 (2.0 KiB) TX bytes:730 (730.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:129 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12722 (12.4 KiB) TX bytes:468 (468.0 b)