Displaying 5 results from an estimated 5 matches for "pvops_dom0".
2009 Nov 10
17
[ANNOUNCE] Xen 3.4.2 released
Folks,
Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There
are a range of bug fixes since 3.4.1, and we recommend users to upgrade.
The source repository can be downloaded from:
http://xenbits.xensource.com/xen-3.4-testing.hg
The release is tagged ''RELEASE-3.4.2''.
Alternatively source tarballs can be downloaded from:
2009 Nov 10
17
[ANNOUNCE] Xen 3.4.2 released
Folks,
Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There
are a range of bug fixes since 3.4.1, and we recommend users to upgrade.
The source repository can be downloaded from:
http://xenbits.xensource.com/xen-3.4-testing.hg
The release is tagged ''RELEASE-3.4.2''.
Alternatively source tarballs can be downloaded from:
2009 Nov 30
3
32bit domUs
Hey all,
I have need to boot 32bit domu''s on a amd64 system. I was able to deploy a 32bit image but the kernel is still 64bit. I have a feeling in my .cfg file for the domU I need to specify a 32bit kernel. Is this correct?
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2010 Jan 13
65
ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
On a selection of boxes, ntpd running in Xen Dom0 reproducibly
exhibits extermely high noise/jitter.
Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise.
Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0?
Is the problem a config issue, or a bug?
Already reported this downstream; everybody''s "stumped".
2010 Jan 13
65
ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
On a selection of boxes, ntpd running in Xen Dom0 reproducibly
exhibits extermely high noise/jitter.
Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise.
Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0?
Is the problem a config issue, or a bug?
Already reported this downstream; everybody''s "stumped".