similar to: tcpdump

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

Hi Everyone, Does anybody have any experience using pfSense on Xen? I would most probably have to use HVM... My idea would be to use PCI-Passthrough to the pfsense DomU, and only make the Dom0 accessable via the pfsense firewall Thanks Jonathan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi Everyone, How does one install Ubuntu 10.04 DomU in PV mode when running Xen 4.0? My Dom0 is also running 10.04. Can I still use the CD? Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi, Firstly I apologise for the cross-post, however I don't expect to get as quick a response from the package maintainers as I do from the Debian community, and this issue affects a service that I've got scheduled to go live at midnight this evening. :( A recent update from xen-hypervisor-4.1-amd64 version 4.1.3-7, to version 4.1.3-8 on Debian Wheezy has caused all vm's on this host

Hi Everyone, To convert an HVM install to PV, is it just as simple as creating a new config file, and use the "kernel" and "initrd" parameters to boot from a XEN kernel stored in the Dom0, and use the (ex) HVM''s disk image in the "disk" parameter? Or is there something else I am missing? Thanks _______________________________________________ Xen-users

Hi Everyone, I upgraded my CentOS 5.5 to Xen 3.4.2 using this guide: http://www.syntaxtechnology.com/2010/01/upgrade-xen-3-0-on-centos-5-4-x86_64-to-xen-3-4-2/ Now, using the new kernel that it gave me, the system doesn''t seem to be able to detect vt-x.. In virt-manager, Local Install Media and Network Boot are greyed out.. Any ideas? Thanks

Hello, I am having big problems with Xen virtual network interfaces. First I tried typical bridge support, no luck. The packets sent from dom0 to domU seemed to disappear somewhere. Then, to debug the problem I have set up a simple point-to-point link and still have the same problem. I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU. I have tried kernel 2.6.16.35 and 2.6.16.41. I

Hello everyone, I grabbed xen-3.3.1 sources from the Mercurial repository (xen-3.3-testing.hg, changeset 475:1cf755387728, from Oct. 23, 2008) and built Xen from these sources on a 32-core (8 quad core Barcelona CPUs) SunFire machine, running an Ubuntu 8.04 (Hardyy Heron) distribution. Everything seemed to be going OK until I booted an HVM (also Ubuntu 8.04) domain. That domain boots normally but

Dear *, I''m more used to work with RedHat like OSes. Still, I did not denied the request from a user who wants a domU based on ubunto. I usually use virt-install to do the job, with a script similar to this one: #!/bin/sh BASE=SL-4.7-i386-pv \ virt-install --nographics \ --nonsparse \ --paravirt \ --noreboot \

Hello, Fast question: from DomU I cannot ping Dom0, I only get 19:17:33.573370 arp who-has 192.168.10.1 tell 192.168.10.150 19:17:34.573421 arp who-has 192.168.10.1 tell 192.168.10.150 using tcpdump in Dom0. Why? --------------- Detailed question: I''m setting up a Xen virtual server. The environment is: -HVM -AMD64 -Debian Etch and using Xen from Debian repository (so Xen 3.0.3,

Hello all I am using open source xen v 3.0.4. When network-nat and vif-nat is activated in the config file, modified guests boot ok but hvm guests does not have network connection. Here is the config files: xend-config.sxp ------------------------------------- #(network-script network-bridge) #(vif-script vif-bridge) (network-script network-nat) (vif-script vif-nat)

Hi Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

Hi, I cannot get my network up in WinXP- and winVISTA-domU''s I need some help, since I got lost in the google-jungle... My system: UBUNTU gutsy gibon-AMD64 on a intel core duo-system. this is my /etc/xen/winxp.cfg: ######### # # Configuration file for the Xen instance debian.qwork.test, created # by xen-tools 3.5 on Sun Mar 16 20:03:26 2008. # # # Kernel + memory size # kernel =

Hello, I have a xen server (xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p / kernel 2.6.24-28-xen). I have some domUs, one of them is a fli4l router, the others are eisfair domUs (fileserver, webserver and mailserver). All of the domUs are connected via vif network interface with a bridge in dom0. There is a problem invoking following command in every domU: openssl s_client -connect

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

When I start xen dom0 I get that same dhcp address for eth0 and for xen-br0, dom0 can talk to the world. If I start each of my 3 domU''s mannually, each guest gets a xen-br0 vif with a dhcp address and all 3 can talk to the outside world and each other (my "flat network"). What I want is a tiered network with the first domU acting as a firewall with 3 nics vif = [

*Hello,* I have installed Xen as Hypervisor with OpenSUSE running in Dom0. I want to use ovswitch (ovs) instead of the bridges that Xen created. In order to do so, I installed ovs in dom0 just like for the plain Linux. Xen has replaced eth0 with peth0, and has created a bridge named eth0. And eth0 is connected peth0 interface , vif2.0 interface (VM), and everything is working fine. Now I delete

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to