http://permalink.gmane.org/gmane.comp.emulators.xen.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.emulators.xen.user/78864 <pre>Good day, Gordan, On Mon, May 20, 2013 at 4:36 AM, Gordan Bobic &lt;gordan&lt; at &gt;bobich.net&gt; wrote: If PCI passthrough works the way I think it works, then it just might. Pre-OS interaction with PCI devices (a-la Primary/VGA Passthrough) requires mapping memory such that an option ROM can interact with the device in the same way it would when a system is first booted. One of the great things about iPXE is that, while it interacts with the BIOS via that tradition option ROM interface, it scans the PCI bus itself, hunting for PNP devices in much the same way that a Windows or Linux kernel would when it starts up..... and since utilization of passed-through PCI devices works *extremely well* in those circumstances, I wouldn't be at all surprised if it does work. The build of iPXE that is included with Xen is... a little on the old side. All I really know about it is that my scripts don't work properly in it---I actually chainload a custom iPXE build from Xen's built-in copy, and then go from there. If you happen </pre> Andrew Bobulsky 2013-05-20T19:47:22 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78863 <pre>Hello. El 20/05/13 09:54, Alexey Makarov escribió: What is "XCP Network Management", xsconsole? By default, XCP 1.6 creates a "network" for each physical interface, as a bridge. So, there is no ethX directly usable, the bridges are used as network interface instead. Check "xe network-list" and "xe pif-list" output to inspect that. Does they have the "UP" flag or not? Greetings. </pre> Alexandre Kouznetsov 2013-05-20T17:14:42 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78862 <pre>Hello. El 19/05/13 20:19, James Triplett escribió: This looks pretty nice, should work as is, maybe with few corrections: 1. The specification of "network" and "broadcast" may be safely omitted, ifupdown scripts do excellent job deducing this parameters. Omitting them leaves you less room to make a mistake. 2. Consider adding "bridge_stp off" parameter. http://wiki.xen.org/wiki/Xen_Bridge_Loop#Why_STP_is_turned_off.3F 3. Specify "eth0" in bridge_ports, it would make things more explicit. 4. IMPORTANT Make sure eth0 is not configured elsewhere. Comment out any "auto eth0" or "allow-hotplug eth0" (contrary to what Adam Goryachev suggested) in /etc/network/interfaces. Make sure any network automated configuration tool is turned off, such as Debian's NetworkManager. A simple and clean starting /etc/network/interfaces would look like this: ##allow-hotpug eth0 #iface eth0 inet static # address 192.168.0.26 # netmask 255.255.255.0 # gateway 192.168.0.1 auto br0 iface br0 inet static address 192.1</pre> Alexandre Kouznetsov 2013-05-20T16:58:54 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78861 <pre>Hi, Thank you! I got the patches and will try them out this evening. -- View this message in context: http://xen.1045712.n5.nabble.com/Need-Download-link-for-Xen-VGA-Passthrough-Patches-tp5716230p5716256.html Sent from the Xen - User mailing list archive at Nabble.com. </pre> QGJ 2013-05-20T16:16:45 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78860 <pre>I just got permanent domain www.thexenguy.com/forums _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> jacek burghardt 2013-05-20T15:23:30 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78859 <pre>On a fresh installation of XCP 1.6 there is no interface in XCP Network Management. While in comman line ifconfig -a shows me both physical interfaces. I would appreciate for an ideas on what. </pre> Alexey Makarov 2013-05-20T14:54:51 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78857 <pre>It looks like one of my network admins has carved up this address space and pointed the numbers I was trying to use elsewhere, I'm getting them to find out what's going on. Anyway, I changed the static IP to 139.25 ifdown eth0 &amp;&amp; ifup eth0 and hey presto, can ping out and all is good! Thanks for your help guys, really appreciated. From: Jan Hejl [mailto:jh&lt; at &gt;excello.cz] Sent: 20 May 2013 14:42 To: Simon Jones Cc: xen-users&lt; at &gt;lists.xen.org Subject: Re: [Xen-users] xenbr0 / domU static IPs So far so good. And eth1 configuration? Did you try tcpdump on dom0 to see what's happening there when you're pinging from domU? Dne 20.5.2013 15:38, Simon Jones napsal(a): #route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 195.2.139.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0 0.0.0.0 195.2.139.1 0.0.0.0 UG 0 0 0 xenbr0 #ip ro</pre> Simon Jones 2013-05-20T13:47:38 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78856 <pre>And that's where the ghost comes alive :-D Dne 20.5.2013 15:47, Simon Jones napsal(a): _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Jan Hejl 2013-05-20T13:48:43 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78855 <pre>So far so good. And eth1 configuration? Did you try tcpdump on dom0 to see what's happening there when you're pinging from domU? Dne 20.5.2013 15:38, Simon Jones napsal(a): _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Jan Hejl 2013-05-20T13:42:20 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78854 <pre> Am 20.05.2013 um 15:09 schrieb Simon Jones: For bridging only setup this should be "0" as no routing happens. But it seems you are running into a routing rpoblem with your eth0 as it "grabs" the whole network you expect "inside" your dom0 and/or your bridge network. Try to disable eth0 completely (should be have no ip and route) for testing your Dom0/domU networking or give him another IP (your admin network is in another physical network and should have another IP. In this case you need routes and ip_forward on again. hth, best regards, Niels. </pre> Niels Dettenbach 2013-05-20T13:43:01 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78853 <pre> That is not needed for a bridge, only for routed connections. The same for iptables, it shouldn't apply to the bridge. I think there is another tool ebtables or similar which will do filtering of traffic across a bridge, but you should know if you have configured that. Try the following from dom0: tcpdump -tn -i xenbr0 host &lt;ip of domu&gt; Then, from the domu, ping the gateway IP That should show whether the dom0 is seeing the traffic from the domU ... if you don't see the traffic on the bridge, then try the vif interface for the domU, if you still don't see the traffic, then it is a domU issue. Also, check the output of "route -n" (linux) or "route print" (windows) from the domU Regards, Adam </pre> Adam Goryachev 2013-05-20T13:43:38 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78852 <pre>#route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 195.2.139.0 0.0.0.0 255.255.255.0 U 0 0 0 xenbr0 0.0.0.0 195.2.139.1 0.0.0.0 UG 0 0 0 xenbr0 #ip route 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.4 195.2.139.0/24 dev xenbr0 proto kernel scope link src 195.2.139.4 default via 195.2.139.1 dev xenbr0 From: Jan Hejl [mailto:jh&lt; at &gt;excello.cz] Sent: 20 May 2013 14:35 To: Simon Jones Cc: xen-users&lt; at &gt;lists.xen.org Subject: Re: [Xen-users] xenbr0 / domU static IPs No you don't have to, for now. Firewall looks clear, contains only irrelevant rules. It's definately a network problem. Probably on dom0. Can you please check your dom0 routing table? With: ip route show And how is the eth1 on dom0 configured? Dne 20.5.2013 15:25, Simon Jones napsal(a): No firewall in the way; root&lt; at &gt;xen-1:/etc</pre> Simon Jones 2013-05-20T13:38:03 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78851 <pre>No you don't have to, for now. Firewall looks clear, contains only irrelevant rules. It's definately a network problem. Probably on dom0. Can you please check your dom0 routing table? With: ip route show And how is the eth1 on dom0 configured? Dne 20.5.2013 15:25, Simon Jones napsal(a): _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Jan Hejl 2013-05-20T13:34:46 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78850 <pre> Jan Hejl &lt;jh&lt; at &gt;excello.cz&gt; schrieb: For bridging only it should be 0, but "could" be "1"... It seems you've runned into a routing prob as your eth0 offers the whole net you expect on your bridge. Check your networking without eth0 (put eth0 down for that time and delete the IP on it). hth, Niels. </pre> Niels Dettenbach 2013-05-20T13:30:06 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78849 <pre>No firewall in the way; root&lt; at &gt;xen-1:/etc/xen/scripts# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif4.0 --physdev-is-bridged ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif4.0 --physdev-is-bridged udp spt:bootpc dpt:bootps ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif4.0 --physdev-is-bridged ACCEPT all -- 10.0.0.101 anywhere PHYSDEV match --physdev-in vif4.0 --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif3.0 --physdev-is-bridged ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif3.0 --physdev-is-bridged Chain OUTPUT (policy ACCEPT) target prot opt source </pre> Simon Jones 2013-05-20T13:25:40 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78848 <pre>Weird. What about your firewall? Specially FORWARD chain. Is somethnig there what can block traffic? Are you sure that there's nothing (router / switch) that can block your traffic? Some hosting providers allow traffic only from dom0 MAC address everything else is dropped. Then you should set up routed network inside you dom0. Dne 20.5.2013 15:09, Simon Jones napsal(a): _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Jan Hejl 2013-05-20T13:19:54 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78847 <pre> Nick Katsipoulakis &lt;popanik&lt; at &gt;gmail.com&gt; schrieb: You wrote it still here: ...means that the two virtual disks in your regarding DomU are file based, placed as files: /vmstore//domains/VM4LiveFS/disk.img ... (btw: the (double) slashes "//" should be changed into one "/". If they are not there (even when the DomU is started) you might use the wrong config file here. When the DomU is running you may look after it too by: xm block-list or xl block-list and losetup -a (from mind, pls check the correct syntax by help if required) hth, best regards, Niels. </pre> Niels Dettenbach 2013-05-20T09:32:14 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78846 <pre>Aha! It's set to 0, echo "1"&gt; /proc/sys/net/ipv4/ip_forward has changed it to 1, still can't ping anything other than Dom0 ip on both guests though. From: Jan Hejl [mailto:jh&lt; at &gt;excello.cz] Sent: 20 May 2013 14:02 To: Simon Jones Cc: xen-users&lt; at &gt;lists.xen.org Subject: Re: [Xen-users] xenbr0 / domU static IPs Thanks. It's more clearer now. :) What "/proc/sys/net/ipv4/ip_forward" contains? 0 or 1? Should be set to 1. Dne 20.5.2013 14:57, Simon Jones napsal(a): The windows guest can also ping dom0 but again, can't ping the gateway or anything else other than Dom0's IP. I can only get vnc to the windows machine and as such can't copy/paste the output from ipconfig /all but it is all correct, static IP 195.2.139.196 / 255.255.255.0 / gateway 195.2.139.1 and our public recursor dns servers 195.2.130.8 / 200, should I check for something in particular? Here's how dom0 is configured; # The loopback interface auto lo iface lo inet loopback # Bridge Static Configuration # (network, broadcast and gateway are opti</pre> Simon Jones 2013-05-20T13:09:42 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78845 <pre>Thanks. It's more clearer now. :) What "/proc/sys/net/ipv4/ip_forward" contains? 0 or 1? Should be set to 1. Dne 20.5.2013 14:57, Simon Jones napsal(a): _______________________________________________ Xen-users mailing list Xen-users&lt; at &gt;lists.xen.org http://lists.xen.org/xen-users</pre> Jan Hejl 2013-05-20T13:01:42 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78844 <pre>The windows guest can also ping dom0 but again, can't ping the gateway or anything else other than Dom0's IP. I can only get vnc to the windows machine and as such can't copy/paste the output from ipconfig /all but it is all correct, static IP 195.2.139.196 / 255.255.255.0 / gateway 195.2.139.1 and our public recursor dns servers 195.2.130.8 / 200, should I check for something in particular? Here's how dom0 is configured; # The loopback interface auto lo iface lo inet loopback # Bridge Static Configuration # (network, broadcast and gateway are optional) auto xenbr0 iface xenbr0 inet static bridge_ports eth1 address 195.2.139.4 broadcast 195.2.139.255 netmask 255.255.255.0 network 195.2.139.0 gateway 195.2.139.1 #Eth0 Static Configuration auto eth0 iface eth0 inet static address 192.168.2.4 netmask 255.255.255.0 Eth1 is the public port on the WAN and Eth0 is just our back-end admin lan so you can ignore that. Dom0 works great, I can ping o</pre> Simon Jones 2013-05-20T12:57:23 http://permalink.gmane.org/gmane.comp.emulators.xen.user/78843 <pre>Have you installed the GPLPV drivers in the windows domU? Can you show the output of "ipconfig /all" from the windows machine (command prompt) Regards, Adam </pre> Adam Goryachev 2013-05-20T12:54:23 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.emulators.xen.user