search for: xen_vers

Hi all, All of a sudden my xend is crashing, when i do "xm create domu" due to which the domains are created in paused state. Iam using minios as domU kernel, but the problem occurs even for linux-2.6.18.1 pv kernel as domu kernel. xend.log shows [2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it.... after doing some preliminary

..., .long hypercall_page - ELFNOTE "Xen", XEN_INFO, .asciz "FEATURES=!writable_page_tables|!auto_translated_physmap" + ELFNOTE(Xen, XEN_ELFNOTE_GUEST_OS, .asciz, "linux") + ELFNOTE(Xen, XEN_ELFNOTE_GUEST_VERSION, .asciz, "2.6") + ELFNOTE(Xen, XEN_ELFNOTE_XEN_VERSION, .asciz, "xen-3.0") + ELFNOTE(Xen, XEN_ELFNOTE_VIRT_BASE, .long, __PAGE_OFFSET) + ELFNOTE(Xen, XEN_ELFNOTE_ENTRY, .long, startup_xen) + ELFNOTE(Xen, XEN_ELFNOTE_HYPERCALL_PAGE, .long, hypercall_page) + ELFNOTE(Xen, XEN_ELFNOTE_FEATURES, .asciz, "!writable...

...- .ascii ",PAE=yes" -#else - .ascii ",PAE=no" -#endif - .ascii ",LOADER=generic" - .byte 0 -.previous - ELFNOTE(Xen, XEN_ELFNOTE_GUEST_OS, .asciz, "linux") ELFNOTE(Xen, XEN_ELFNOTE_GUEST_VERSION, .asciz, "2.6") ELFNOTE(Xen, XEN_ELFNOTE_XEN_VERSION, .asciz, "xen-3.0")

...rote __PAGE_OFFSET into that field. This field defaults to 0 + * if not present. + * + * LEGACY: ELF_PADDR_OFFSET. (n.b. legacy default is VIRT_BASE) + */ +#define XEN_ELFNOTE_PADDR_OFFSET 4 + +/* + * The version of Xen that we work with (string). + * + * LEGACY: XEN_VER + */ +#define XEN_ELFNOTE_XEN_VERSION 5 + +/* + * The name of the guest operating system (string). + * + * LEGACY: GUEST_OS + */ +#define XEN_ELFNOTE_GUEST_OS 6 + +/* + * The version of the guest operating system (string). + * + * LEGACY: GUEST_VER + */ +#define XEN_ELFNOTE_GUEST_VERSION 7 + +/* + * The loader type (string...

I''m continuing to work on making a new XenCD as previously discussed here. In the course of that work, I''ve generated (actually, currently stuck on) the enclosed crash dump. Thought I''d forward it for interest. To head off questions, you''ll see references to a very large initrd (~114 Mb). The Xen dump may or not be related to this unusual usage.

Hi, I noticed the earlier thread on this started by Scott Koranda (sorry - was reading off gmane so I can''t reply to thread) I have exactly the same symptoms: machine hangs as soon as I attempt to start a single domU, just after emitting "using config file..." At that point the machine appears completely wedged. The sequence of 3 ^A on the console no longer does

Hi, I did not find any hints in the web where to configure/setup/manipulate the rx/tx ring buffer allocation within dom0 for xen-unstable, maybe someone here can nudge me towards the right knob. The problem: when booting a handful of domUs and connecting them (comprising a small experimental IP network with links and nodes etc.), some interfaces that have been given by the configuration files

Hello all; I am trying to create SuSE10 guest under my FC5 host, this configuration has worked before but due to abnormal shutdown of my server i get the following error while trying to create the guest OS; ** the same configuration *used to* work just fine *#xm create -c /etc/xen/suse.cfg* ------------------------------------------------------------------------------------- Using config file

Hi there I get the following error message when i try to "xm create <domid>" Error: Error creating domain: (22, ''Invalid argument'') I have included everything i can think of Thanks The DomU config is kernel = "/boot/vmlinuz-2.6.12-xenU" ramdisk = "/boot/initrd-2.6.12.6-xenU.img" memory = 128 name = "xen01" nics=1 disk = [

I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but on my EMT64 blades, it does not. Has anyone else encountered this problem on EMT64 hardware? Here are the errors I am getting: This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): kernel (hd0,0)/boot/xen.gz dom0_mem=256000 com2=19200,8n1

Hi, Thanks to everyone involved in the Xen project. I think it is great and can''t wait to get my hands dirty with it. In the meantime, I cannot boot Dom0 on an ibm x335 and I am not sure what the problem is. Any insights are welcome. Here is what my grub.conf file looks like: title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=/dev/sda9

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

This implements a loader for version 2.07 boot protocol bzImage format files. This allows a single bzImage kernel file to boot either native from a normal bootloader (grub, etc), or paravirtualized under Xen. These bzImages have two changes to make this possible: 1. There's a new field for the bootloader to tell the booted kernel what kind of environment its coming up under. We

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

I have a 2 way machine. Soliciting folks opinion on whether it makes sense to smp enable DOM0 so that IO handling can be balanced over both CPU''s... Opinions? Thanks, Scott _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

hi: I had installed Xen-2.0.6 on my server DELL 2850 with 6G memory, dual Xeon CPU, it''s can''t use all 6G memory, i had upgrade to Xen-unstable, it''s still can use 3.3G memory. [root@CentOS4 ~]# xm dmesg __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _`

Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed,