search for: guest_ver

...l_page) .byte 0 .previous -#define XEN_INFO 0 /* name=value pair */ -#define XEN_ENTRY 1 /* entrypoint */ -#define XEN_HYPERCALL 2 /* hypercall page address (not pfn) */ - - ELFNOTE "Xen", XEN_INFO, .asciz "GUEST_OS=linux" - ELFNOTE "Xen", XEN_INFO, .asciz "GUEST_VER=2.6" - ELFNOTE "Xen", XEN_INFO, .asciz "XEN_VER=xen-3.0" - ELFNOTE "Xen", XEN_ENTRY, .long startup_xen - ELFNOTE "Xen", XEN_HYPERCALL, .long hypercall_page - ELFNOTE "Xen", XEN_INFO, .asciz "FEATURES=!writable_page_tables|!auto_translated_...

...(\value) < 0 || (\value) >= 0x10 - utoa (((\value)>>4)&0x0fffffff) - .endif - .if ((\value) & 0xf) < 10 - .byte '0' + ((\value) & 0xf) - .else - .byte 'A' + ((\value) & 0xf) - 10 - .endif -.endm - -.section __xen_guest - .ascii "GUEST_OS=linux,GUEST_VER=2.6" - .ascii ",XEN_VER=xen-3.0" - .ascii ",VIRT_BASE=0x" - utoa __PAGE_OFFSET - .ascii ",ELF_PADDR_OFFSET=0x0" - .ascii ",VIRT_ENTRY=0x" - utoa (__PAGE_OFFSET + __PHYSICAL_START + VIRT_ENTRY_OFFSET) - .ascii ",HYPERCALL_PAGE=0x" - utoa ((__...

...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). + * + * LEGACY: LOADER + */ +#define XEN_ELFNOTE_LOADER 8 + +/* + * The kernel supports PAE (x86/32 only, string = "yes" or "no"). + * + * LEGACY: PAE (n.b. The legacy interface included a pro...

...PCI hardware (bus 00) (XEN) PCI: Using IRQ router PIIX/ICH [8086/7110] at 00:07.0 (XEN) PCI: Cannot allocate resource region 4 of device 00:07.1 (XEN) Limiting direct PCI/PCI transfers. (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 00c00000->00ffcd48 (XEN) Initrd image: 00ffd000->08bbb000 (XEN) Dom0 alloc.: 08c00000->1c300000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kerne...

...rm: (B3,I4,P0) -> 17 (XEN) PCI->APIC IRQ transform: (B3,I5,P0) -> 18 (XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 19 (XEN) PCI->APIC IRQ transform: (B3,I7,P0) -> 16 (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=ge neric,PT_MODE_WRITABLE'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 00c00000->0103f584 (XEN) Initrd image: 00000000->00000000 (XEN) Dom0 alloc.: 01400000->21400000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded ker...

...bytes/line) (XEN) CPU0: AMD Athlon(tm) stepping 01 (XEN) SMP motherboard not detected. (XEN) spurious 8259A interrupt: IRQ7. (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 1 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LO ADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 02000000->04000000 (24576 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c0660904 (XEN) Init. ramdisk: c0661000->c102500...

...---------------------------------------------------------------------------------- */var/log/xend-debug.log:* --------------------------------------------------------------------------------------------- ERROR: Will only load images built for Xen v3.0 ERROR: Actually saw: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0 ,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic'' ERROR: Error constructing guest OS Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 77, in op_create dominfo = self.xd.domain_create(config) File &...

...ailed. (XEN) ...trying to set up timer as Virtual Wire IRQ... works. (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=yes,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000007800000->0000000008000000 (129024 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c06205e4 (XEN) Init. ramdisk: c06...

...s 4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:D6987764 (XEN) .... scale: 00000001:1C6B619C (XEN) .... Wall Clock: 1118847138s 160000us (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80100000,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000008000000->0000000010000000 (31232 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80100000->ffffffff80578086 (XEN) Ini...

...XEN) PCI->APIC IRQ transform: (B0,I15,P0) -> 11 (XEN) PCI->APIC IRQ transform: (B1,I1,P0) -> 22 (XEN) PCI->APIC IRQ transform: (B2,I1,P0) -> 24 (XEN) PCI->APIC IRQ transform: (B2,I2,P0) -> 25 (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE= 0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 02800000->02bbdf08 (XEN) Initrd image: 00000000->00000000 (XEN) Dom0 alloc.: 02c00000->0ac00000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded ker...

....193MHz PIT (XEN) Brought up 2 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) mtrr: your CPUs had inconsistent fixed MTRR settings (XEN) mtrr: probably your BIOS does not setup all CPUs. (XEN) mtrr: corrected configuration. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xffffffff80000000,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000020000000->0000000040000000 (382799 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80100000->ffffffff805ab086 (XEN) In...

Here are two patches that let xm create, save and restore extract and preserve elfnotes read by the domain builder. This is handy for a few things. In particular, I''d like it so that xm can decide whether or not guest domains support fast resume (if save fails, or for checkpointing). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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

...4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:BE46EF60 (XEN) .... scale: 00000001:40C515C9 (XEN) .... Wall Clock: 1121013264s 120000us (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,LOADER=ge neric'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 08000000->10000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c040b65c (XEN) Init. ramdisk: c040c000->c0509800 (XEN) Phys-Mach map: c050a000->...

...4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:BE46EF60 (XEN) .... scale: 00000001:40C515C9 (XEN) .... Wall Clock: 1121013264s 120000us (XEN) Brought up 4 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,LOADER=ge neric'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 08000000->10000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c040b65c (XEN) Init. ramdisk: c040c000->c0509800 (XEN) Phys-Mach map: c050a000->...

I''ve had domU''s hickup a few times with latest unstable, and I guess this can be expected. Is there a procedure in place to report these problems? For exampe: Unable to handle kernel paging request at virtual address c12b46c0 printing eip: cpanel cpanel.mydomain c02555f7 *pde = ma 7e9fc067 pa 00002067 *pte = ma 00000000 pa 55555000 Oops: 0002 [#1] PREEMPT SMP Modules

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:

...2200+ stepping 01 (XEN) Total of 1 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) Platform timer is 1.193MHz PIT (XEN) Brought up 1 CPUs (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 01800000->02000000 (30720 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c046ed7c (XEN) Init. ramdisk: c046f000->c046f000...

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