similar to: Dom-U config: whats the role of vif - IP

Package: xen-utils-common Version: 4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 Severity: important Tags: patch security -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),

Hi folks, I am trying to get antispoofing running on xen3 (based on Debian Sarge). This is what I have done to enable it: 1. I have compiled a dom0 kernel with CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m 2. I made sure this module is loaded: lsmod gives xt_physdev (among others). 3a. I have changed the line "(network-script network-bridge)" to "(network-script network-bridge

Hey everyone, I have a question about vif-common.sh. I run multiple bridges attached on dummy interfaces, which allow me to put guests in seperate subnets (routed through the dom0). As you might expect I already have quite extensive iptables scripts to accomidate this kind of routing. I was just hoping someone on this list can confirm, that I understand what the iptables lines in vif-common.sh

Hello, Despite of reading a lot of descriptions I don''t understand the network configuration. I simply have too little experience. I work remote with the machine via ssh. My dom0 is running. I copied an existing installation into a LV and created the following file: # cat /etc/xen/domu-sarge # -*- mode: python; -*- kernel = "/boot/vmlinuz-2.6.18-4-xen-686" #kernel =

Hi, The attached patch fixes the setup of the bridge ports and the bridge itself. Changes: * move some functions to xen-network-common.sh, so both vif-bridge and network-bridge can use them. * add a new function to configure bridge ports and use it. * make sure arp requests, ipv6 autoconfiguration and ipv6 router solicitations are disabled for the bridge ports and also for the

Hi, I''m using the XEN 3.4.1-pre4 Hypervisor in Routet Mode and I''m facing some problems when I start the DomU. In detail, it means that the DomU IP-Adress will not be implemented in the Kernel routing table after starting the domU via "xm create /<path +configfle>" After making a "netstat -nr" it will not show the IPadress bound to the

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950. In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64. I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues. Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my

Hullo everybody I want to install a guest slackeware guest OS on a VM for xenserver 5.6 . I have created logical volumes , mounted the slackware 13 image and copied the /lib/modules and below are my configurations. [root@virtualintranet /]# uname -r 2.6.27.42-0.1.1.xs5.6.0.44.111158xen *Grub Configs:* [root@virtualintranet grub]# cat grub.conf default=0 timeout=10 title

Hullo everybody I want to install a guest slackeware guest OS on a VM for xenserver 5.6 . I have created logical volumes , mounted the slackware 13 image and copied the /lib/modules and below are my configurations. [root@virtualintranet /]# uname -r 2.6.27.42-0.1.1.xs5.6.0.44.111158xen *Grub Configs:* [root@virtualintranet grub]# cat grub.conf default=0 timeout=10 title

Hi folks, I started testing the antispoof feature of xen stable (2.0.7). I am stuck with it. I have setup a standard bridged environment. I understood it like this: in domU config I set up the virtual NIC like vif = [ ''mac=ae:00:00:78:78:78, ip=192.168.0.100'' ] Then I configure /etc/network/interface of this domU to show the same IP address for eth0. After restarting

uname -a SunOS i7 5.11 snv_114 i86pc i386 i86xpv The box is a core i7 with 6GB of RAM. The command virt-install --name 10u7 --ram 1024 --hvm --file /guests/10u7 --os-type=solaris os-variant=solaris10 --location /export/iso/sol-10-u7-ga-x86-dvd.iso get as far as opening the VNC client, when I select Solaris from grub, the OS starts to boot then panics, closing the session. So I

Hi, I have seen many posts regarding this but have not found the soultion. So please cna someone shed some light on this Thanks - padma I get this error when I do try to create a domU guest (xen 3.0.0, 2.6.12.6). The vif is set to vif = [ '' mac=aa:00:00:00:11, bridge=xenbr0'' ] and a "brctl show" shows xenbr0 8000,fefffffff interfaces vif0.0 peth0 Xend.log

Hi all, I''m searching for a tutorial how to setup multiple network cards with xen network bridge setup in debian lenny. My problem is, bridges seams only to work if i put an ip adress in dom0 to them. Thanks, Alex _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, Ive built a new server using xen debian lenny packages. Im trying to firewall dom 0 which i can do ok but it then blocks access to the dom Us. Has anyone managed to do this successfully? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris

We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM). The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

I''m wondering if Open Solaris + xVM will allow me to do the following: I currently have 2 Solaris 10 servers sucking down electrons that I would like to consolidate into 2 xVM instances on a Solaris 11 quad core box. This is what it looks like: Internet --->A sol 10 FW/Web B>---->C Sol 10 app/mail D---> local LAN So interface A is connected to the Internet. The FW/Web box