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 3.02_09763-0.8 xen-tools 3.02_09763-0.8 xen-tools-ioemu 3.02_09763-0.8 I understad allof these have tomach. If I do the compile of the tarball with make distro, does this al create all of the files? If this does not create all of the files, how do I find the other files? Done a goggle of the internet and found nothing about these tools, etc. Also, If I want to inatall a 32-bit operating system under a 64-bit athlon system, do I need to install the xen-libs-32bit? (descriptions for all of the packages are the same in yast, so that does not help much) Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote:> On 24 Oct 2006 at 21:28, Art Fore wrote: > > > 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 3.02_09763-0.8 > > xen-tools 3.02_09763-0.8 > > xen-tools-ioemu 3.02_09763-0.8 > > > > I understad allof these have tomach. If I do the compile of the tarball > > with make distro, does this al create all of the files? > > > > If this does not create all of the files, how do I find the other files? > > rpm -qi <package name> will show the source RPM. There you have the sources. > Update the sources, thenrebuild the RPMs. > > [...] > Ulrich >The more I look into this, the more confused I get.>From http://www.xensource.com/files/xen_install_windows.pdfThere is a paragraph: Type /usr/sbin/xm info | grep caps at the command prompt. You will see “hvm-3.0-x86_32” if Xen can detect the VT or AMD-V technology. If you do not see this, then your system does not have the appropriate processor technology, or it has been disabled in the BIOS. You must rectify this before proceeding. When I type the command, I get: linux-p204:~ # /usr/sbin/xm info | grep caps hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 I have 3 hvm listings instead of 1. Could someone kindly explain: Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? If it is normal, why 3 hvms? If it isn''t, what is happening? I created 2 full virtualization machines with Yast, but they are both stopped. The WinXP never completed installation,it hung the computer about 2/3 of the device installation phase, and the Suse 10 was going so slow that it was going to take 13 hours to install. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote:> On 24 Oct 2006 at 21:28, Art Fore wrote: > > > 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 3.02_09763-0.8 > > xen-tools 3.02_09763-0.8 > > xen-tools-ioemu 3.02_09763-0.8 > > > > I understad allof these have tomach. If I do the compile of the tarball > > with make distro, does this al create all of the files? > > > > If this does not create all of the files, how do I find the other files? > > rpm -qi <package name> will show the source RPM. There you have the sources. > Update the sources, thenrebuild the RPMs. > > [...] > Ulrich >The more I look into this, the more confused I get.>From http://www.xensource.com/files/xen_install_windows.pdfThere is a paragraph: Type /usr/sbin/xm info | grep caps at the command prompt. You will see “hvm-3.0-x86_32” if Xen can detect the VT or AMD-V technology. If you do not see this, then your system does not have the appropriate processor technology, or it has been disabled in the BIOS. You must rectify this before proceeding. When I type the command, I get: linux-p204:~ # /usr/sbin/xm info | grep caps hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 I have 3 hvm listings instead of 1. Could someone kindly explain: Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? If it is normal, why 3 hvms? If it isn''t, what is happening? I created 2 full virtualization machines with Yast, but they are both stopped. The WinXP never completed installation,it hung the computer about 2/3 of the device installation phase, and the Suse 10 was going so slow that it was going to take 13 hours to install. Art Just had a though after I sent the email. I deleted the Suse virtual machine that was stopped in Yast,the ran the /usr/sbin/xm info | grep caps again, but came up with same answer! Just adds to the confusion. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 24 October 2006 18:55 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > 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 3.02_09763-0.8 > > > xen-tools 3.02_09763-0.8 > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > I understad allof these have tomach. If I do the compile > of the tarball > > > with make distro, does this al create all of the files? > > > > > > If this does not create all of the files, how do I find > the other files? > > > > rpm -qi <package name> will show the source RPM. There you > have the sources. > > Update the sources, thenrebuild the RPMs. > > > > [...] > > Ulrich > > > > The more I look into this, the more confused I get. > > >From http://www.xensource.com/files/xen_install_windows.pdf > There is a paragraph: > Type /usr/sbin/xm info | grep caps at the command prompt. You will see > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > technology. If you do > not see this, then your system does not have the appropriate processor > technology, or it has been disabled in the BIOS. You must rectify this > before proceeding. > > When I type the command, I get: > linux-p204:~ # /usr/sbin/xm info | grep caps > hw_caps : > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 > > I have 3 hvm listings instead of 1. Could someone kindly explain: > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > If it is normal, why 3 hvms? > If it isn''t, what is happening?It''s normal. You can run: xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. hvm-3.0-x86_32 - fully virtualized 32-bit kernel. hvm-3.0-x86_64 - fully virtualized 64-bit kernel. And it''s actually only two hvms and one "xen" (but until I started splitting it up on separate lines, I didn''t see the difference either!). The above .pdf reference I presume was written by someone that didn''t do 64-bit builds of Xen at the time of writing. [Although essentially, what the above text refers to is THERE, right, it''s just not alone, which the text doesn''t say it should be (nor does it say that is shouldn''t be alone)].> > I created 2 full virtualization machines with Yast, but they are both > stopped. The WinXP never completed installation,it hung the computer > about 2/3 of the device installation phase, and the Suse 10 > was going so > slow that it was going to take 13 hours to install.What version (according to xm info) are you using? Can you post the full "xm info" output, please? -- Mats> > Art > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-24 at 20:05 +0200, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 24 October 2006 18:55 > > To: xen-users@lists.xensource.com > > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > > > 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 3.02_09763-0.8 > > > > xen-tools 3.02_09763-0.8 > > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > > > I understad allof these have tomach. If I do the compile > > of the tarball > > > > with make distro, does this al create all of the files? > > > > > > > > If this does not create all of the files, how do I find > > the other files? > > > > > > rpm -qi <package name> will show the source RPM. There you > > have the sources. > > > Update the sources, thenrebuild the RPMs. > > > > > > [...] > > > Ulrich > > > > > > > The more I look into this, the more confused I get. > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > There is a paragraph: > > Type /usr/sbin/xm info | grep caps at the command prompt. You will see > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > > technology. If you do > > not see this, then your system does not have the appropriate processor > > technology, or it has been disabled in the BIOS. You must rectify this > > before proceeding. > > > > When I type the command, I get: > > linux-p204:~ # /usr/sbin/xm info | grep caps > > hw_caps : > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 > > > > I have 3 hvm listings instead of 1. Could someone kindly explain: > > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > > If it is normal, why 3 hvms? > > If it isn''t, what is happening? > > It''s normal. > You can run: > xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. > hvm-3.0-x86_32 - fully virtualized 32-bit kernel. > hvm-3.0-x86_64 - fully virtualized 64-bit kernel. > > And it''s actually only two hvms and one "xen" (but until I started > splitting it up on separate lines, I didn''t see the difference either!). > > > The above .pdf reference I presume was written by someone that didn''t do > 64-bit builds of Xen at the time of writing. [Although essentially, what > the above text refers to is THERE, right, it''s just not alone, which the > text doesn''t say it should be (nor does it say that is shouldn''t be > alone)]. > > > > > > I created 2 full virtualization machines with Yast, but they are both > > stopped. The WinXP never completed installation,it hung the computer > > about 2/3 of the device installation phase, and the Suse 10 > > was going so > > slow that it was going to take 13 hours to install. > > What version (according to xm info) are you using? Can you post the full > "xm info" output, please? > > -- > Mats > > > > > Art > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > >Well that is a relief that it is normal. Thanks for the info. Here is the output of xm info # xm info host : linux-p204 release : 2.6.16.21-0.25-xen version : #1 SMP Tue Sep 19 07:26:15 UTC 2006 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2000 hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f total_memory : 2047 free_memory : 124 max_free_memory : 1811 max_para_memory : 1807 max_hvm_memory : 1794 xen_major : 3 xen_minor : 0 xen_extra : .2_09763-0.8 xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 platform_params : virt_start=0xffff800000000000 xen_changeset : 09763 cc_compiler : gcc version 4.1.0 (SUSE Linux) cc_compile_by : abuild cc_compile_domain : suse.de cc_compile_date : Fri Oct 6 16:00:18 UTC 2006 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 24 October 2006 19:33 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > On Tue, 2006-10-24 at 20:05 +0200, Petersson, Mats wrote: > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > Of Art Fore > > > Sent: 24 October 2006 18:55 > > > To: xen-users@lists.xensource.com > > > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > > > > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > > > > > 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 3.02_09763-0.8 > > > > > xen-tools 3.02_09763-0.8 > > > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > > > > > I understad allof these have tomach. If I do the compile > > > of the tarball > > > > > with make distro, does this al create all of the files? > > > > > > > > > > If this does not create all of the files, how do I find > > > the other files? > > > > > > > > rpm -qi <package name> will show the source RPM. There you > > > have the sources. > > > > Update the sources, thenrebuild the RPMs. > > > > > > > > [...] > > > > Ulrich > > > > > > > > > > The more I look into this, the more confused I get. > > > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > > There is a paragraph: > > > Type /usr/sbin/xm info | grep caps at the command prompt. > You will see > > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > > > technology. If you do > > > not see this, then your system does not have the > appropriate processor > > > technology, or it has been disabled in the BIOS. You must > rectify this > > > before proceeding. > > > > > > When I type the command, I get: > > > linux-p204:~ # /usr/sbin/xm info | grep caps > > > hw_caps : > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > hvm-3.0-x86_64 > > > > > > I have 3 hvm listings instead of 1. Could someone kindly explain: > > > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > > > If it is normal, why 3 hvms? > > > If it isn''t, what is happening? > > > > It''s normal. > > You can run: > > xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. > > hvm-3.0-x86_32 - fully virtualized 32-bit kernel. > > hvm-3.0-x86_64 - fully virtualized 64-bit kernel. > > > > And it''s actually only two hvms and one "xen" (but until I started > > splitting it up on separate lines, I didn''t see the > difference either!). > > > > > > The above .pdf reference I presume was written by someone > that didn''t do > > 64-bit builds of Xen at the time of writing. [Although > essentially, what > > the above text refers to is THERE, right, it''s just not > alone, which the > > text doesn''t say it should be (nor does it say that is shouldn''t be > > alone)]. > > > > > > > > > > I created 2 full virtualization machines with Yast, but > they are both > > > stopped. The WinXP never completed installation,it hung > the computer > > > about 2/3 of the device installation phase, and the Suse 10 > > > was going so > > > slow that it was going to take 13 hours to install. > > > > What version (according to xm info) are you using? Can you > post the full > > "xm info" output, please? > > > > -- > > Mats > > > > > > > > Art > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > Well that is a relief that it is normal. Thanks for the info. > > Here is the output of xm info > > # xm info > host : linux-p204 > release : 2.6.16.21-0.25-xen > version : #1 SMP Tue Sep 19 07:26:15 UTC 2006 > machine : x86_64 > nr_cpus : 2 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 2000 > hw_caps : > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > total_memory : 2047 > free_memory : 124 > max_free_memory : 1811 > max_para_memory : 1807 > max_hvm_memory : 1794 > xen_major : 3 > xen_minor : 0 > xen_extra : .2_09763-0.8 > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 > platform_params : virt_start=0xffff800000000000 > xen_changeset : 09763This tells me that it''s roughly 2000 changesets old... So there''s been "a few" changes that may influence your success in running hvm (or other) domains on your system. You may want to download the latest sources or precompiled binary from xensource (if the precompiled binary is what you''re using now, then that''s obviously not much use - latest sources would be better). -- Mats> cc_compiler : gcc version 4.1.0 (SUSE Linux) > cc_compile_by : abuild > cc_compile_domain : suse.de > cc_compile_date : Fri Oct 6 16:00:18 UTC 2006 > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-24 at 20:39 +0200, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 24 October 2006 19:33 > > To: xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > > > On Tue, 2006-10-24 at 20:05 +0200, Petersson, Mats wrote: > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > Of Art Fore > > > > Sent: 24 October 2006 18:55 > > > > To: xen-users@lists.xensource.com > > > > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > > > > > > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > > > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > > > > > > > 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 3.02_09763-0.8 > > > > > > xen-tools 3.02_09763-0.8 > > > > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > > > > > > > I understad allof these have tomach. If I do the compile > > > > of the tarball > > > > > > with make distro, does this al create all of the files? > > > > > > > > > > > > If this does not create all of the files, how do I find > > > > the other files? > > > > > > > > > > rpm -qi <package name> will show the source RPM. There you > > > > have the sources. > > > > > Update the sources, thenrebuild the RPMs. > > > > > > > > > > [...] > > > > > Ulrich > > > > > > > > > > > > > The more I look into this, the more confused I get. > > > > > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > > > There is a paragraph: > > > > Type /usr/sbin/xm info | grep caps at the command prompt. > > You will see > > > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > > > > technology. If you do > > > > not see this, then your system does not have the > > appropriate processor > > > > technology, or it has been disabled in the BIOS. You must > > rectify this > > > > before proceeding. > > > > > > > > When I type the command, I get: > > > > linux-p204:~ # /usr/sbin/xm info | grep caps > > > > hw_caps : > > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > > hvm-3.0-x86_64 > > > > > > > > I have 3 hvm listings instead of 1. Could someone kindly explain: > > > > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > > > > If it is normal, why 3 hvms? > > > > If it isn''t, what is happening? > > > > > > It''s normal. > > > You can run: > > > xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. > > > hvm-3.0-x86_32 - fully virtualized 32-bit kernel. > > > hvm-3.0-x86_64 - fully virtualized 64-bit kernel. > > > > > > And it''s actually only two hvms and one "xen" (but until I started > > > splitting it up on separate lines, I didn''t see the > > difference either!). > > > > > > > > > The above .pdf reference I presume was written by someone > > that didn''t do > > > 64-bit builds of Xen at the time of writing. [Although > > essentially, what > > > the above text refers to is THERE, right, it''s just not > > alone, which the > > > text doesn''t say it should be (nor does it say that is shouldn''t be > > > alone)]. > > > > > > > > > > > > > > I created 2 full virtualization machines with Yast, but > > they are both > > > > stopped. The WinXP never completed installation,it hung > > the computer > > > > about 2/3 of the device installation phase, and the Suse 10 > > > > was going so > > > > slow that it was going to take 13 hours to install. > > > > > > What version (according to xm info) are you using? Can you > > post the full > > > "xm info" output, please? > > > > > > -- > > > Mats > > > > > > > > > > > Art > > > > > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > > > > > > Well that is a relief that it is normal. Thanks for the info. > > > > Here is the output of xm info > > > > # xm info > > host : linux-p204 > > release : 2.6.16.21-0.25-xen > > version : #1 SMP Tue Sep 19 07:26:15 UTC 2006 > > machine : x86_64 > > nr_cpus : 2 > > nr_nodes : 1 > > sockets_per_node : 1 > > cores_per_socket : 2 > > threads_per_core : 1 > > cpu_mhz : 2000 > > hw_caps : > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > total_memory : 2047 > > free_memory : 124 > > max_free_memory : 1811 > > max_para_memory : 1807 > > max_hvm_memory : 1794 > > xen_major : 3 > > xen_minor : 0 > > xen_extra : .2_09763-0.8 > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : 09763 > > This tells me that it''s roughly 2000 changesets old... So there''s been > "a few" changes that may influence your success in running hvm (or > other) domains on your system. > > You may want to download the latest sources or precompiled binary from > xensource (if the precompiled binary is what you''re using now, then > that''s obviously not much use - latest sources would be better). > > -- > Mats > > cc_compiler : gcc version 4.1.0 (SUSE Linux) > > cc_compile_by : abuild > > cc_compile_domain : suse.de > > cc_compile_date : Fri Oct 6 16:00:18 UTC 2006 > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > >Thanks for the info. The precompiled binaries are the stock Suse 10.1 binaries which are 3.0.2. I tried the latest version for Suse 9.3 that are availalbe, but guess I didn''t do it right or they don''t work for this kernel as it caused a kernel crash and I removed it. Am going to try the source tab but that is where the confusion came in as far as the other packages that have to go along with it. When yoou make distro and then install, exactly what packages are installed or where do you find out? Are the xen-tools and xen-tools-ioemu files included with the source tar and if not, where do you get them that match or do the have to match? Googling has not found anything for 3.0.3 for these packages. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > Sent: 24 October 2006 20:21 > To: xen-users@lists.xensource.com > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > On Tue, 2006-10-24 at 20:39 +0200, Petersson, Mats wrote: > > > > > -----Original Message----- > > > From: xen-users-bounces@lists.xensource.com > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > Of Art Fore > > > Sent: 24 October 2006 19:33 > > > To: xen-users@lists.xensource.com > > > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > > > > > On Tue, 2006-10-24 at 20:05 +0200, Petersson, Mats wrote: > > > > > > > > > -----Original Message----- > > > > > From: xen-users-bounces@lists.xensource.com > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > Of Art Fore > > > > > Sent: 24 October 2006 18:55 > > > > > To: xen-users@lists.xensource.com > > > > > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > > > > > > > > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > > > > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > > > > > > > > > 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 3.02_09763-0.8 > > > > > > > xen-tools 3.02_09763-0.8 > > > > > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > > > > > > > > > I understad allof these have tomach. If I do the compile > > > > > of the tarball > > > > > > > with make distro, does this al create all of the files? > > > > > > > > > > > > > > If this does not create all of the files, how do I find > > > > > the other files? > > > > > > > > > > > > rpm -qi <package name> will show the source RPM. There you > > > > > have the sources. > > > > > > Update the sources, thenrebuild the RPMs. > > > > > > > > > > > > [...] > > > > > > Ulrich > > > > > > > > > > > > > > > > The more I look into this, the more confused I get. > > > > > > > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > > > > There is a paragraph: > > > > > Type /usr/sbin/xm info | grep caps at the command prompt. > > > You will see > > > > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > > > > > technology. If you do > > > > > not see this, then your system does not have the > > > appropriate processor > > > > > technology, or it has been disabled in the BIOS. You must > > > rectify this > > > > > before proceeding. > > > > > > > > > > When I type the command, I get: > > > > > linux-p204:~ # /usr/sbin/xm info | grep caps > > > > > hw_caps : > > > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > > > hvm-3.0-x86_64 > > > > > > > > > > I have 3 hvm listings instead of 1. Could someone > kindly explain: > > > > > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > > > > > If it is normal, why 3 hvms? > > > > > If it isn''t, what is happening? > > > > > > > > It''s normal. > > > > You can run: > > > > xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. > > > > hvm-3.0-x86_32 - fully virtualized 32-bit kernel. > > > > hvm-3.0-x86_64 - fully virtualized 64-bit kernel. > > > > > > > > And it''s actually only two hvms and one "xen" (but > until I started > > > > splitting it up on separate lines, I didn''t see the > > > difference either!). > > > > > > > > > > > > The above .pdf reference I presume was written by someone > > > that didn''t do > > > > 64-bit builds of Xen at the time of writing. [Although > > > essentially, what > > > > the above text refers to is THERE, right, it''s just not > > > alone, which the > > > > text doesn''t say it should be (nor does it say that is > shouldn''t be > > > > alone)]. > > > > > > > > > > > > > > > > > > I created 2 full virtualization machines with Yast, but > > > they are both > > > > > stopped. The WinXP never completed installation,it hung > > > the computer > > > > > about 2/3 of the device installation phase, and the Suse 10 > > > > > was going so > > > > > slow that it was going to take 13 hours to install. > > > > > > > > What version (according to xm info) are you using? Can you > > > post the full > > > > "xm info" output, please? > > > > > > > > -- > > > > Mats > > > > > > > > > > > > > > Art > > > > > > > > > > > > > > > _______________________________________________ > > > > > Xen-users mailing list > > > > > Xen-users@lists.xensource.com > > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Well that is a relief that it is normal. Thanks for the info. > > > > > > Here is the output of xm info > > > > > > # xm info > > > host : linux-p204 > > > release : 2.6.16.21-0.25-xen > > > version : #1 SMP Tue Sep 19 07:26:15 UTC 2006 > > > machine : x86_64 > > > nr_cpus : 2 > > > nr_nodes : 1 > > > sockets_per_node : 1 > > > cores_per_socket : 2 > > > threads_per_core : 1 > > > cpu_mhz : 2000 > > > hw_caps : > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > total_memory : 2047 > > > free_memory : 124 > > > max_free_memory : 1811 > > > max_para_memory : 1807 > > > max_hvm_memory : 1794 > > > xen_major : 3 > > > xen_minor : 0 > > > xen_extra : .2_09763-0.8 > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > hvm-3.0-x86_64 > > > platform_params : virt_start=0xffff800000000000 > > > xen_changeset : 09763 > > > > This tells me that it''s roughly 2000 changesets old... So > there''s been > > "a few" changes that may influence your success in running hvm (or > > other) domains on your system. > > > > You may want to download the latest sources or precompiled > binary from > > xensource (if the precompiled binary is what you''re using now, then > > that''s obviously not much use - latest sources would be better). > > > > -- > > Mats > > > cc_compiler : gcc version 4.1.0 (SUSE Linux) > > > cc_compile_by : abuild > > > cc_compile_domain : suse.de > > > cc_compile_date : Fri Oct 6 16:00:18 UTC 2006 > > > > > > > > > > > > _______________________________________________ > > > Xen-users mailing list > > > Xen-users@lists.xensource.com > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > Thanks for the info. The precompiled binaries are the stock Suse 10.1 > binaries which are 3.0.2. I tried the latest version for Suse 9.3 that > are availalbe, but guess I didn''t do it right or they don''t work for > this kernel as it caused a kernel crash and I removed it. Am going to > try the source tab but that is where the confusion came in as > far as the > other packages that have to go along with it. > > When yoou make distro and then install, exactly what packages are > installed or where do you find out? Are the xen-tools and > xen-tools-ioemu files included with the source tar and if > not, where do > you get them that match or do the have to match? Googling has > not found > anything for 3.0.3 for these packages.Yes, as long as you have ALL the necessary tools and packages to compile all components, the source-tar-ball contains all the necessary code to build xen itself, tools, ioemu bits and whatever else you may need. There is a hitch in building the "firmware" which is part of tools to run hvm - you need a 16-bit compiler which you have to go somewhere to download, it''s not normally distributed with the distributions... If you do "cd <xen-root>/tools/firmware" and type "make", it''ll suggest a location to download from - you probably also need to build this, and when I last tried, it didn''t build correctly in 64-bit mode, so try building with "linux32" or some such set... -- Mats> > Art > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, 2006-10-24 at 21:25 +0200, Petersson, Mats wrote:> > > -----Original Message----- > > From: xen-users-bounces@lists.xensource.com > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Art Fore > > Sent: 24 October 2006 20:21 > > To: xen-users@lists.xensource.com > > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > > > On Tue, 2006-10-24 at 20:39 +0200, Petersson, Mats wrote: > > > > > > > -----Original Message----- > > > > From: xen-users-bounces@lists.xensource.com > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > Of Art Fore > > > > Sent: 24 October 2006 19:33 > > > > To: xen-users@lists.xensource.com > > > > Subject: RE: [Xen-users] Xen 3.0.3 confusion > > > > > > > > On Tue, 2006-10-24 at 20:05 +0200, Petersson, Mats wrote: > > > > > > > > > > > -----Original Message----- > > > > > > From: xen-users-bounces@lists.xensource.com > > > > > > [mailto:xen-users-bounces@lists.xensource.com] On Behalf > > > > Of Art Fore > > > > > > Sent: 24 October 2006 18:55 > > > > > > To: xen-users@lists.xensource.com > > > > > > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > > > > > > > > > > > On Tue, 2006-10-24 at 17:00 +0200, Ulrich Windl wrote: > > > > > > > On 24 Oct 2006 at 21:28, Art Fore wrote: > > > > > > > > > > > > > > > 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 3.02_09763-0.8 > > > > > > > > xen-tools 3.02_09763-0.8 > > > > > > > > xen-tools-ioemu 3.02_09763-0.8 > > > > > > > > > > > > > > > > I understad allof these have tomach. If I do the compile > > > > > > of the tarball > > > > > > > > with make distro, does this al create all of the files? > > > > > > > > > > > > > > > > If this does not create all of the files, how do I find > > > > > > the other files? > > > > > > > > > > > > > > rpm -qi <package name> will show the source RPM. There you > > > > > > have the sources. > > > > > > > Update the sources, thenrebuild the RPMs. > > > > > > > > > > > > > > [...] > > > > > > > Ulrich > > > > > > > > > > > > > > > > > > > The more I look into this, the more confused I get. > > > > > > > > > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > > > > > There is a paragraph: > > > > > > Type /usr/sbin/xm info | grep caps at the command prompt. > > > > You will see > > > > > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > > > > > > technology. If you do > > > > > > not see this, then your system does not have the > > > > appropriate processor > > > > > > technology, or it has been disabled in the BIOS. You must > > > > rectify this > > > > > > before proceeding. > > > > > > > > > > > > When I type the command, I get: > > > > > > linux-p204:~ # /usr/sbin/xm info | grep caps > > > > > > hw_caps : > > > > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > > > > hvm-3.0-x86_64 > > > > > > > > > > > > I have 3 hvm listings instead of 1. Could someone > > kindly explain: > > > > > > Is this normal of Athlon 64 X2 (Running Suse 10.1 Xen kernel)? > > > > > > If it is normal, why 3 hvms? > > > > > > If it isn''t, what is happening? > > > > > > > > > > It''s normal. > > > > > You can run: > > > > > xen-3.0-x86_64 - Paravirtual 3.0-compatible 64-bit kernel. > > > > > hvm-3.0-x86_32 - fully virtualized 32-bit kernel. > > > > > hvm-3.0-x86_64 - fully virtualized 64-bit kernel. > > > > > > > > > > And it''s actually only two hvms and one "xen" (but > > until I started > > > > > splitting it up on separate lines, I didn''t see the > > > > difference either!). > > > > > > > > > > > > > > > The above .pdf reference I presume was written by someone > > > > that didn''t do > > > > > 64-bit builds of Xen at the time of writing. [Although > > > > essentially, what > > > > > the above text refers to is THERE, right, it''s just not > > > > alone, which the > > > > > text doesn''t say it should be (nor does it say that is > > shouldn''t be > > > > > alone)]. > > > > > > > > > > > > > > > > > > > > > > I created 2 full virtualization machines with Yast, but > > > > they are both > > > > > > stopped. The WinXP never completed installation,it hung > > > > the computer > > > > > > about 2/3 of the device installation phase, and the Suse 10 > > > > > > was going so > > > > > > slow that it was going to take 13 hours to install. > > > > > > > > > > What version (according to xm info) are you using? Can you > > > > post the full > > > > > "xm info" output, please? > > > > > > > > > > -- > > > > > Mats > > > > > > > > > > > > > > > > > Art > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Xen-users mailing list > > > > > > Xen-users@lists.xensource.com > > > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Well that is a relief that it is normal. Thanks for the info. > > > > > > > > Here is the output of xm info > > > > > > > > # xm info > > > > host : linux-p204 > > > > release : 2.6.16.21-0.25-xen > > > > version : #1 SMP Tue Sep 19 07:26:15 UTC 2006 > > > > machine : x86_64 > > > > nr_cpus : 2 > > > > nr_nodes : 1 > > > > sockets_per_node : 1 > > > > cores_per_socket : 2 > > > > threads_per_core : 1 > > > > cpu_mhz : 2000 > > > > hw_caps : > > > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > > > total_memory : 2047 > > > > free_memory : 124 > > > > max_free_memory : 1811 > > > > max_para_memory : 1807 > > > > max_hvm_memory : 1794 > > > > xen_major : 3 > > > > xen_minor : 0 > > > > xen_extra : .2_09763-0.8 > > > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > > hvm-3.0-x86_64 > > > > platform_params : virt_start=0xffff800000000000 > > > > xen_changeset : 09763 > > > > > > This tells me that it''s roughly 2000 changesets old... So > > there''s been > > > "a few" changes that may influence your success in running hvm (or > > > other) domains on your system. > > > > > > You may want to download the latest sources or precompiled > > binary from > > > xensource (if the precompiled binary is what you''re using now, then > > > that''s obviously not much use - latest sources would be better). > > > > > > -- > > > Mats > > > > cc_compiler : gcc version 4.1.0 (SUSE Linux) > > > > cc_compile_by : abuild > > > > cc_compile_domain : suse.de > > > > cc_compile_date : Fri Oct 6 16:00:18 UTC 2006 > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-users mailing list > > > > Xen-users@lists.xensource.com > > > > http://lists.xensource.com/xen-users > > > > > > > > > > > > > > > > > > > > > > Thanks for the info. The precompiled binaries are the stock Suse 10.1 > > binaries which are 3.0.2. I tried the latest version for Suse 9.3 that > > are availalbe, but guess I didn''t do it right or they don''t work for > > this kernel as it caused a kernel crash and I removed it. Am going to > > try the source tab but that is where the confusion came in as > > far as the > > other packages that have to go along with it. > > > > When yoou make distro and then install, exactly what packages are > > installed or where do you find out? Are the xen-tools and > > xen-tools-ioemu files included with the source tar and if > > not, where do > > you get them that match or do the have to match? Googling has > > not found > > anything for 3.0.3 for these packages. > > Yes, as long as you have ALL the necessary tools and packages to compile > all components, the source-tar-ball contains all the necessary code to > build xen itself, tools, ioemu bits and whatever else you may need. > > There is a hitch in building the "firmware" which is part of tools to > run hvm - you need a 16-bit compiler which you have to go somewhere to > download, it''s not normally distributed with the distributions... If you > do "cd <xen-root>/tools/firmware" and type "make", it''ll suggest a > location to download from - you probably also need to build this, and > when I last tried, it didn''t build correctly in 64-bit mode, so try > building with "linux32" or some such set... > > -- > Mats > > > > Art > > > > > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersI think I will check on the Suse mail list if anyone has already done this for 10.1. It sounds kindof complex building it and the way things have been going lately, everything that could go wrong probably will. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 25 Oct 2006 at 1:55, Art Fore wrote: [...]> The more I look into this, the more confused I get. > > >From http://www.xensource.com/files/xen_install_windows.pdf > There is a paragraph: > Type /usr/sbin/xm info | grep caps at the command prompt. You will see > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V technology. If you do > not see this, then your system does not have the appropriate processor > technology, or it has been disabled in the BIOS. You must rectify this > before proceeding. > > When I type the command, I get: > linux-p204:~ # /usr/sbin/xm info | grep caps > hw_caps : > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64For a 2.6GHz Dual-Core Opteron I see (SLES10 x86_64, xen-3.0.2_09763-0.8): hw_caps : 178bfbff:e3d3fbff:00000000:00000010:00000001:00000000:00000003 xen_caps : xen-3.0-x86_64 So either there''s no HVM support, or it wasn''t compiled in... 8-( [...] Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, 2006-10-25 at 08:32 +0200, Ulrich Windl wrote:> On 25 Oct 2006 at 1:55, Art Fore wrote: > > [...] > > The more I look into this, the more confused I get. > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > There is a paragraph: > > Type /usr/sbin/xm info | grep caps at the command prompt. You will see > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V technology. If you do > > not see this, then your system does not have the appropriate processor > > technology, or it has been disabled in the BIOS. You must rectify this > > before proceeding. > > > > When I type the command, I get: > > linux-p204:~ # /usr/sbin/xm info | grep caps > > hw_caps : > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_64 > > For a 2.6GHz Dual-Core Opteron I see (SLES10 x86_64, xen-3.0.2_09763-0.8): > > hw_caps : > 178bfbff:e3d3fbff:00000000:00000010:00000001:00000000:00000003 > xen_caps : xen-3.0-x86_64 > > So either there''s no HVM support, or it wasn''t compiled in... 8-( > > [...] > > Regards, > Ulrich > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersInteresting. One of the replays says it is normal. I ran the XenLiveCD and also got the same as I got before. When I executed one of the scripts to add a virtual machine, it then changed like the xen_caps line you have. Art _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Ulrich Windl > Sent: 25 October 2006 07:32 > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] Xen 3.0.3 confusion > > On 25 Oct 2006 at 1:55, Art Fore wrote: > > [...] > > The more I look into this, the more confused I get. > > > > >From http://www.xensource.com/files/xen_install_windows.pdf > > There is a paragraph: > > Type /usr/sbin/xm info | grep caps at the command prompt. > You will see > > "hvm-3.0-x86_32" if Xen can detect the VT or AMD-V > technology. If you do > > not see this, then your system does not have the > appropriate processor > > technology, or it has been disabled in the BIOS. You must > rectify this > > before proceeding. > > > > When I type the command, I get: > > linux-p204:~ # /usr/sbin/xm info | grep caps > > hw_caps : > > 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 > hvm-3.0-x86_64 > > For a 2.6GHz Dual-Core Opteron I see (SLES10 x86_64, > xen-3.0.2_09763-0.8): > > hw_caps : > 178bfbff:e3d3fbff:00000000:00000010:00000001:00000000:00000003 > xen_caps : xen-3.0-x86_64 > > So either there''s no HVM support, or it wasn''t compiled in... 8-(What model Opteron processor is that? The three-number models or four-number models? -- Mats> > [...] > > Regards, > Ulrich > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users