similar to: NTP problem in PAE kernel

Hi Is there a doc/wiki page which explains, the kind of domu images/appliances/kernels can be run with what type of dom0 kernels(xen_caps). For example : -- Can a 32 bit, non-PAE domU run on 64 bit, PAE dom 0 in PV mode ? (or HVM mode ?) Are there any checks that can be done before doing the migration ? Is there any programmatic way (from python) to find out if the kernel in a domU disk

Hi, Did I get it right or is it a confusion in my mirrors, that the change from linux-image-2.6.18-3-xen-686 to linux-image-2.6.18-4-xen-686 also changed the PAE mode of the Kernel? After installing this new version and and changeing the kernel in a domU config, I get: Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32p not supported by xen kernel,

Processing commands for control at bugs.debian.org: > reassign 469811 linux-2.6 Bug#469811: xen-hypervisor-3.0.3-1-i386-pae: kernel BUG at drivers/xen/core/evtchn.c:481 Bug reassigned from package `xen-hypervisor-3.0.3-1-i386-pae' to `linux-2.6'. > forcemerge 410807 469811 Bug#410807: linux-2.6/etch xen support - kernel BUG at drivers/xen/core/evtchn.c:481 Bug#469811:

We currently ship a PAE 32-bit domU that we can trivially make bimodal, except that if we set it to "bimodal", then older Xens will default to thinking the domU is not PAE: 353 dsi->pae_kernel = PAEKERN_no; 354 if ( dsi->__elfnote_section ) 355 { 356 p = xen_elfnote_string(dsi, XEN_ELFNOTE_PAE_MODE); 357 if ( p != NULL && strncmp(p,

I think it''s perfect the way it is. Run NTP in dom0, all the domU''s then have synchronized time. I can still set timezones on all of these boxes independantly. Timezone has nothing to do with NTP synchronization. Tim:> > yeah, i''m already doing that, I was just saying, it *seemed* > like they were getting their time from domain0, and weren''t >

Hi everyone, I have the problem with Xen domU's and timekeeping in dom0. Time in dom0 was incorrect by 5 hours due to wrong timezone assumed. Fixed it by ntpdate ntp.nist.gov. The time on a dom0 was changed. I didn't append xen.independent_wallclock=1 to sysctl.conf thus the time in all domU's was also changed. But THEY DIDN'T "KNOW" THAT! The 'date' output

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e

In a word, is it stable? I''m seeing some odd things; segfaults by postgres in a domU, when pae is enabled. And, this last time, I got this on the ssh I had to the domU: == database:/home/shared/doogie# Message from syslogd@database at Wed Dec 14 18:55:05 2005 ... database kernel: [27073.874149] Bad page state at prep_new_page (in process ''postmaster'', page c1326ca0)

Package: xen-hypervisor-3.0-i386-pae Severity: normal Forwarding a problem reported by Nathan Hawkins. > I ran into a problem with the PAE version of the hypervisor. I'm looking at > xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I > ran into a problem with PAE being disabled in the binary: > > $ zcat xen-3.0-i386-pae.gz | strings | grep PAE

Hello, For a few months I build a new Xen server, both domU en dom0 are 64-bits. I had some hardware problems, that's the reason the server is not doing production-work now, but I would like to go in production real soon. My problem is that I made this server for a longer term. And I don't see a 64-bit domU in the 2.6.25 kernel, only a 32-bit domU kernel with PAE support. My processor

I ran into a problem with the PAE version of the hypervisor. I'm looking at xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I ran into a problem with PAE being disabled in the binary: $ zcat xen-3.0-i386-pae.gz | strings | grep PAE PAE=yes PAE disabled. PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s) It should look like: PAE=yes PAE enabled, limit: %d GB PAE

Hello xen-users, I have two days (or rather nights) ago start to play with xen. I have quite old laptop without PAE support, so when I try to install xen 3.1.0 there was error saying, that I cannot run PAE-enabled kernel on PAE-less processor. So I build and install PAE-disabled kernel (for dom0), but I can''t find the way to turn off PAE i XEN micro-kernel. Is there any manner to change

I need to support 32GB of ram, the 32bit HV wont do this i guess. Can i run a 64bit HV with a 32bit Dom0 and a 32bit DomU? Also, i tried building a 64bit HV on a 32bit dom0 but it failed, is it not possible to build a 64bit HV on a 32bit dom0? ~Shaun _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I found this mail about network problems in the archive. I think I have the same network problems with a routing (with or without NAT) domU connected by two network bridges. The dom0 logs thousands of following messages: -- Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet -- and all outgoing TCP packets have wrong TCP checksums (traced on another machine on the

Hi, I installed Fedora 10 as domU on CentOS 5.3. I need new 2.6.25.14 kernel under domU (in order to patch it for MPLS protocol). I followed advice on http://wiki.xensource.com/xenwiki/Kernel.org_Linux_on_Xen, and compiled kernel with XEN options enabled under domU. I got all relevant packages in /boot and /lib/modules, but when I try to boot virtual machine I got this error: Error starting

This one happened today: Gentoo linux dom0, xen 3.2.0 hypervisor (32-bit), Intel Quad-core cpu, 8GB memory. This linux box / dom0 is up for 40 days. OpenSolaris SXCE snv_81 PV domU (32-bit) Problem: when starting the snv_81 domU, we''re stuck for more than 60 seconds early during bootstrap: v3.2.0 chgset ''unavailable'' SunOS Release 5.11 Version snv_81 32-bit

Hello, I am compiling xen 3.3.1 with linux 2.6.18.8 as domain 0. I am able to compile this successfully on a PAE enabled TOSHIBA machine (However having problems with loading graphics drivers but able to boot with runlevel 3). But since the graphics problem could be because of non standard hardware that comes with Toshiba laptop, I tried compiling the same on an IBM laptop . This system does not

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

attached is the vmx domain save/restore patch. works well for different guest/host combination W/O breaking domu save/restore according to my test. pls. first apply xiaowei''s qemu dm fix. ===know issue=== * shpage pfn * HV look for shpage pfn in an e820 entry when init. but some guest(win/em64t linux) will reuse this e820 ram, which cause losing shpage pfn when restore. so this

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-4 Severity: critical Justification: breaks the whole system Hi! the error suddenly appeared when creating a domU using xm create <name> on our etch server The server freezes and isn't accessible via console/ssh anymore. The server is a Dell PowerEdge 2900 with 2 Quad-Core Xeon E5335 and 8Gb memory. pc307005:~# xm create -c