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-install.log is attached
anybody else is seeing this? Is there a cure?
regards,
--
regards,
Oleksandr Korneta
I'm running F12 x86_64, should this matter.
/The nice thing about standards is that there are so many to choose from./
2010/4/8 oleksandr korneta <atenrok@gmail.com>:
> cannot recompile VirtualBox driver module after recent kernel update
>
> $ rpm -qa | grep kernel
> kernel-2.6.32.10-90.fc12.x86_64
> kernel-2.6.32.9-70.fc12.x86_64
> kernel-firmware-2.6.32.10-90.fc12.noarch
> 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 * * * * * * * * * * * * *[ *OK *]
> Recompiling VirtualBox kernel module * * * * * * * * * * * [FAILED]
> *(Look at /var/log/vbox-install.log to find out what went wrong)
>
>
> vbox-install.log is attached
>
> anybody else is seeing this? Is there a cure?
This thread has a fix:
http://www.mail-archive.com/vbox-users@virtualbox.org/msg07263.html
In short, you're adding a one line change to a file (including sched.h).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-08-2010, 08:34 PM
Dennis Gilmore
Recompiling VirtualBox kernel module
On Thursday 08 April 2010 01:48:33 pm oleksandr korneta wrote:
> cannot recompile VirtualBox driver module after recent kernel update
>
> $ rpm -qa | grep kernel
> kernel-2.6.32.10-90.fc12.x86_64
> kernel-2.6.32.9-70.fc12.x86_64
> kernel-firmware-2.6.32.10-90.fc12.noarch
> 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 [ OK ]
> Recompiling VirtualBox kernel module [FAILED]
> (Look at /var/log/vbox-install.log to find out what went wrong)
>
>
> vbox-install.log is attached
>
> anybody else is seeing this? Is there a cure?
>
> regards,
Hi,
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.
Dennis
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 04:10 AM
Greg Woods
Recompiling VirtualBox kernel module
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 original poster, but for me, KVM is buggy, and
doesn't work at all without hardware virtualization. On my Pentium 4
dual core desktop, KVM is so slow that it's useless. VirtualBox performs
quite well.
At work I have a Core Duo desktop, and KVM performs well there but it
crashes. If I leave my VM turned on overnight, in the morning as soon as
I do a couple of things in the VM, it suddenly crashes down to the
"Guest not running" screen and I have to reboot. Xen on the other hand
runs multiple VM's rock solid.
As far as I can see, KVM is not yet ready for prime time, although
others have reported success with it. YMMV.
--Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Fri Apr 9 09:30:02 2010
Return-path: <bounce-debian-user=tom=linux-archive.org@lists.debian.org>
Envelope-to: tom@linux-archive.org
Delivery-date: Fri, 09 Apr 2010 08:53:34 +0300
Received: from liszt.debian.org ([82.195.75.100]:39544)
by s2.java-tips.org with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.69)
(envelope-from <bounce-debian-user=tom=linux-archive.org@lists.debian.org>)
id 1O079p-0002Mu-Gt
for tom@linux-archive.org; Fri, 09 Apr 2010 08:53:33 +0300
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with QMQP
id E1ED42D0FBD; Fri, 9 Apr 2010 06:25:22 +0000 (UTC)
Old-Return-Path: <gpall@ccf.auth.gr>
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on liszt.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-11.0 required=4.0 tests=LDOSUBSCRIBER,LDO_WHITELIST
autolearn=failed version=3.2.5
X-Original-To: lists-debian-user@liszt.debian.org
Delivered-To: lists-debian-user@liszt.debian.org
Received: from localhost (localhost [127.0.0.1])
by liszt.debian.org (Postfix) with ESMTP id D9DF62D9721
for <lists-debian-user@liszt.debian.org>; Fri, 9 Apr 2010 06:25:16 +0000 (UTC)
X-Virus-Scanned: at lists.debian.org with policy bank en-ht
X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3
tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham
Received: from liszt.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id EaksFVFq-LCP for <lists-debian-user@liszt.debian.org>;
Fri, 9 Apr 2010 06:25:09 +0000 (UTC)
X-policyd-weight: using cached result; rate: -7
Received: from hermes3.ccf.auth.gr (hermes3.ccf.auth.gr [155.207.1.69])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "AUTH Mail Servers", Issuer "AUTH Network Operations Center Certification Authority R3" (not verified))
by liszt.debian.org (Postfix) with ESMTPS id 0D7D92D0BFF
for <debian-user@lists.debian.org>; Fri, 9 Apr 2010 06:25:02 +0000 (UTC)
Received: from [155.207.112.12] (aris.ccf2.auth.gr [155.207.112.12])
(authenticated bits=0)
by hermes3.ccf.auth.gr (8.14.3/8.14.3) with ESMTP id o396OwO7014352
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 9 Apr 2010 09:24:59 +0300
Message-ID: <4BBEC83A.2090200@ccf.auth.gr>
Date: Fri, 09 Apr 2010 09:24:58 +0300
From: =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzqDOrM67zrvOsc+C?=
<gpall@ccf.auth.gr>
User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
MIME-Version: 1.0
To: vikram <austinium@yahoo.com>
CC: debian-user@lists.debian.org
Subject: Re: Error: Read from socket failed: Connection reset by peer
References: <559668.39179.qm@web31007.mail.mud.yahoo.com>
In-Reply-To: <559668.39179.qm@web31007.mail.mud.yahoo.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060707030807080305010704"
X-Virus-Scanned: clamav-milter 0.95.3 at hermes1
X-Virus-Status: Clean
X-Rc-Virus: 2007-09-13_01
X-Rc-Spam: 2008-11-04_01
Resent-Message-ID: <p7U-10Re1RI.A.yAD.ShsvLB@liszt>
Resent-From: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/573684
X-Loop: debian-user@lists.debian.org
List-Id: <debian-user.lists.debian.org>
List-Post: <mailto:debian-user@lists.debian.org>
List-Help: <mailto:debian-user-request@lists.debian.org?subject=help>
List-Subscribe: <mailto:debian-user-request@lists.debian.org?subject=subscribe>
List-Unsubscribe: <mailto:debian-user-request@lists.debian.org?subject=unsubscribe>
Precedence: list
Resent-Sender: debian-user-request@lists.debian.org
Resent-Date: Fri, 9 Apr 2010 06:25:22 +0000 (UTC)
This is a cryptographically signed message in MIME format.
vikram wrote:
> Hi,
>
> I get this while trying to scp onto a local machine(on the same
> subnet, both machines running Lenny).
>
> Read from socket failed: Connection reset by peer
> lost connection
>
> I am able to ping the machine fine.
>
> How can this be fixed?
>
> Thanks
> Vikram
>
>
It starts copying and then this, or you get this from the beginning?
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/4BBEC83A.2090200@ccf.auth.gr
04-09-2010, 08:24 AM
Ron Yorston
Recompiling VirtualBox kernel module
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.
>
>I can't speak for the original poster, but for me, KVM is buggy, and
>doesn't work at all without hardware virtualization. On my Pentium 4
>dual core desktop, KVM is so slow that it's useless. VirtualBox performs
>quite well.
Likewise not presuming to speak for the OP. I don't use KVM because
none of the machines I own supports hardware virtualisation. Excluding
the stuff in the attic that would be two desktops, a laptop and three
netbooks. On one of the desktops I use VMware Server and on one of the
netbooks I use QEMU.
I note that the OP is running an x86_64 kernel, but even that doesn't
guarantee that they can use KVM. One of the machines I use here at
work is an early Opteron. We have VMware Server on that.
What's lacking from the default offerings is support for processors
without hardware virtualisation.
Ron
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 12:18 PM
oleksandr korneta
Recompiling VirtualBox kernel module
on 04/08/2010 03:36 PM Kwan Lowe wrote:
> This thread has a fix:
> http://www.mail-archive.com/vbox-users@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 this matter.
/The nice thing about standards is that there are so many to choose from./
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 12:26 PM
oleksandr korneta
Recompiling VirtualBox kernel module
on 04/08/2010 04:34 PM Dennis Gilmore wrote:
> On Thursday 08 April 2010 01:48:33 pm oleksandr korneta wrote:
>> cannot recompile VirtualBox driver module after recent kernel update
>>
>> $ rpm -qa | grep kernel
>> kernel-2.6.32.10-90.fc12.x86_64
>> kernel-2.6.32.9-70.fc12.x86_64
>> kernel-firmware-2.6.32.10-90.fc12.noarch
>> 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 [ OK ]
>> Recompiling VirtualBox kernel module [FAILED]
>> (Look at /var/log/vbox-install.log to find out what went wrong)
>>
>>
>> vbox-install.log is attached
>>
>> anybody else is seeing this? Is there a cure?
>>
>> regards,
>
> Hi,
>
> 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.
perhaps because at the time started looking for ways to run a virtual
machine (quite recently) top ten hits in google were howtos on
virtualbox an not on kvm. And since you've asked, I just looked around
and found out that my machine does not support hardware virtualization
(Opteron dual core).
--
regards,
Oleksandr Korneta
I'm running F12 x86_64, should this matter.
/The nice thing about standards is that there are so many to choose from./
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 01:15 PM
Dennis Gilmore
Recompiling VirtualBox kernel module
On Friday 09 April 2010 07:26:23 am oleksandr korneta wrote:
> on 04/08/2010 04:34 PM Dennis Gilmore wrote:
> > On Thursday 08 April 2010 01:48:33 pm oleksandr korneta wrote:
> >> cannot recompile VirtualBox driver module after recent kernel update
> >>
> >> $ rpm -qa | grep kernel
> >> kernel-2.6.32.10-90.fc12.x86_64
> >> kernel-2.6.32.9-70.fc12.x86_64
> >> kernel-firmware-2.6.32.10-90.fc12.noarch
> >> 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 [ OK ]
> >> Recompiling VirtualBox kernel module [FAILED]
> >>
> >> (Look at /var/log/vbox-install.log to find out what went wrong)
> >>
> >> vbox-install.log is attached
> >>
> >> anybody else is seeing this? Is there a cure?
> >>
> >> regards,
> >
> > Hi,
> >
> > 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.
>
> perhaps because at the time started looking for ways to run a virtual
> machine (quite recently) top ten hits in google were howtos on
> virtualbox an not on kvm. And since you've asked, I just looked around
> and found out that my machine does not support hardware virtualization
> (Opteron dual core).
what do you get for "cat /proc/cpuinfo |grep svm" what model cpus do you
have? i have a pair of dual dual core opterons they run kvm great. one of
them has 12gb ram and has 13 guests running on it currently, I do agree we
need to come up with a way to support hardware that does not have hardware
virtualisation better. there is the kqemu kernel module in rpmfusion that
will give you accelerated virtualisation using tools that are native in fedora
for the rest. I bring it up because it seems vmware and virtual box regularly
break because there kernel modules don't build and you are left on your own
to fix it.
Dennis
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 02:22 PM
Greg Woods
Recompiling VirtualBox kernel module
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
> break because there kernel modules don't build and you are left on your own
> to fix it.
There are definite advantages to using things that are part of the
mainline kernel. When they work. For me, KVM often doesn't work, so I
have to use something else. It's that simple.
For what it's worth, Xen is supported by Red Hat in RHEL 5 (and
therefore by CentOS 5 as well), despite not being part of mainline.
VirtualBox is of course "on your own", but I have never had a problem
getting the kernel modules to build. I *have* had that problem with
VMware which, along with the $300 price tag for VMware Workstation, was
the reason for switching to VirtualBox in the first place.
--Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
04-09-2010, 04:14 PM
Dennis Gilmore
Recompiling VirtualBox kernel module
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 E2180 @ 2.00GHz
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 bios.
> > it seems vmware and virtual box regularly
> > break because there kernel modules don't build and you are left on your
> > own to fix it.
>
> There are definite advantages to using things that are part of the
> mainline kernel. When they work. For me, KVM often doesn't work, so I
> have to use something else. It's that simple.
what parts of it don't work? I use only kvm and run lots of guests. including
ones that see a significant work load. and have not experienced issues. im
using rhel5 and fedora 12 hosts. and a mixture of os's as guests. from fedora
to rhel, to debian, and open solaris. im not running windows guests so im not
sure how they work.
> For what it's worth, Xen is supported by Red Hat in RHEL 5 (and
> therefore by CentOS 5 as well), despite not being part of mainline.
> VirtualBox is of course "on your own", but I have never had a problem
> getting the kernel modules to build. I *have* had that problem with
> VMware which, along with the $300 price tag for VMware Workstation, was
> the reason for switching to VirtualBox in the first place.
>
> --Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines