On Tuesday 01 June 2010 01:45:46 Jonathan Tripathy wrote:
> this email in error.
>
> On 01/06/10 00:43, Jonathan Tripathy wrote:
> > On 31/05/10 21:22, Jonathan Tripathy wrote:
> >> On 31/05/10 21:23, Bart Coninckx wrote:
> >>> On Monday 31 May 2010 21:59:24 Jonathan Tripathy wrote:
> >>>> Jonathan Tripathy
> >>>> I.T. Solutions Manager
> >>>> ABPNI Computer Solutions Ltd.
> >>>> Registered Address:
> >>>> Emerson House, Belfast, BT8 8DN
> >>>> Tel: +44 (0)800 11 234 28
> >>>> Web: www.abpni.com
> >>>> Registered in N. Ireland No. 602753
> >>>>
> >>>> This email and any attachments to it may be confidential
> >>>> and are intended solely for the use of the individual to
> >>>> whom it is addressed. Any views or opinions expressed are
> >>>> solely those of the author and do not necessarily represent
> >>>> those of ABPNI Computer Solutions Ltd. If you are not the
> >>>> intended recipient of this email, you must neither take any
> >>>> action based upon its contents, nor copy or show it to anyone.
> >>>> Please contact the sender if you believe you have received
> >>>> this email in error.
> >>>>
> >>>> On 31/05/10 20:45, Bart Coninckx wrote:
> >>>>> On Monday 31 May 2010 21:42:20 Jonathan Tripathy wrote:
> >>>>>> On 31/05/10 20:42, Bart Coninckx wrote:
> >>>>>>> On Monday 31 May 2010 20:24:15 Jonathan Tripathy wrote:
> >>>>>>>> On 31/05/10 19:11, Rudi Ahlers wrote:
> >>>>>>>>> On Mon, May 31, 2010 at 8:00 PM, Jonathan
> >>>>>>>>> Tripathy<jonnyt@xxxxxxxxxxx
> >>>>>>>>> <mailto:jonnyt@xxxxxxxxxxx>> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi Everyone,
> >>>>>>>>>
> >>>>>>>>> I upgraded my CentOS 5.5 to Xen 3.4.2 using this guide:
> >>>>>>>>>
> >>>>>>>>> http://www.syntaxtechnology.com/2010/01/upgrade-xen-3-0-on-centos
> >>>>>>>>>-5-4
> >>>>>>>>>
> >>>>>>>>> -x 86 _64-to-xen-3-4-2/
> >>>>>>>>>
> >>>>>>>>> Now, using the new kernel that it gave me, the system
> >>>>>>>>> doesn't
> >>>>>>>>> seem to be able to detect vt-x..
> >>>>>>>>>
> >>>>>>>>> In virt-manager, Local Install Media and Network Boot are
> >>>>>>>>> greyed out..
> >>>>>>>>>
> >>>>>>>>> Any ideas?
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> Xen-users mailing list
> >>>>>>>>>
> >>>>>>>>> Xen-users@xxxxxxxxxxxxxxxxxxx<mailto:Xen-users@xxxxxxxxxxxxxxxxxx
> >>>>>>>>>m>
> >>>>>>>>>
> >>>>>>>>> http://lists.xensource.com/xen-users
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Doe your CPU acrtually support vt-x?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Website: http://www.SoftDux.com
> >>>>>>>>> Technical Blog: http://Blog.SoftDux.com
> >>>>>>>>> Office: 087 805 9573
> >>>>>>>>> Cell: 082 554 7532
> >>>>>>>>
> >>>>>>>> Yes it does. It worked fine with the orignal version of Xen
> >>>>>>>> that came
> >>>>>>>> with CentOS 5.5. It's a brand new server opened today from Dell
> >>>>>>>> which
> >>>>>>>> support Vt-x and Vt-d. Virtualisation technology is enabled in the
> >>>>>>>> BIOS
> >>>>>>>
> >>>>>>> You have the vmx flag in /proc/cpuinfo?
> >>>>>>> I suppose you had the VT extension enabled before the migration but
> >>>>>>> suppose you fiddled with it, power down your host (like shutdown
> >>>>>>> and
> >>>>>>> pull the plug) and power it up again. I experienced this being
> >>>>>>> necessary once because simple rebooting after getting out of the
> >>>>>>> BIOS
> >>>>>>> did NOT enable VT for real.
> >>>>>>>
> >>>>>>> B.
> >>>>>>
> >>>>>> Nope, I don't have that flag in cpuinfo, but I can't understand
> >>>>>> why....
> >>>>>> Is it possible that the kernel upgrade can disable this somehow??
> >>>>>>
> >>>>>> It's really confusing me
> >>>>>
> >>>>> I personally think not. Do the power recycle thing and check
> >>>>> again. If
> >>>>> you're sure it's on in the BIOS. Ow yes, which reminds me, I once
> >>>>> had a
> >>>>> BIOS where it needed to be enabled on two different spots - I
> >>>>> think it
> >>>>> was a HP machine.
> >>>>
> >>>> Power cycling made no different. I had the plug out for about 2 or 3
> >>>> minutes.
> >>>>
> >>>> This is really starting to worry me why the vmx flag isn't showing...
> >>>>
> >>>> I never checked for the vmx flag in the vanilla install, but since
> >>>> I was
> >>>> able to create an HVM guest, I image it would have been there?
> >>>
> >>> I can't imagine this is a result of the kernel being used. Whatever
> >>> is in
> >>> /proc/cpuinfo is what Linux reads out of the BIOS. Something is
> >>> wrong there.
> >>
> >> Hmm I just threw in a Ubuntu live CD there and vmx is showing....
> >> Something must be dud in that Xen 3.4.2 source that i downloaded...
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >
> > Ok this is starting to bug me...
> >
> > I installed Ubuntu 10.04 onto my server. I then spent a couple of
> > hours compiling and installing Xen 4.0. Now yet again, vmx has
> > disappeared from /proc/cpuinfo!!!!
> >
> > Xend isn't working correctly, but that's another issue, so I can't
> > really test any HVM guests.
> >
> > Buggy BIOS??
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
>
> Actually, maybe this is correct with newer version of Xen:
> http://www.linux-kvm.org/page/FAQ#How_can_I_tell_if_I_have_Intel_VT_or_AMD-
> V.3F
>
Ha, didn't know that: "The Xen hypervisor suppresses these flags in order to
prevent hijacking" - not even sure what this hijacking is - being taken over
by another hypervisor? Anyway, at least you know now the flags are active as
long as you check with a regular kernel.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home