similar to: dom0 network interface intermittent

Can anybody tell me if it makes a difference if domU''s have separate LVM volume groups? For instance, the Xen User Manual ( http://tx.downloads.xensource.com/downloads/docs/user/#SECTION03330000000000000000) says, when setting up a domU''s disks with LVM, to do a vgcreate vg /dev/sda10 Should each domU have it''s own volume group, or can all the domU''s share

Hi all, This is a dom0 NAT question. /etc/xen/xend-config.sxp (network-script my-network-bridge) (vif-script vif-bridge) there are two physical network cards on the box and my-network-bridge creates two bridges. domU''s use these bridges. I have some windows pc''s connected to one of the nics and I would like to use dom0 route their traffic and do SNAT. (firewall/router setup)

Hello, Where can I find a link (or docs) to *working* network config for xen 4.1.2? My tests (s. below) were not successful. Thank you in advance for any hints. Regards, Mark # --- root@xen411dom0:~# cat /etc/network/interfaces # Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or # /usr/share/doc/ifupdown/examples for more information. auto lo iface lo inet loopback auto bond0

Hello guys, I am setting up dom0. I have read that is recommended restricting one cpu for dom0. In the xen wiki there''s a list of grub parameters http://wiki.xen.org/wiki/Xen_Hypervisor_Boot_Options but it seems deprecated? http://groups.google.com/group/ganeti/browse_thread/thread/a18979bdd00f6461 Do you guys use this option (maxcpus) as shown here as well?

Hello, We have a machine (Debian Etch, Xen from Debian repositories, etc.) with two NICs: one for LAN (192.168.0.0/24) and another one with public IP address. After enable Bridging (in /etc/xen/xend-config.sxp): (network-script ''network-bridge netdev=eth0'') (vif-script vif-bridge) # eth0 is the LAN NIC I have eth0, peth0, vif0.1 (I guess that it''s usual for you) and

I set GRUB_CMDLINE_XEN="dom0_mem=1024M" and put "(dom0-min-mem 1024)" and "(enable-dom0-ballooning no)" in xend-config.sxp. Then in upgrading the machine''s RAM, MemTotal in dom0''s /proc/meminfo is 906864 with 4GB, but only 779900 with 16GB. Does that seem reasonable? Is Xen hiding part of that 1024M from dom0 to...manage the larger memory?

Hello Friends, good afternoon I'd like to ask about stored settings of dom0 and guests machine. For example, I've a SunFire x4600 with 32GB/Ram and 16 CPU's (8 CPU's dual core). When I power on my system, with the command #xm vcpu-list, I can see this [root at srv ~]# xm vcpu-list Name ID VCPUs CPU State Time(s) CPU Affinity Domain-0

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from

Hi, I've tried to get my sarge desktop booting under the xen hypervisor, and have been having some problems. I've asked about it on the xen-users mailing lists, the #xen irc channel with oftc, and on the sage-au mailing lists, but not had any answers at all. I can boot into the system, but the boot process seems to freeze during the /etc/rc2.d/S* scripts. It used to freeze while

Hi, We''re trying to run Xen on a Debian "Etch" base system (kernel 2.6.18-6-xen-amd64), but have come across a strange networking error whenever bridging (vif-bridge/network-bridge) is in operation. The symptom is that the dom0 base system loses all network connectivity to the outside world while the two guest instances function perfectly well. As far as we can tell, we

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

Hello! I have two problems. One is, that I cannot ping a DomU from Dom0 (or any other host in my local network) and the second one is, that I cannot ping the same site (eg. www.suse.com) from two DomU''s at the same time. I have a fresh installation of openSuse 11.0 with Kernel 2.6.25.20-0.1-xen and my box has two physical ethernet cards. As far as I have investigated, eth0 is the one

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any

Package: xen-utils-common Version: 4.4.1-9 Severity: important This bug was already reported as #763102 and was brushed off because maintainer says it implicates xend which is not there in 4.4 anymore. However, this problem is present during upgrade from wheezy to jessie and means that reboots are not possible without physical interventions. As noted in #763102, during shutdown, we can see this

Is there any reason why I would not want to set dom0-min-mem to 0 or to what I set dom0_mem on my kernel line? Setting to 0 or setting to the same value as dom0_mem disables memory balloon correct? I cant seem to think of a reason why I would want memory ballooning. Also setting dom0-min-mem should that be done in xend-config.sxp or on the kernel command line? -- Nick Anderson

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to

Hi I was experimenting with Xen(-2.0) on NetBSD last summer and I have been trying it on Debian GNU/Linux recently. I was surprised to see that my guest OS had no Internet connectivity. I took the Xen documentation, but did not find any clue: the doc basically tells ``everything should work out of the box''. I spoke about that with a friend who had already used Xen under Debian and he

> On Sat, Apr 16, 2016 at 5:40 PM, rgritzo <rgritzo at gmail.com <https://lists.centos.org/mailman/listinfo/centos-virt>> wrote: > > so i guess i was not paying too close attention and upgraded to xen 4.6.1 before i migrated my domU configurations to libxl :{ > > Just FYI, as a fall-back you can always move yourself to the Xen 4.4 "track" by: > 1.