search for: __xen_guest

With a suitably recent xen the __xen_guest string is no longer required so remove it. See the caveat in 0/5 though! Should be merged into 024-head.patch Signed-off-by: Ian Campbell <ian.campbell@xensource.com> diff -r 82192f4547ab arch/i386/paravirt-xen/xen-head.S --- a/arch/i386/paravirt-xen/xen-head.S Wed Aug 23 15:15:18 2006 +01...

...s world, I did a search around looking for a solution on this problem and I could find anything I''ve a new server Dell R900 (Two QuadCore 2.93Ghz, 32GB Ram) where the following message appear when I try to boot any DomU guest machine: ERROR: Not a Xen-ELF image: No ELF notes or ''__xen_guest'' section found. ERROR: Error constructing guest OS I already tried with CentOS 5.2 (amd64) with Xen 3.1, Debian Etch (amd64 & i386-pae) with Xen 3.0 and Xen 3.2 because I find some references saying that you can''t run 64bit host and 32bit guest before Xen 3.2, but nothing hel...

...completely new. I've made a note in the intro to the individual patches. There is one caveat which is that shadow mode for paravirt guests seems to be a little broken at the current tip of xen-unstable so you may want to stick where you are for now and not apply patch #4 (the one which removes __xen_guest from the header). The rest of the series is fine to apply whether you update or not. Sorry for the lack of References: from the patches to this mail, I'm doing this manually. If anyone has any pointers to a decent patchbomb script I'm all ears ;-) Ian.

Hi, i try the kernel from [1] and get: WARNING: vmlinux.o (__xen_guest): unexpected non-allocatable section. Did you forget to use "ax"/"aw" in a .S file? Note that for example <linux/init.h> contains section definitions for use in .S files. WARNING: modpost: Found 2 section mismatch(es). To see full details build your kernel with: ''...

..._PUBLIC_ELFNOTE_H__ +#define __XEN_PUBLIC_ELFNOTE_H__ + +/* + * The notes should live in a SHT_NOTE segment and have "Xen" in the + * name field. + * + * Numeric types are either 4 or 8 bytes depending on the content of + * the desc field. + * + * LEGACY indicated the fields in the legacy __xen_guest string which + * this a note type replaces. + */ + +/* + * NAME=VALUE pair (string). + * + * LEGACY: FEATURES and PAE + */ +#define XEN_ELFNOTE_INFO 0 + +/* + * The virtual address of the entry point (numeric). + * + * LEGACY: VIRT_ENTRY + */ +#define XEN_ELFNOTE_ENTRY 1 + +/* Th...

...uddenly. Any clue or hints would be very helpful. here is a sample domain_builder log when xend crashes.... xc_dom_parse_image: called xc_dom_find_loader: trying ELF-generic loader ... OK elf_parse_binary: phdr: paddr=0x0 memsz=0x1dfa4 elf_parse_binary: memory: 0x0 -> 0x1dfa4 elf_xen_parse: __xen_guest: "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,PAE=yes,LOADER=generic" elf_xen_parse_guest_info: GUEST_OS="Mini-OS" elf_xen_parse_guest_info: XEN_VER="xen-3.0" elf_xen_parse_guest_info: VIRT_BASE="0x0" elf_xen_parse_g...

I am learning xen's memory management recently. I find most docs is how to use the hypercall related memory management. Can somesome tell me where is the implementation of the them in the xen source. Or some docs explaining it will be ideal. 年少不惧江湖老，放歌四海任逍遥。未解前路多少事，欲与青天试比高。 _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

...nel 3) CentOS (2.6.18-128) XEN domU <= domU kernel Booting entry 1 shows -------------------------------------------------------------------------------------------------- (2, ''Invalid kernel'', "elf_xen_note_check: ERROR: Not a Xen-ELF image: No ELF notes or ''__xen_guest'' section found.\n") -------------------------------------------------------------------------------------------------- Booting entry 2 shows -------------------------------------------------------------------------------------------------- Error: (2, ''Invalid kernel'...

>> + * __xen_guest information >> + */ >> +.macro utoa value >> + .if (\value) < 0 || (\value) >= 0x10 >> + utoa (((\value)>>4)&0x0fffffff) >> + .endif >> + .if ((\value) & 0xf) < 10 >> + .byte ''0'' + ((\value) & 0xf) >> + .e...

I've updated the patches at http://ozlabs.org/~rusty/paravirt/?mf=33ba6c4fce13;path=/ to carve out the basic shape of how I see all this fitting together. These patches implement an initial set of Xen paravirt ops, as well as adapting head.S to set up a Xen-specific entrypoint. The head.S code does absolutely minimal setup, and then calls xen_start_kernel(). This installs the Xen

Hi Rusty, I had a look over your 011-paravirt-head.S.patch. I'm struggling to come up with a list of any benefits over having separate entrypoints for each hypervisor. Multiple entry pros: * allows maximum startup flexibility for any given hypervisor * for Xen at least, it's pretty simple * the "what hypervisor am I under" question is answered trivially cons:

I am getting the following error when I try to bring up Mini-OS on x86_64 Xen (unstable: 9994). It is dying in xc_linux_build() causing xend to fault and restart. Any clue why this happening? Has something changed in the builder that Mini-OS needs to be aware of? PS: I tried reverting changeset 9993 (Allow linking of mini-os with application-specific object code), but still got the same error

Hi all, I have a Sun x2200 named Adra running OpenSolaris 2008.11 set up as a Dom0 per Levon''s instructions on this site. It hosts some production services and has been running nice and stable for a number of months now (with NetWare DomUs running GroupWise, believe it or not). The machine is pretty nicely speced out and there''s room for more virtualisation, so I was

Hi, i''am trying to build a Gentoo Dom0-kernel booting a HP DL380 G6. Has anyone twiddled a working kernel configuration for this hardware? i do have the linux-2.6.32-xen-r1 sources checked out by portage and tried some configurations. Olaf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...omainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x99ff60 xc: detail: elf_parse_binary: memory: 0x0 -> 0x99ff60 xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mini-OS,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPE RCALL_PAGE=0x2,LOADER=generic" xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mini-OS" xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" xc: detail: elf_xen_parse_guest_info: VIRT_BASE=&q...

Hello, I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN and copied the blk files from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN (I don''t know which of these patches have been applied to xen unstable, so

...#define __ASSEMBLY__ +#include <xen/interface/elfnote.h> +#endif + #include "assym.s" /* @@ -86,3 +92,50 @@ NON_GPROF_ENTRY(btext) ALIGN_DATA /* just to be sure */ .space 0x1000 /* space for bootstack - temporary stack */ bootstack: + +#ifdef XENHVM +/* Xen */ +.section __xen_guest + ELFNOTE(Xen, XEN_ELFNOTE_GUEST_OS, .asciz, "FreeBSD") + ELFNOTE(Xen, XEN_ELFNOTE_GUEST_VERSION, .asciz, "HEAD") + ELFNOTE(Xen, XEN_ELFNOTE_XEN_VERSION, .asciz, "xen-3.0") + ELFNOTE(Xen, XEN_ELFNOTE_VIRT_BASE, .quad, KERNBASE) + ELFNOTE(Xen, XEN_ELFNOT...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths