similar to: delete interfaces

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

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'']

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Hello everybody, I have an odd problem with iptables using a Xen bridge setup. I don''t know if it would be better to post to netfilter Mailing-List. But I hope someone here know how to solve it. If it''s OT here, please let me know. I''ll try to do a little bit ASCII-Graphics to explain the topo better: _________ ________

When I try to run xm shutdown, I get the following error messages. At this point, I am unable to perform any operations in dom0, and must reboot the server. I currently have the network information for each domU (2) configured in the sxp file as well as the interfaces file of the domU. Any help would be greatly appreciated. Error: Device 0 not connected Usage: xm list [options] [Domain, ...]

When I add all interfaces, the internet does not work.... eth0 = interneteth1 = lan ------------------auto eth0 iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255 auto eth1 iface eth1 inet static address 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 auto xenbr0 iface xenbr0 inet static

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

Hi, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at

Hi, I have just installed Slackware64 13.0 Linux as a HVM guest with Xen 3.5-unstable changeset 20143 pv-ops dom0 kernel 2.6.31.4. For more details, please refer to the following link: http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ There are 83 screenshots so far at

Sorry to duplicate my issues onto the list - I thought I had looked through this thread before and seen a different error, but apparently Adam and I are running into much the same thing. I'm seeing exactly the same "Failed to assign device to IOMMU" along with the "Device not owned by PCI Back End or pci-stub" in these scenarios. I have not gone back to previous versions,

In my project, I tried to use iptables, instead of bridge, to direct networking traffics from one VM to another in one host. What I am doing is I delete xen-br0, and I have two VMs that have IP addresses of 10.8.0.51 and 10.8.0.52. I use iptables -t mangle -A FORWARD -d 10.8.0.51 -j ROUTE --oif vif1.0 iptables -t mangle -A FORWARD -d 10.8.0.52 -j ROUTE --oif vif2.0 vif1.0 and vif2.0 are the

Here is the situation. I have a xen system with 2 drives setup in a RAID1. I pulled one drive and put it into an identical server. Now, when I boot up the new server, peth1 is not created. [root@dom0 ~]# ifconfig | grep Link eth1 Link encap:Ethernet HWaddr 00:14:38:A7:55:C2 inet6 addr: fe80::214:38ff:fea7:55c2/64 Scope:Link lo Link encap:Local Loopback vif1.0 Link

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 =

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, some more info which I collected during physically accessing the machine while rebooting. I was suprised that while it was not able to do anything it was not a ''static'' kernel panic, but the following text was scrolling continously thru the screen: """ ata3: port reset, p_is 1 is e pis 1 cmd c017 tf 50 ss 113 se 0 ata3: status=0x50 { DriveReady SeekComplete }

Fresh Ubuntu 13.10 server build with all the latest patches, installed Xen 4.3 and XCP-XAPI. Got Xenbr0 working properly and created an LVM storage repository and a CIFS ISO repository. I can create VM''s no problem at all but whenever I try to start them I get the following error from the log. Only Windows VM. The error comes up almost instantly when trying to start it. Not sure where to

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write