[sisyphus] vmnet отказался работать на 2.6.12-wks26-up-alt4

[sisyphus] vmnet отказался работать на 2.6.12-wks26-up-alt4

[Aleksey E. Birukov]

Вот такая ситуация на новом ядре.
[root@localhost root]# modprobe vmmon
[root@localhost root]# modprobe vmnet
[root@localhost root]# rm -f /etc/vmware/not_configured
[root@localhost root]# service vmware start
Starting VMware services:
   Virtual machine monitor                                                                     
[ DONE ]
   Virtual ethernet                                                                            
[ DONE ]
   Bridged networking on /dev/vmnet2                                                           
[FAILED]

На предидущем ядре все работает. Модули собраны по тойже технологии.

В /var/log/messages такое:
Aug 14 12:42:23 localhost kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000069
Aug 14 12:42:23 localhost kernel:  printing eip:
Aug 14 12:42:23 localhost kernel: b0234f49
Aug 14 12:42:23 localhost kernel: *pde = 00000000
Aug 14 12:42:23 localhost kernel: Oops: 0000 [#1]
Aug 14 12:42:23 localhost kernel: PREEMPT
Aug 14 12:42:23 localhost kernel: Modules linked in: vmnet vmmon binfmt_misc 
ipt_ULOG af_packet radeon drm lp rfcomm l2cap thermal fan shpchp p
ci_hotplug i2c_nforce2 nvidia_agp analog evdev ns558 gameport psmouse 
parport_pc parport 8250_pnp 8250 serial_core floppy hci_usb bluetooth ohc
i_hcd ehci_hcd usbcore snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_seq_dummy 
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_mixer_os
s snd_pcm snd_timer snd soundcore snd_page_alloc w83627hf i2c_sensor i2c_isa 
i2c_core 8139too mii ipt_MASQUERADE iptable_nat ipt_owner ipt_mult
iport ipt_limit ipt_LOG ipt_REJECT ipt_state iptable_filter ip_tables subfs 
dm_mod capability commoncap agpgart ip_conntrack_ftp ip_conntrack p
rocessor button ac ide_cd cdrom rtc ext3 jbd mbcache ide_disk ide_generic 
amd74xx ide_core
Aug 14 12:42:23 localhost kernel: CPU:    0
Aug 14 12:42:23 localhost kernel: EIP:    0060:[sk_alloc+9/320]    Tainted: P      
VLI
Aug 14 12:42:23 localhost kernel: EIP:    0060:[<b0234f49>]    Tainted: P      
VLI
Aug 14 12:42:23 localhost kernel: EFLAGS: 00210246   (2.6.12-wks26-up-alt4)
Aug 14 12:42:23 localhost kernel: EIP is at sk_alloc+0x9/0x140
Aug 14 12:42:23 localhost kernel: eax: b966000e   ebx: b9660a00   ecx: 
0000000b   edx: cddc6800
Aug 14 12:42:23 localhost kernel: esi: b9660a0c   edi: 00000000   ebp: 
00000001   esp: cdd91e0c
Aug 14 12:42:23 localhost kernel: ds: 007b   es: 007b   ss: 0068
Aug 14 12:42:23 localhost kernel: Process vmnet-bridge (pid: 12087, 
threadinfo=cdd90000 task=c31d2aa0)
Aug 14 12:42:23 localhost kernel: Stack: b9660a00 b9660a00 b9660a0c 00000000 
b9660a0c d119773d 00000010 00000020
Aug 14 12:42:23 localhost kernel:        00000001 00000000 b9660a00 cddc6805 
b9660a11 d119791f b9660a00 d1198418
Aug 14 12:42:23 localhost kernel:        b9660a0c cddc6800 b9660a00 00000000 
b9660a00 b023bb17 b9660a00 00000001
Aug 14 12:42:23 localhost kernel: Call Trace:
Aug 14 12:42:23 localhost kernel: Call Trace:
Aug 14 12:42:23 localhost kernel:  [pg0+551376701/1338229760] 
VNetBridgeUp+0xbd/0x1e0 [vmnet]
Aug 14 12:42:23 localhost kernel:  [<d119773d>] VNetBridgeUp+0xbd/0x1e0 
[vmnet]
Aug 14 12:42:23 localhost kernel:  [pg0+551377183/1338229760] 
VNetBridgeNotify+0x5f/0x130 [vmnet]
Aug 14 12:42:23 localhost kernel:  [<d119791f>] VNetBridgeNotify+0x5f/0x130 
[vmnet]
Aug 14 12:42:23 localhost kernel:  [register_netdevice_notifier+87/96] 
register_netdevice_notifier+0x57/0x60
Aug 14 12:42:23 localhost kernel:  [<b023bb17>] 
register_netdevice_notifier+0x57/0x60
Aug 14 12:42:23 localhost kernel:  [pg0+551374853/1338229760] 
VNetBridge_Create+0x75/0x240 [vmnet]
Aug 14 12:42:23 localhost kernel:  [<d1197005>] VNetBridge_Create+0x75/0x240 
[vmnet]
Aug 14 12:42:23 localhost kernel:  [pg0+551364082/1338229760] 
VNetFileOpIoctl+0x212/0x470 [vmnet]
Aug 14 12:42:23 localhost kernel:  [<d11945f2>] VNetFileOpIoctl+0x212/0x470 
[vmnet]
Aug 14 12:42:23 localhost kernel:  [handle_mm_fault+303/368] 
handle_mm_fault+0x12f/0x170
Aug 14 12:42:23 localhost kernel:  [<b01553af>] handle_mm_fault+0x12f/0x170
Aug 14 12:42:23 localhost kernel:  [do_page_fault+423/1480] 
do_page_fault+0x1a7/0x5c8
Aug 14 12:42:23 localhost kernel:  [<b0113ff7>] do_page_fault+0x1a7/0x5c8
Aug 14 12:42:23 localhost kernel:  [do_ioctl+70/112] do_ioctl+0x46/0x70
Aug 14 12:42:23 localhost kernel:  [<b0176006>] do_ioctl+0x46/0x70
Aug 14 12:42:23 localhost kernel:  [vfs_ioctl+83/448] vfs_ioctl+0x53/0x1c0
Aug 14 12:42:23 localhost kernel:  [<b0176193>] vfs_ioctl+0x53/0x1c0
Aug 14 12:42:23 localhost kernel:  [sys_ioctl+93/112] sys_ioctl+0x5d/0x70
Aug 14 12:42:23 localhost kernel:  [<b017635d>] sys_ioctl+0x5d/0x70
Aug 14 12:42:23 localhost kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Aug 14 12:42:23 localhost kernel:  [<b0103009>] syscall_call+0x7/0xb
Aug 14 12:42:23 localhost kernel: Code: 00 00 c7 44 24 0c 00 00 00 00 e9 89 fc 
ff ff ba ea ff ff ff c7 44 24 04 04 00 00 00 e9 51 fc ff ff 90 5
5 57 56 53 53 8b 6c 24 20 <8b> 75 68 85 f6 0f 84 fc 00 00 00 8b 4c 24 1c 51 56 
e8 d1 94 f1
Aug 14 12:42:23 localhost kernel:  <6>note: vmnet-bridge[12087] exited with 
preempt_count 1
Aug 14 12:42:31 localhost ntpd[8665]: kernel time discipline status change 41

-- 
$respect

Re: [sisyphus] vmnet отказался работать на 2.6.12-wks26-up-alt4

[Andrey Rahmatullin]

[-- Attachment #1: Type: text/plain, Size: 314 bytes --]

On Sun, Aug 14, 2005 at 12:49:34PM +0400, Aleksey E. Birukov wrote:
> Вот такая ситуация на новом ядре.
Попробуйте последний update с ftp.cvut.cz/vmware

-- 
WBR, wRAR (ALT Linux Team)
Powered by the ALT Linux fortune(8):

новый udev предлагает прекрасные возможности для таких хаков
		-- rider in #7085

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [sisyphus] vmnet отказался работать на 2.6.12-wks26-up-alt4

[Aleksey E. Birukov]

В сообщении от 14 Август 2005 13:16 Andrey Rahmatullin написал(a):
> On Sun, Aug 14, 2005 at 12:49:34PM +0400, Aleksey E. Birukov wrote:
> > Вот такая ситуация на новом ядре.
>
> Попробуйте последний update с ftp.cvut.cz/vmware
Я собирал последние модули, по предложенной вами схеме. Как использовать этот 
vmware-any-any-update93.tar.gz (он имеется ввиду под "update")?

-- 
$respect

Re: [sisyphus] vmnet отказался работать на 2.6.12-wks26-up-alt4

[Aleksey E. Birukov]

В сообщении от 14 Август 2005 13:16 Andrey Rahmatullin написал(a):
> On Sun, Aug 14, 2005 at 12:49:34PM +0400, Aleksey E. Birukov wrote:
> > Вот такая ситуация на новом ядре.
>
> Попробуйте последний update с ftp.cvut.cz/vmware
Разобрался. Попробывал. Теперь скрипт vmware-config.pl не может найти в 
хидерах нужные ему файлы:
What is the location of the directory of C header files that match your 
running
kernel? [/usr/src/linux/include] /usr/src/linux-2.6.12-wks26-up/include

The directory of kernel headers (version 2.6.12-wks26-up-alt4) does not match
your running kernel (version 2.6.11-wks26-up-alt4).  Even if the module were 
to
compile successfully, it would not load into the running kernel.

Что ему еще надо?

-- 
$respect

[sisyphus] Re: vmnet отказался работать на 2.6.12-wks26-up-alt4

[Konstantin A. Lepikhov]

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

Hi Aleksey!

Sunday 14, at 03:28:18 PM you wrote:

<skip>
> What is the location of the directory of C header files that match your 
> running
> kernel? [/usr/src/linux/include] /usr/src/linux-2.6.12-wks26-up/include
> 
> The directory of kernel headers (version 2.6.12-wks26-up-alt4) does not match
> your running kernel (version 2.6.11-wks26-up-alt4).  Even if the module were 
> to
> compile successfully, it would not load into the running kernel.
> 
> Что ему еще надо?
разберитесь сначала, с каким ядром вы хотите работать.

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@jabber.org
aka L.A. Kostis       write  to ==>mailto:lakostis@pisem.net.nospam

...The information is like the bank... 			  (c) EC8OR

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [sisyphus] Re: vmnet отказался работать на 2.6.12-wks26-up-alt4

[Aleksey E. Birukov]

В сообщении от 14 Август 2005 15:34 Konstantin A. Lepikhov написал(a):
> Hi Aleksey!
>
> Sunday 14, at 03:28:18 PM you wrote:
>
> <skip>
>
> > What is the location of the directory of C header files that match your
> > running
> > kernel? [/usr/src/linux/include] /usr/src/linux-2.6.12-wks26-up/include
> >
> > The directory of kernel headers (version 2.6.12-wks26-up-alt4) does not
> > match your running kernel (version 2.6.11-wks26-up-alt4).  Even if the
> > module were to
> > compile successfully, it would not load into the running kernel.
> >
> > Что ему еще надо?
>
> разберитесь сначала, с каким ядром вы хотите работать.
Сорри. Ошибся.

Все поставил. Работает.
2wrar: спасибо. Собрался rpm с правильными модулями после использования 
эни-апдейта.

Всем спасибо, а я спать :)

-- 
$respect

[sisyphus] Re: vmnet отказался работать на 2.6.12-wks26-up-alt4

[Vitaly Ostanin]

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

Aleksey E. Birukov пишет:
> Вот такая ситуация на новом ядре.
> [root@localhost root]# modprobe vmmon
> [root@localhost root]# modprobe vmnet
> [root@localhost root]# rm -f /etc/vmware/not_configured
> [root@localhost root]# service vmware start
> Starting VMware services:
>    Virtual machine monitor                                                                     
> [ DONE ]
>    Virtual ethernet                                                                            
> [ DONE ]
>    Bridged networking on /dev/vmnet2                                                           
> [FAILED]
> 
> На предидущем ядре все работает. Модули собраны по тойже технологии.
> 
> В /var/log/messages такое:
> Aug 14 12:42:23 localhost kernel: Unable to handle kernel NULL pointer 
> dereference at virtual address 00000069

У меня та же проблема, но с другим ядром:

2.6.12-std26-smp-alt3
kernel-modules-vmware-5.0.0-std26-smp-5.0.0-alt2.3
vmware-5.0.0-alt0.4.1

<skipped/>

-- 
Regards, Vyt
mailto:  vyt@vzljot.ru
JID:     vyt@vzljot.ru


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]