search for: xen_cap

I''m trying to install RHEL 4 on an HVM (Core 2 Duo). However, when the RHEL installer tries to start the kernel, it complains that the CPU doesn''t support extended mode, and that I should use a 32-bit installer. However: hrm@willow:~$ sudo xm info | grep xen_caps xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 Is there some magic I need in the config file for the domain to tell it that it''s a 64-bit guest? Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 1...

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 image is 32bit/64 bit/PAE/non-PAE/PV/HVM ?...

I am thoughly confused with the various Xen 3.0.3 versions for Suse. Firt there is not for suse 10.1, so I gues I woulllt the source tarball and compile. ( I tried the RPM for 10.0 (I am running SuSE 10.1) but it caused a kernel panic) I have 5 packages listed unter Yast software management (not including documentation,pdf, etc). Kernel-xen ver 2.6.16.21.25 Xen 3.02_09763-0.8 xen-libs

...: 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.9.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_...

I''m a bit confused about the kernel used by the Xen hypervisor. I''ve just installed a 30 day trial of XenSource''s Enterprise edition software on a Sun Fire 4600. It was my understanding that it would install a 64 bit hypervisor, however, upon running uname -a on my machine, I am told that I am running a i686 kernel. Did I miss something? How does one use a 64 bit

I own an Athlon 64 X2 Dual Core Processor 5200+. I enabled SVM extensions on BIOS. I did a power cycle. xm dmesg shows me: (XEN) AMD SVM: ASIDs enabled (XEN) HVM: SVM enabled I run a 64 bit Xen kernel (OpenSuse 11). Xen version is 3.2.1_16881_04-8.6 I _can not_ run any x86_64 O.S on a HVM domU, because it appears something like this: "your cpu does not support long mode. use a 32bit

...: 1 cpu_mhz : 1995 hw_caps : bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001 total_memory : 24570 free_memory : 918 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 2 xen_extra : -1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.3.1 (Debian...

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

...rt_caps : total_memory : 4079 free_memory : 581 node_to_cpu : node0:0-3 node_to_memory : node0:581 node_to_dma32_mem : node0:581 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Mon Aug 02 11:18:41 2010 +0100 21296:e7bd619f8aaa xen_commandline : cc_compiler : gcc versi...

...gt;cpu_mhz : 2793 >hw_caps : >bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 >total_memory : 1023 >free_memory : 62 >xen_major : 3 >xen_minor : 0 >xen_extra : -unstable >xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 >platform_params : virt_start=0xfc000000 >xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d >cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) >cc_compile_by : build >cc_compile...

...00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 3.4.6 200...

...00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 24567 free_memory : 22240 node_to_cpu : node0:0-15 node_to_memory : node0:22240 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 3.4.6 200...

Hello I have Debian Linux 2.6.32-5-xen-amd64 Xen 4.0.1, 2 SAS drives in RAID 1, 16GB ram. I have virtualized Windows 2003R2 32bit where you install the latest version 0.11.0.295 gplpv After reading and reading forums and post testing, I noticed that the hard disk performance drops significantly when I assign the windows domU 9GB ram. (below I leave the config files) If I run the

...virt_caps : hvm > total_memory : 98291 > free_memory : 62390 > sharing_freed_memory : 0 > sharing_used_memory : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 2 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline...

...0:00000000:00000340:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 32758 free_memory : 3974 node_to_cpu : node0:0-15 node_to_memory : node0:3974 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 2008070...

...w_caps : bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000 virt_caps : hvm total_memory : 2037 free_memory : 988 free_cpus : 0 xen_major : 4 xen_minor : 2 xen_extra : .2-23.el6 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : dom0_mem=1024M,max:1024M l...

...aps : total_memory : 6143 free_memory : 2054 node_to_cpu : node0:0-1 node_to_memory : node0:2054 node_to_dma32_mem : node0:1807 max_node_id : 0 xen_major : 4 xen_minor : 0 xen_extra : .1-rc3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : cc_compiler : gcc version 4.4.4 (Debian 4.4.4-5) cc_compil...

...: 1 threads_per_core : 1 cpu_mhz : 2793 hw_caps : bfebfbff:20000000:00000000:00000180:0000e43d:00000000:00000001 total_memory : 1023 free_memory : 62 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32 platform_params : virt_start=0xfc000000 xen_changeset : Tue Apr 25 18:22:11 2006 +0100 9744:1ad06bd6832d cc_compiler : gcc version 4.0.0 20050519 (Red Hat 4.0.0-8) cc_compile_by : build cc_compile_domain : katan...