search for: compat32

...: false no runlevel check : false no network : false no ABI note : false no RPMs : false no kernel module : false force SELinux : default no X server check : false force tls : (not specified) force compat32 tls : (not specified) X install prefix : (not specified) X library install path : (not specified) X module install path : (not specified) OpenGL install prefix : (not specified) OpenGL install libdir : (not specified) compat32 install chroot : (not specified) compat...

Hello, all I thought dom0 is layed out on physical memory starting 0, linearly, but this message, (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1d87000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000c14000000->0000000c18000000 (498514 pages to be allocated) shows the address range 0000000c14000000->0000000c18000000 , what is this? it''s 64MB ran...

...tualisation disabled (XEN) Total of 6 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 6 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x1000000 -> 0x16be000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000230000000->0000000232000000 (2031119 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff81000000->ffffffff816be000 (XEN) Init....

...c). I''m using xen 3.1 on Centos 5, binary distributed kernel, 64 bit mode, ''2.6.18-xen'', IBM bladecenter. Something from "xm dmesg" (which does not otherwise contain errors or info on my problem): (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff805b0e6c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007d000000->000000007e000000 (477266 pages to be allocated) Anyway, I cannot start any VM. Now I *have* been looking around for this error message bu...

I'm trying to get wine working on my slackware 13.37 64bit system. I downloaded and installed the wine-1.3.19-x86_64-lsg.txz package. That went fine and I can run /usr/bin/wine64 to confirm the version and stuff. When I try to run or install any pc applications this is what I get: Code: bash-4.1$ wine64 asdf.exe /lib/ld-linux.so.2: could not open There is no /lib/ld-linux.so on my

...(XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs disabled. (XEN) HVM: VMX enabled (XEN) Brought up 8 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1c00000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000040c000000->0000000410000000 (4095169 pages to be allocated) (XEN) Init. ramdisk: 000000041fa89000->000000041ffffe00 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) L...

...t Branch Record (LBR) Virtualisation (XEN) - Next-RIP Saved on #VMEXIT (XEN) HVM: SVM enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Brought up 4 CPUs (XEN) Xenoprofile: Failed to setup IBS LVT offset, IBSCTL = 0xffffffff (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff808e302c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000238000000->0000000239000000 (255908 pages to be allocated) (XEN) Init. ramdisk: 000000023f7a4000->000000023ffffa00 (XEN) VIRTUAL MEMORY ARRANGEME...

...ocessor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) EPT supports 2MB super page. (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Brought up 8 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x205f000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000032c000000->0000000330000000 (3048830 pages to be allocated) (XEN) Init. ramdisk: 000000033d7fd000->0000000340000000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN)...

...SC synchronization across 16 CPUs: passed. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 16 CPUs (XEN) I/O virtualisation disabled (XEN) CPUIDLE: disabled due to no HPET. Force enable with ''cpuidle''. (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff8075550c (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000062c000000->000000062e000000 (188416 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff80755...

...MHz. (XEN) ..... host bus clock speed is 200.0128 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) Platform timer overflows in 8589 jiffies. (XEN) Platform timer is 25.000MHz HPET (XEN) Brought up 8 CPUs (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff807014e4 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000022a000000->000000022c000000 (122880 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff...

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

Hi, I''ve recently setup a few machines with 3.2 64bit without any unresolvable problem. These machines all run pv domU''s and a view "basic" hvm domUs. As I''ve got one machine left for internal use and testing, I would like to take a look at pciback with VT-d support (bios screen shows a VT-d [enable|disable]). My question is, do I need to add patches, or use

...cessors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) I/O virtualisation disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff807014e4 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000134000000->0000000136000000 (969614 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff80701...

A few weeks back Robert Watson announced the merge of these features from 7 back into 6-STABLE. I hadn't seen any updates and was curious as to the status. Us 6-STABLE users are curious to test it out. Thanks. --A

...virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff806e2f04 (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff806e2f04 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007a000000->000000007c000000 (470828 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff806...

(CCed to xen-devel for completeness. ;) On Wed, 2006-08-16 at 17:24 +0200, Tristan Gingold wrote: > I am porting xen-ppc''s xencomm to xen/ia64. > Currently on xen/ia64 copy_from/to_guest uses guest virtual address. This > works well as long as the virtual addresses are in the TLB. When not in TLB > (or vTLB) the hypercall can''t success without domain help. The

...al of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer overflows in 234 jiffies. (XEN) Platform timer is 3.579MHz ACPI PM Timer (XEN) Brought up 2 CPUs (XEN) AMD IOMMU: Disabled (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x631918 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000128000000->000000012c000000 (978399 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff80631918 (XEN) Init. ram...

...elf_paddr_offset = 0x0 (XEN) virt_offset = 0xffffffff80000000 (XEN) virt_kstart = 0xffffffff81000000 (XEN) virt_kend = 0xffffffff82197000 (XEN) virt_entry = 0xffffffff81ac41e0 (XEN) p2m_base = 0xffffffffffffffff (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x2197000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000224000000->0000000228000000 (182927 pages to be allocated) (XEN) Init. ramdisk: 000000023218f000->000000023fe00000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Lo...

...r Identifiers (VPID) (XEN)? - Virtual NMI (XEN)? - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 8 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN)? Xen? kernel: 64-bit, lsb, compat32 (XEN)? Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x193d000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN)? Dom0 alloc.:?? 0000000224000000->0000000226000000 (507577 pages to be allocated) (XEN)? Init. ramdisk: 000000022deb9000->000000022ffffa00 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN)? Lo...