on 04/09/2010 09:15 AM Dennis Gilmore wrote:
> what do you get for "cat /proc/cpuinfo |grep svm"
nothing
> what model cpus do you have?
$ cat /proc/cpuinfo | grep model
model : 35
model name : Dual Core AMD Opteron(tm) Processor 165
model : 35
model name : Dual Co
On Friday 09 April 2010 11:22:07 am Greg Woods wrote:
> On Fri, 2010-04-09 at 11:14 -0500, Dennis Gilmore wrote:
> > its a amd specific flag that signifies hardware virtualisation. intels
> > is vmx so you would run "cat /proc/cpuinfo |grep vmx" if you get a
> > result you have hardware virtulaisa
On Fri, 2010-04-09 at 11:14 -0500, Dennis Gilmore wrote:
>
> its a amd specific flag that signifies hardware virtualisation. intels is
> vmx so
> you would run "cat /proc/cpuinfo |grep vmx" if you get a result you have
> hardware virtulaisation in your cpu. it could still be disabled in the
On Friday 09 April 2010 09:22:44 am Greg Woods wrote:
> On Fri, 2010-04-09 at 08:15 -0500, Dennis Gilmore wrote:
> > what do you get for "cat /proc/cpuinfo |grep svm" what model cpus do you
> > have?
>
> No output at all. Dual core Pentium 4:
>
> model name : Intel(R) Pentium(R) Dual CPU
On Fri, 2010-04-09 at 08:15 -0500, Dennis Gilmore wrote:
> what do you get for "cat /proc/cpuinfo |grep svm" what model cpus do you
> have?
No output at all. Dual core Pentium 4:
model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
> it seems vmware and virtual box regularly
>
evel-2.6.32.10-90.fc12.x86_64
> >> kernel-devel-2.6.32.9-70.fc12.x86_64
> >>
> >> it says
> >>
> >> sudo /etc/init.d/vboxdrv setup
> >> Stopping VirtualBox kernel module [ OK ]
> >> Recompiling VirtualBox k
s
>>
>> sudo /etc/init.d/vboxdrv setup
>> Stopping VirtualBox kernel module [ OK ]
>> Recompiling VirtualBox kernel module [FAILED]
>> (Look at /var/log/vbox-install.log to find out what went wrong)
>>
>>
>> vbox-in
on 04/08/2010 03:36 PM Kwan Lowe wrote:
> This thread has a fix:
> http://www.mail-archive.com/vbox-us...@virtualbox.org/msg07263.html
>
> In short, you're adding a one line change to a file (including sched.h).
thanks, it worked.
--
regards,
Oleksandr Korneta
I'm running F12 x86_64, should th
Greg Woods wrote:
>On Thu, 2010-04-08 at 15:34 -0500, Dennis Gilmore wrote:
>> Im curious why you use virtualbox and not kvm/libvirt/virt-manager that are
>> included by default in fedora? Im just trying to work out what is lacking
>> in
>> the default offerings that you go to a third party.
>
On Thu, 2010-04-08 at 15:34 -0500, Dennis Gilmore wrote:
>
> Im curious why you use virtualbox and not kvm/libvirt/virt-manager that are
> included by default in fedora? Im just trying to work out what is lacking in
> the default offerings that you go to a third party.
I can't speak for the o
abrt-addon-kerneloops-1.0.8-2.fc12.x86_64
> kernel-headers-2.6.32.10-90.fc12.x86_64
> kernel-devel-2.6.32.10-90.fc12.x86_64
> kernel-devel-2.6.32.9-70.fc12.x86_64
>
> it says
>
> sudo /etc/init.d/vboxdrv setup
> Stopping VirtualBox kernel module [
6_64
> kernel-headers-2.6.32.10-90.fc12.x86_64
> kernel-devel-2.6.32.10-90.fc12.x86_64
> kernel-devel-2.6.32.9-70.fc12.x86_64
>
> it says
>
> sudo /etc/init.d/vboxdrv setup
> Stopping VirtualBox kernel module [ OK ]
> Recompiling VirtualBox kerne
-2.6.32.10-90.fc12.x86_64
kernel-devel-2.6.32.9-70.fc12.x86_64
it says
sudo /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong
13 matches
Mail list logo
