similar to: Windows HVM and routed setup

Hi Is there a way to configure Windows in a pointopoint fashion? Windows can do this for dial up networking, but I find no way to do it on ethernet. Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, can anyone give an example for a pointopoint routed setup? i.e. each virtual machine has one ip with pointopoint config to the host machine, on a private interface - thus the virtual machines can only talk to the host, which routes them and can use normal iptables for filtering all traffic. with xen this was a simple script doing ifconfig ${vif} ${main_ip} netmask 255.255.255.255 up ip

Hi I have a Xen 4.4 installation with Windows in a HVM domain and I need to use a routed setup. However the vif-route script does not work for HVM domains. So far I used an outdated Xen 4.1 installation with manually patched scripts that could do routed setups with HVM. But now I wanted to update and switch from xm to xl. Is there any way to make Xen work with HVM in a routed setup? Or do I

Hello, I''m used to using Xen in a bridge mode where my dom0 and all domUs are on the same layer 2 network. However now I have to set up a server whose eth0 is on one network and the domUs will be on another /29. So, for example, if the eth0 of dom0 is 192.168.1.214/24, then I have 10.1.1.0/29 (10.1.1.0 -> 10.1.1.7) routed to it for use in domUs, how would I go about setting that up?

Just successfully installed SLES9.3-32bit as file-backended HVM domU. Everything went OK, the distributive partitioned its "harddisk" into root and swap OK, have its grub installed into sda boot sector, but I could not make to boot no one single first time after installation. Every domU boot gives the following screen for a short time and dies: Booting from Hard Disk... Boot from

Hello people, first of all this is my first mail and I am new to Xen so be nice with me :-) OK, I installed a Centos 5.5 in a system. Used yum groupinstall "Virtualization" to install anything related to Xen. Those packages installed:

Hello all, There is a Suse 10 dom0 machine which is acting as a router. It has two ethernet cards, one assinged a public address and the other a private one. The machine also logins to a VPN server on the public network (via eth0) and it can route traffic requests from one network to another. This is the configuration: eth0 Link encap:Ethernet HWaddr 00:30:05:AC:15:26 inet

Thanks for the reply. Sorry I didn't provide more details, but, yes, these are HVM domains. I use PV domains whenever possible, but in the case of Windows XP, that isn't possible, so I have to use HVM. I haven't tried suspending to OCFS2 with a PV domain, but I may give that a shot. Still, I think it's strange that it works perfectly fine to my ext3 and reiser filesystems, but

Hi all, I was wondering if cpu frequency scaling in dom0 (using the cpufreq=dom0-kernel boot parameter) may cause problems with HVM domUs? This is on Xen 3.2.1. PV domUs seem to work just fine. They adjust to the frequency change on the go. The HVM I run using the unmodified_driver drivers (also from the 3.2.1 release) seem to have very slow timers if dom0 lowers the frequency. Birger

Hello. Up to version 3.0.4, I did the following to get two xen kernels (dom0 and domU) with my own config: wget http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/... make xen make tools make docs make linux-2.6-xen0-config CONFIGMODE=menuconfig make linux-2.6-xen0-build make linux-2.6-xen0-install make linux-2.6-xen0-dist make linux-2.6-xenU-config CONFIGMODE=menuconfig make

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

Hi! I tried booting ubuntu natty/oneiric domUs with 2.6.39 and 3.0rc1 linux-image packages, but they all "just stop" after the kernel is loaded and the init process should take over. The problem must be within the linux-image package, since natty domUs with the standard 2.6.38 kernel boot just fine. I also have debian and gentoo domUs running 2.6.39 without issues, so it''s

Dear Xen Community, today we tried to upgrade our base server from a Xeon E5430 to a Xeon X5570 (Nehalem). This worked fine so far, but our DomUs with Kernel 2.6.27 no longer boot - they start up until the following message appears: [..] Mount-cache hash table entries: 256 Initializing cgroup subsys ns Initializing cgroup subsys cpuacct Initializing cgroup subsys memory Initializing cgroup

Hi, I want to combine all the above mentioned technologies. The Linbit pages warn not to use the drbd: VBD with HVM DomUs. This page however: http://publications.jbfavre.org/virtualisation/cluster-xen-corosync-pacemaker-drbd-ocfs2.en (thank you Jean), simply puts two DRBD devices in dual primary mode and starts Xen DomUs while pointing to the DRBD devices with phy: in the DomU config files.

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

tag 554805 + patch thanks The problem to solve is that qemu-ifup assumes the world is always bridged, and vif-routed does not know of the concept of TAP devices, and even if it did, it has at this point no way to get at qemu's TAP device anyway. The following set of patches help run in the ioemu-HVM situation: * xend-image.py.diff : modifies the HVM loader so that when running in

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

What are the settings that I must specify to have DomU be saved and then automatically started on reboot of the physical server? In my /etc/sysconfi/xendomains it points to a save folder (which does not exist) My configuration files are located at /vm/cfg/vm-xxxx/vm-xxxx.xen   In my config file I have: on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash =

Hello! I am using xen some years now and it just runs without any problems. But now one customer needs a stupid WinXP domU and I am trying to get this running for about two weeks... I am using 2.6.26-2-xen-amd64 kernel, set up a dummy network auto dummy0 allow-hotplog dummy0 iface dummy0 inet static address 10.0.0.1 netmask 255.255.255.0 broadcast 10.0.0.255 xend-config: (network-script

Hello, I am having some routing troubles with my Xen setup. I have two domUs, one running as a firewall and another running as a dmz: The dom0 has the following: - eth0 bridge (10.0.0.3/24) The domU-firewall has the following: - Direct passthrough PCI NIC (Public Internet) - Virtual NIC connected to the eth0 bridge on dom0 (10.0.0.1/24) - Bridge called brdmz for the dmz zone (10.0.2.1/24)