search for: dom0s

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

Hello, I made an interesting observation related to the "Clocksource tsc unstable (delta = -2999660320319 ns)" problem. In the log of ntpd I found: Oct 5 03:46:35 greenville-dom0 ntpd[4020]: kernel time sync status change 6001 Oct 5 04:03:41 greenville-dom0 ntpd[4020]: kernel time sync status change 2001 Oct 5 05:29:03 greenville-dom0 ntpd[4020]: kernel time sync status change

Hello ! Just a quick question about time synchronization between xen dom0 and domUs... We''re running Xen 3.1 64-bit, with 32 and 64 bits linux guests. It''s up since 89 days and the domU''s time is around 5 minutes behind the dom0, which is updated via ntpdate... Any idea why it doesn''t sync the guests even that /proc/sys/xen/independent_wallclock is 0 ?

I''m trying to configure GRUB to allocate fixed amount of dedicated memory to dom0, according to this best practices thread (http://wiki.xensource.com/xenwiki/XenBestPractices | "Xen dom0 dedicated memory and preventing dom0 memory ballooning "). When I reboot, dom0 has the fixed amount of memory as it was configured, but neither xm info shows the rest of memory available

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having some dom0 running 2.6.18-53.1.6.el5xen (x86_64). On the dom0 where the load is high (more than 70% of total system memory consumed by dom0 and domU) we have a lot of "memory squeeze ". The result is that the domU seems to be blocked (no network/no disk acces/ etc....). Looking for a solution in xen

Hello, I thinking about using PCI passthrough to dedicated a domU as firewall. I understand PCI passthrough concept. When done, my domU will see network card and the dom0 won''t any more. So I''ll be able to filter all trafic from outside, since it will go through network domU. Then, how will I be able to connect other domU (and maybe dom0) to the network domU ? In a normal way,

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

Hello folks, I have a Xen server running on Centos 6.2 with 3.6.6-1.el6xen.x86_64 as the Dom0 kernel, and i have dedicted 2 CPUs and 4G ram for the Dom0.I have close to 4-5 Virtual machines running on the Xen server. The problem is that for some reason,carrying outany CPU/Disk intensive task on the Dom0 seems to be affecting the DomUs adversly.For ex.i noticed that my Domus become extremly

Hi all, I have upgraded a test machine from OpenSuSE 11.1 to 11.2. I have found following bug: the server is a 2x quadcore intel box also 2x4=8cpu If you limit the dom0 cpu with dom0-cpus= [1-7]: - [xenwatch_cb] is running 100% cpu and makes var log entry every 65 sec BUG: soft lockup - CPU#X stuck for 61s! - xm commands not work - xend is dead if set dom0-cpus to 0 or 8: - everything looks

I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,

Hello, I read, and know, that ZFS + XEN are not works well together. (I''ve only 512MB for Dom0). How I can disable/off all ZFS stuff to have more usable memory to Dom0. Regards Maciej

Hello, I have a network issue in dom0; I''m not sure if it''s a configuration problem or a design problem in my setup. My setup: The server (dom0) runs Ubuntu 7.10, Xen was installed using apt-get (means version: Xen 3.10, Kernel 2.6.22-14). This server has 4 NICs. I use bridged networking with my own script which creates 4 bridges ("$dir/network-bridge"

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Renato, When I tried running "opcontrol --start" (after previously running "opcontrol --start-daemon") in dom0, I get this error message: /usr/local/bin/opcontrol: line 1639: echo: write error: Operation not permitted and this message in the Xen console: (XEN) xenoprof: operation 9 failed for dom 0 (status : -1) It looks like opcontrol is trying to do this: echo 1 >

Hi, dom0: Debian Lenny 2.6.26-2-xen-amd64, domU: same. Xen 3.2-1 After resizing a LV on dom0, Xen is not reporting the new extended size to the PV domU even though dom0 is well aware of the new size. I''ve rebooted domU (not dom0 yet as that''s running a lot of other domU''s). The LV I tried to resize is encrypted. Resizing unencrypted volumes works as expected. dom0:~#

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hi experts, Q1:What''s the different for "dom0_max_vcpus=4 dom0_vcpus_pin" and "dom0_max_vcpus=4" ? which will get better performance Q2: dom0_max_vcpus=4 means "core0-3 will be just used by dom0" or means "4 cores(not dedicate cores) will be used by dom0, eg: core2-5 or core3-6? Q3.what does mean "nosmp" , xen, dom0,domU, will just use one

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an

Hi , I have been trying to understand PCI -passthrough support. Please correct me if I am wrong in my following inferences. 1. Device emulation and pass through are both implemented using split drivers. 2. But, in case of emulation drivers of dom0 are used where as in case of passthrough ( as the name suggests ) native drivers in domU are used . 3. dom0 provides a virtual PCI device { an