Don't forget to post the results on the kvm list On Mon, Nov 6, 2017 at 2:21 PM, Clinton Shane Wright <clintonabco@xxxxxxxxx> wrote: > I believe you are right sir. > > I think I have found the solution. Busy testing now. Linode has an > option to switch to full virtualization. Going to see if vmx comes > with that enabled. > > Kind regards, > > On Mon, Nov 6, 2017 at 9:17 PM, Mauricio Tavares <raubvogel@xxxxxxxxx> wrote: >> On Mon, Nov 6, 2017 at 2:13 PM, Clinton Shane Wright >> <clintonabco@xxxxxxxxx> wrote: >>> Hi Mauricio, >>> >>> What I can tell, and sorry for spelling your name wrong, is that there >>> is some other kind of virtualization. I ran lscpu and got the >>> following: >>> >>> Architecture: x86_64 >>> CPU op-mode(s): 32-bit, 64-bit >>> Byte Order: Little Endian >>> CPU(s): 4 >>> On-line CPU(s) list: 0-3 >>> Thread(s) per core: 1 >>> Core(s) per socket: 1 >>> Socket(s): 4 >>> NUMA node(s): 1 >>> Vendor ID: GenuineIntel >>> CPU family: 6 >>> Model: 63 >>> Model name: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz >>> Stepping: 2 >>> CPU MHz: 2499.988 >>> BogoMIPS: 4999.97 >>> Hypervisor vendor: KVM >>> Virtualization type: full >>> L1d cache: 32K >>> L1i cache: 32K >>> L2 cache: 4096K >>> NUMA node0 CPU(s): 0-3 >>> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep >>> mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx >>> pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni >>> pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt >>> tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm >>> fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat >>> >>> Note the Virtualization: full. >>> >>> I have sent an email to linode support about the VT virtualization support. >>> >>> Many thanks and kind regards, >> >> Correct me if I am wrong but you want to run vbox inside the >> linode thingie. So, vbox must detect the vmx or svm cpu options in the >> CPU it knows of to provide the 64bit stuff. For that to happen they >> (linode) have to pass them to the guest, otherwise vbox will think the >> cpu can only support 32bit vms. >> >>> >>> On Mon, Nov 6, 2017 at 9:04 PM, Clinton Shane Wright >>> <clintonabco@xxxxxxxxx> wrote: >>>> Hi Maruicio, >>>> >>>> Many thanks for your reply. >>>> >>>> The egrep command produces no result, so I guess there is no >>>> virtualization support then on Linode KVM guest. >>>> >>>> Going to contact their support. >>>> >>>> Anything I can do? I guess not. >>>> >>>> Many thanks again. >>>> >>>> On Mon, Nov 6, 2017 at 8:59 PM, Mauricio Tavares <raubvogel@xxxxxxxxx> wrote: >>>>> On Mon, Nov 6, 2017 at 1:44 PM, Clinton Shane Wright >>>>> <clintonabco@xxxxxxxxx> wrote: >>>>>> Hi, >>>>>> >>>>>> I am hoping someone can help me. I am trying to run a windows7 64 bit >>>>>> guest os using Virtualbox running inside of Linux KVM guest. My server >>>>>> is hosted by linode, so its a linode KVM machine running Debian 9 >>>>>> (also tried CentOS 7). >>>>>> >>>>>> I have managed to install VirtualBox and setup my VM but when I >>>>>> startup Windows 7 I get the following message: >>>>>> >>>>>> Attempting to load 64-bit application, however this CPU is not >>>>>> compatible with 64-bit mode. >>>>>> >>>>>> Please can you advise if what I am trying to do is possible, can a KVM >>>>>> guest run a Virtualbox 64bit guest inside of it? The Linode team seem >>>>>> to think you can. >>>>>> >>>>>> Any help is appreciated. >>>>>> >>>>>> Kind regards, >>>>>> >>>>> Did you check your cpuinfo to see if they are passing the >>>>> virtualization stuff to your guest? You know, something like >>>>> >>>>> egrep '(vmx|svm)' --color=always /proc/cpuinfo >>>>> >>>>> >>>>>> -- >>>>>> Clinton Wright >>>>>> clintonabco@xxxxxxxxx >>>> >>>> >>>> >>>> -- >>>> Clinton Wright >>>> >>>> +27 76 567 6539 >>>> clintonabco@xxxxxxxxx >>> >>> >>> >>> -- >>> Clinton Wright >>> >>> +27 76 567 6539 >>> clintonabco@xxxxxxxxx > > > > -- > Clinton Wright > > +27 76 567 6539 > clintonabco@xxxxxxxxx
