VMWare Fehler bei der Installation

[Hary00]

Hi Leute,
ich habe n dickes Problem. Ich Versuche VMWare 5.5.1 zu instalieren. Ich bin nach dem Tutorial http://www.linuxforen.de/forums/showpost.php?p=235439&postcount=8 vorgegangen.

Um die config zu machen habe ich die Option gewält:

cp /boot/config-x.y.z /usr/src/linux-x.y.z
cd /usr/src/linux-x.y.z
make menuconfig

Wenn ich nun make menuconfig eingebe, so kommt folgender Text:

NX-01:/usr/src/linux-2.6.16.13-4 # make menuconfig
HOSTCC scripts/basic/fixdep
/tmp/ccPtogKb.s: Assembler messages:
/tmp/ccPtogKb.s:12: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:14: Error: `test.4623(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:17: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:20: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:38: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:40: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:54: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:56: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:58: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:59: Error: bad register name `%r12'
/tmp/ccPtogKb.s:61: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:63: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:65: Error: bad register name `%r12'
/tmp/ccPtogKb.s:71: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:72: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:73: Error: bad register name `%r12'
/tmp/ccPtogKb.s:74: Error: bad register name `%rbp,%rsi)'
/tmp/ccPtogKb.s:76: Error: bad register name `%rcx'
/tmp/ccPtogKb.s:77: Error: bad register name `%rcx'
/tmp/ccPtogKb.s:85: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:86: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:88: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:89: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:98: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:99: Error: `str_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:100: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:101: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:103: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:104: Error: bad register name `%rdx)'
/tmp/ccPtogKb.s:105: Error: bad register name `%rax,%rdx)'
/tmp/ccPtogKb.s:106: Error: bad register name `%r11'
/tmp/ccPtogKb.s:107: Error: bad register name `%r8'
/tmp/ccPtogKb.s:109: Error: bad register name `%rdx,%r11)'
/tmp/ccPtogKb.s:114: Error: bad register name `%r8'
/tmp/ccPtogKb.s:115: Error: bad register name `%r9'
/tmp/ccPtogKb.s:116: Error: bad register name `%r8'
/tmp/ccPtogKb.s:119: Error: bad register name `%r8)'
/tmp/ccPtogKb.s:121: Error: bad register name `%r9)'
/tmp/ccPtogKb.s:123: Error: bad register name `%r11'
/tmp/ccPtogKb.s:124: Error: bad register name `%r8'
/tmp/ccPtogKb.s:125: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:126: Error: bad register name `%r11'
/tmp/ccPtogKb.s:130: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:135: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:149: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:158: Error: `size_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:160: Error: bad register name `%rdx,%rdx)'
/tmp/ccPtogKb.s:161: Error: `str_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:162: Error: `size_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:163: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:165: Error: bad register name `%rax'
/tmp/ccPtogKb.s:166: Error: bad register name `%rax'
/tmp/ccPtogKb.s:170: Error: `len_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:171: Error: `size_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:174: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:188: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:191: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:193: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:194: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:195: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:198: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:199: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:200: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:201: Error: `str_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:204: Error: `len_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:205: Error: `str_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:206: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:207: Error: bad register name `%rdx,%rax)'
/tmp/ccPtogKb.s:208: Error: bad register name `%rcx)'
/tmp/ccPtogKb.s:209: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:210: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:211: Error: `len_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:212: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:226: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:228: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:231: Error: bad register name `%r12'
/tmp/ccPtogKb.s:233: Error: bad register name `%r13'
/tmp/ccPtogKb.s:235: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:237: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:242: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:243: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:244: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:245: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:246: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:251: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:252: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:253: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:254: Error: bad register name `%r13,%rbx)'
/tmp/ccPtogKb.s:256: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:257: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:258: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:260: Error: bad register name `%r12'
/tmp/ccPtogKb.s:261: Error: bad register name `%rsp,%rbx)'
/tmp/ccPtogKb.s:263: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:267: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:268: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:269: Error: bad register name `%r12'
/tmp/ccPtogKb.s:272: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:276: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:279: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:281: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:282: Error: bad register name `%r12'
/tmp/ccPtogKb.s:285: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:293: Error: bad register name `%rax)'
/tmp/ccPtogKb.s:294: Error: `movslq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:295: Error: bad register name `%rax,%rdx,4)'
/tmp/ccPtogKb.s:296: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:309: Error: bad register name `%r13'
/tmp/ccPtogKb.s:311: Error: bad register name `%r12'
/tmp/ccPtogKb.s:313: Error: bad register name `%rsi,%rdi)'
/tmp/ccPtogKb.s:314: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:316: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:318: Error: bad register name `%rdi)'
/tmp/ccPtogKb.s:319: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:321: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:327: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:330: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:337: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:338: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:341: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:342: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:346: Error: bad register name `%r12)'
/tmp/ccPtogKb.s:347: Error: bad register name `%rax'
/tmp/ccPtogKb.s:353: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:357: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:358: Error: bad register name `%r13'
/tmp/ccPtogKb.s:361: Error: bad register name `%rax)'
/tmp/ccPtogKb.s:362: Error: bad register name `%r13'
/tmp/ccPtogKb.s:366: Error: bad register name `%rdx'
/tmp/ccPtogKb.s:367: Error: bad register name `%rdx'
/tmp/ccPtogKb.s:370: Error: bad register name `%rdx)'
/tmp/ccPtogKb.s:371: Error: `movsbq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:372: Error: bad register name `%rsi,%rax,2)'
/tmp/ccPtogKb.s:378: Error: bad register name `%r13'
/tmp/ccPtogKb.s:379: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:383: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:386: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:387: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:388: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:389: Error: bad register name `%r12'
/tmp/ccPtogKb.s:390: Error: bad register name `%r13'
/tmp/ccPtogKb.s:393: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:394: Error: bad register name `%r12)'
/tmp/ccPtogKb.s:395: Error: bad register name `%rax'
/tmp/ccPtogKb.s:411: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:415: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:417: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:418: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:425: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:428: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:429: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:431: Error: bad register name `%r9d'
/tmp/ccPtogKb.s:433: Error: bad register name `%r8d'
/tmp/ccPtogKb.s:437: Error: bad register name `%rax'
/tmp/ccPtogKb.s:438: Error: bad register name `%rax'
/tmp/ccPtogKb.s:440: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:441: Error: bad register name `%rax'
/tmp/ccPtogKb.s:443: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:444: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:450: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:451: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:452: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:461: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:466: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:483: Error: `len_config(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:510: Error: bad register name `%r14'
/tmp/ccPtogKb.s:512: Error: bad register name `%r13'
/tmp/ccPtogKb.s:514: Error: bad register name `%r12'
/tmp/ccPtogKb.s:516: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:518: Error: bad register name `%rdi'
/tmp/ccPtogKb.s:519: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:521: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:523: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:526: Error: bad register name `%rax'
/tmp/ccPtogKb.s:527: Error: bad register name `%rax'
/tmp/ccPtogKb.s:529: Error: bad register name `%rbp,%rbx)'
/tmp/ccPtogKb.s:530: Error: bad register name `%rax'
/tmp/ccPtogKb.s:531: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:532: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:533: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:534: Error: bad register name `%r12)'
/tmp/ccPtogKb.s:535: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:537: Error: `target(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:540: Error: bad register name `%rsp,%rbx)'
/tmp/ccPtogKb.s:543: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:547: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:555: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:558: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:559: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:560: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:563: Error: bad register name `%r12'
/tmp/ccPtogKb.s:566: Error: bad register name `%r12'
/tmp/ccPtogKb.s:567: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:568: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:569: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:570: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:572: Error: bad register name `%rsp,%rbx)'
/tmp/ccPtogKb.s:574: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:579: Error: bad register name `%r12)'
/tmp/ccPtogKb.s:580: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:583: Error: `target(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:586: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:588: Error: `target(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:592: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:593: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:594: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:595: Error: bad register name `%r12'
/tmp/ccPtogKb.s:596: Error: bad register name `%r13'
/tmp/ccPtogKb.s:597: Error: bad register name `%r14'
/tmp/ccPtogKb.s:601: Error: bad register name `%r12)'
/tmp/ccPtogKb.s:603: Error: bad register name `%r12'
/tmp/ccPtogKb.s:604: Error: bad register name `%r12'
/tmp/ccPtogKb.s:606: Error: bad register name `%r12'
/tmp/ccPtogKb.s:612: Error: bad register name `%rax)'
/tmp/ccPtogKb.s:613: Error: bad register name `%r13'
/tmp/ccPtogKb.s:616: Error: bad register name `%rdx'
/tmp/ccPtogKb.s:617: Error: `movsbq' is only supported in 64-bit mode
/tmp/ccPtogKb.s:618: Error: bad register name `%rcx,%rax,2)'
/tmp/ccPtogKb.s:620: Error: bad register name `%rdx)'
/tmp/ccPtogKb.s:624: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:629: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:633: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:637: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:641: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:659: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:663: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:665: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:667: Error: `depfile(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:673: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:676: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:677: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:679: Error: bad register name `%r9d'
/tmp/ccPtogKb.s:681: Error: bad register name `%r8d'
/tmp/ccPtogKb.s:685: Error: bad register name `%rax'
/tmp/ccPtogKb.s:686: Error: bad register name `%rax'
/tmp/ccPtogKb.s:688: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:689: Error: bad register name `%rax'
/tmp/ccPtogKb.s:691: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:692: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:696: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:697: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:698: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:702: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:703: Error: `depfile(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:710: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:711: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:712: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:721: Error: `stderr(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:726: Error: `depfile(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:743: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:745: Error: `target(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:747: Error: `cmdline(%rip)' is not a valid base/index expression
/tmp/ccPtogKb.s:750: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:756: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:757: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:759: Error: bad register name `%rbx)'
/tmp/ccPtogKb.s:771: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:781: Error: bad register name `%rbx'
/tmp/ccPtogKb.s:783: Error: bad register name `%rbp'
/tmp/ccPtogKb.s:786: Error: bad register name `%rsp'
/tmp/ccPtogKb.s:788: Error: bad register name `%rsi'
/tmp/ccPtogKb.s:794: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:795: Error: bad register name `%rax'
/tmp/ccPtogKb.s:796: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:797: Error: bad register name `%rax'
/tmp/ccPtogKb.s:798: Error: bad register name `%rbp)'
/tmp/ccPtogKb.s:799: Error: bad register name `%rax'
/tmp/ccPtogKb.s:802: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:803: Error: bad register name `%rsp)'
/tmp/ccPtogKb.s:805: Error: bad register name `%rsp'
make[1]: *** [scripts/basic/fixdep] Fehler 1
make: *** [scripts_basic] Fehler 2


Was kann ich dagegen tun? Kernel-source, perl, gcc und binutils sind installiert.

Hary00

[stefan.becker]

Hast du den Any-Any Patch installiert? Wenn nein, wie im Howto beschrieben ausführen.

[Hary00]

Danke das war's.... ^^ Wieder jemand der nicht lesen kann ^^ Ihr solltet diesen tipp mal in das von mir genannte Tut intigrieren.

[stefan.becker]

Schau mal in der Mitte des Beitrags, Überschrift "VMWARE Update bei Problemen" :-)

[Hary00]

Ja ok... ^^

Ich habe noch ein Problem und poste das hier gleich mal:
Ich habe VMware zum laufen bekommen und Windows XP instaliert. Allerdings ist mir Linux abgeschmiert (eingefrohren). Nun ich habe logischerweise meine System neu gestartet und muste fest stellten, dass das 10GB große Image (wo drauf WINXP instaliert ist) verschwunden ist. Selbst die suche bring mich nicht weiter. Das komische an der ganzen Sache ist allerdings, dass der Speicherplatz nicht wieder frei gegeben wurde.... Hat einer ne Idee was man da machen kann?

[stefan.becker]

Such mal im Verzeichnis "/lost+found" danach.

[Hary00]

Könntest du etwas näher beschreiben, wo ich das Verzeichniss finde? Über die suche habe ich es nicht gefunden...

[stefan.becker]

"/lost+found", also auf der Hauptebene.

[Hary00]

Mein System schreibt mir nur, dass dieses Verzeichniss nicht existiert.

[stefan.becker]

Schau doch mal bitte an der Kommadozeile.

Also "cd /lost+found". Und das als root-Login.

[Hary00]

NX-01:/home/nemesis # cd /lost+found
bash: cd: /lost+found: Datei oder Verzeichnis nicht gefunden


Es gibt das Verzeichniss nicht. Allerdings stürzt derzeit miene System dauernt ab.... Ist das normal, dass man das verzeichniss nicht finden kann? Nicht als User und nicht als root?

[stefan.becker]

Poste mal bitte die Datei /etc/fstab und den Pfad, wo sich das Image befand.

[Hary00]

/etc/fstab:

/dev/hda1 / reiserfs acl,user_xattr 1 1
/dev/hda5 /windows/C ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hdb5 /windows/D ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hdb6 /windows/E ntfs ro,users,gid=users,umask=0002,nls=utf8 0 0
/dev/hda2 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
/dev/hdb5 /mnt/captive-temp captive-ntfs defaults,noauto 0 0
/dev/hdb6 /mnt/captive-sicher captive-ntfs defaults,noauto 0 0
/dev/hda5 /mnt/captive-programme captive-ntfs defaults,noauto 0 0

Das Verzeichniss, wo sich das Image und die ganze config von VMware für WINXP befand war glaube ich /home/nemesis/vmware/.

[stefan.becker]

Ich sehe gerade, dass du ReiserFS verwendest. Meine Aussage bezog sich auf ext2/3. Tut mir leid, kann ich dir dann nicht sagen. Aber das müsste doch ein anderer Reiser Anwender wissen, wie das Verzeichnis, sofern es das gibt, dort heisst.

[Hary00]

Weg kann die Datei ja nicht sein. Schließlich beobachte ich immer den benutzten Festplattenspeicher. Ein 10GB Image macht sich da schon bemerkbar. Zufinden ist es aber nicht :( Selbst die interne suchfunltion findet das Teil net.... was ja so paradox ist, da es ja eigendlich doch da ist.

[kreol]

Versuch als root mal ein
find / -type d lost+found


Kreol

[Hary00]

hmm.... Da kommt bei mir nur:


NX-01:/home/nemesis # find / -type d lost+found
find: Der Pfad muß vor dem Suchkriterium stehen.
Usage: find [-H] [-L] [-P] [path...] [expression]

EDIT: Habe find / lost+found -type d mal eingegeben.. sucht gerade

EDIT2:
find: lost+found: Datei oder Verzeichnis nicht gefunden

[kreol]

Sry, -name vergessen: Muß heissen:
find / -type d -name lost+found

Hast Du überhaupt vorher schon ein fsck (als root) auf die verdächtige Partition losgelassen?


Kreol

[Hary00]

Der finden das Verzeichniss beim bestem Willen nicht.

[Nuno]

Hi,

probier es mal einfacher ...

locate lost

[kreol]

Ohne fsck kein lost+found... Erstmal sollte das FS gecheckt werden.


Kreol

[Hary00]

Da ist was interessanten bei rausgekommen:

Nach dem ich den Befehl ausgeführt habe kamm unteranderem auch /usr/sbin/mklost+found wieder. Den Befehl habe ich gleich mal ausgeführt.


NX-01:/home/nemesis # mklost+found
mklost+found 1.38 (30-Jun-2005)
*** buffer overflow detected ***: mklost+found terminated
======= Backtrace: =========
/lib64/libc.so.6(__chk_fail+0x2f)[0x2b22e4148edf]
/lib64/libc.so.6[0x2b22e4148419]
/lib64/libc.so.6(_IO_default_xsputn+0x89)[0x2b22e40e1c79]
/lib64/libc.so.6(_IO_vfprintf+0x1497)[0x2b22e40ba077]
/lib64/libc.so.6(__vsprintf_chk+0x9d)[0x2b22e41484bd]
/lib64/libc.so.6(__sprintf_chk+0x80)[0x2b22e4148400]
mklost+found[0x400aac]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2b22e4095154]
mklost+found[0x400949]
======= Memory map: ========
00400000-00401000 r-xp 00000000 03:01 53073 /usr/sbin/mklost+found
00501000-00502000 rw-p 00001000 03:01 53073 /usr/sbin/mklost+found
00502000-00523000 rw-p 00502000 00:00 0 [heap]
2b22e3f5b000-2b22e3f76000 r-xp 00000000 03:01 29842 /lib64/ld-2.4.so
2b22e3f76000-2b22e3f77000 rw-p 2b22e3f76000 00:00 0
2b22e3f77000-2b22e3f78000 r--p 00000000 03:01 41981 /usr/lib/locale/de_DE.utf8/LC_MESSAGES/SYS_L C_MESSAGES
2b22e3f78000-2b22e3f7f000 r--s 00000000 03:01 41659 /usr/lib64/gconv/gconv-modules.cache
2b22e3fa4000-2b22e3fa5000 rw-p 2b22e3fa4000 00:00 0
2b22e3fa5000-2b22e3fe0000 r--p 00000000 03:01 41982 /usr/lib/locale/de_DE.utf8/LC_CTYPE
2b22e4076000-2b22e4078000 rw-p 0001b000 03:01 29842 /lib64/ld-2.4.so
2b22e4078000-2b22e419e000 r-xp 00000000 03:01 29849 /lib64/libc-2.4.so
2b22e419e000-2b22e429e000 ---p 00126000 03:01 29849 /lib64/libc-2.4.so
2b22e429e000-2b22e42a1000 r--p 00126000 03:01 29849 /lib64/libc-2.4.so
2b22e42a1000-2b22e42a3000 rw-p 00129000 03:01 29849 /lib64/libc-2.4.so
2b22e42a3000-2b22e42a9000 rw-p 2b22e42a3000 00:00 0
2b22e42a9000-2b22e42b6000 r-xp 00000000 03:01 43963 /lib64/libgcc_s.so.1
2b22e42b6000-2b22e43b5000 ---p 0000d000 03:01 43963 /lib64/libgcc_s.so.1
2b22e43b5000-2b22e43b6000 rw-p 0000c000 03:01 43963 /lib64/libgcc_s.so.1
7fffc6b39000-7fffc6b4f000 rw-p 7fffc6b39000 00:00 0 [stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vdso]
Abgebrochen


Nun also damit kann ich nichts anfangen, außer dass genau diese Datein vor dem Any-Any Patch Probleme beim instalieren von VMWare gemacht haben.

Dann habe ich fsck ausgeführt:


NX-01:/home/nemesis # fsck
fsck 1.38 (30-Jun-2005)
reiserfsck 3.6.19 (2003 www.namesys.com)

************************************************** ***********
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
************************************************** ***********

Will read-only check consistency of the filesystem on /dev/hda1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):y
fsck.reiserfs /dev/hda1 failed (status 0x10). Run manually!


Wie starte ich das manuell? Ich dachte Konsole ist schon manuell genug?

EDIT: Ich habe mich mal auf die manuelle Suche nach der Datei gemacht. Ich habe bei jedem Ordner im Hauptverzeichniss die Größe berechnen lassen (Konqueror). Ein Verzeichniss müste ja mindestens 10GB groß sein, wie die Image datei. Dem ist allerdings nicht so...

[kreol]

Was ist an
Do you want to run this program?[N/Yes] (note need to type Yes if you do):y
fsck.reiserfs /dev/hda1 failedso unverständlich? Yes für Ja, N für Nein, y reicht nicht.... Die Partion sollte auch nicht rw eingehängt sein. Wäre auch gut, sie im Befehl anzugeben... Ergo: Lies doch die manpage von fsck bevor Du irgendwas machst. Und vllt. auch ein bisschen von den Links aus meiner Signatur...


Kreol

[Hary00]

Woher soll ich das den wissen? Nicht jeder kann vom einen auf den anderen Tag die Linux Syntax und rafft die Fehlermeldungen. Ich habe in den Links nichts zu dem Problem gefunden. Was für Parameter muss ich nun eingeben, damit hda1 gechekt wird? Und wie mounte ich die ro?


EDIT: Ich bin echt total doof. Ich habe nicht bemerkt, dass vmworkstation unter root war, als ich WINXP installiert habe. Folge ist natürlich, dass das image in /root/vmware/ installiert wurde. Mit Linux interner Suchfunktionen kann man als user aber net in die root Verzeichnisse opsen. Nun ok tut mir leid für so vie Wirbel, aber ich habe die Datei wieder gefunden.
Damit ich VMWare nicht immer als Root ausführen muss um an das Image zu kommen habe ich den kompletten Windows XP Ordner in /home/nemesis/vmware/ geschoben. Nun ok ich habe nun wieder VMWare gestartet. Dabei kamm folgende Fehlermeldung:in einem Fenster:

Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.

Failed to initialize monitor device.

Unable to change virtual machine power state: Cannot find a valid peer process to connect to.

Failed to reply to the dialog: Pipe: Read failed

Ich habe hier im Forum gelesen, dass man die vmware-config.pl noch einmal durchlaufen lassen soll. Folgenden kommt bei raus:

NX-01:/home/nemesis # vmware-config.pl
Making sure services for VMware Workstation are stopped.

Stopping VMware services:
Virtual machine monitor done
Bridged networking on /dev/vmnet0 done
DHCP server on /dev/vmnet1 done
Host-only networking on /dev/vmnet1 done
DHCP server on /dev/vmnet8 done
NAT service on /dev/vmnet8 done
Host-only networking on /dev/vmnet8 done
Virtual ethernet done

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the mime type icons?
[/usr/share/icons]

What directory contains your desktop menu entry files? These files have a
.desktop file extension. [/usr/share/applications]

In which directory do you want to install the application's icon?
[/usr/share/pixmaps]

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable for your
running kernel. Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running
kernel? [/lib/modules/2.6.16.13-4-default/build/include]

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmmon-only'
make -C /lib/modules/2.6.16.13-4-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default'
make -C ../../../linux-2.6.16.13-4 O=../linux-2.6.16.13-4-obj/x86_64/default modules
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
CC [M] /tmp/vmware-config1/vmmon-only/common/cpuid.o
CC [M] /tmp/vmware-config1/vmmon-only/common/hash.o
CC [M] /tmp/vmware-config1/vmmon-only/common/memtrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/phystrack.o
CC [M] /tmp/vmware-config1/vmmon-only/common/task.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-Werror-implicit-function-declaration" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wdeclaration-after-statement" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wno-pointer-sign" is valid for C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for Ada/C/ObjC but not for C++
cc1plus: warning: command line option "-ffreestanding" is valid for C/ObjC but not for C++
/tmp/vmware-config1/vmmon-only/common/task_compat.h: In function ‘void Task_Switch_V45(VMDriver*, Vcpuid)’:
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$validEIP’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$cs’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rsp’ may be used uninitialized in this function
/tmp/vmware-config1/vmmon-only/common/task_compat.h:1713: warning: ‘sysenterState$rip’ may be used uninitialized in this function
CC [M] /tmp/vmware-config1/vmmon-only/common/vmx86.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/compat.o
CC [M] /tmp/vmware-config1/vmmon-only/vmcore/moduleloop.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config1/vmmon-only/vmmon.mod.o
LD [M] /tmp/vmware-config1/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
The module loads perfectly in the running kernel.

This program previously created the file /dev/vmmon, and was about to remove it.
Somebody else apparently did it already.

This program previously created the file /dev/parport0, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport1, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport2, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/parport3, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet0, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet1, and was about to remove
it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet8, and was about to remove
it. Somebody else apparently did it already.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?
(yes/no) [yes] yes

Extracting the sources of the vmnet module.

Building the vmnet module.

Building for VMware Workstation 5.5.x.
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-config1/vmnet-only'
make -C /lib/modules/2.6.16.13-4-default/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default'
make -C ../../../linux-2.6.16.13-4 O=../linux-2.6.16.13-4-obj/x86_64/default modules
CC [M] /tmp/vmware-config1/vmnet-only/driver.o
CC [M] /tmp/vmware-config1/vmnet-only/hub.o
CC [M] /tmp/vmware-config1/vmnet-only/userif.o
CC [M] /tmp/vmware-config1/vmnet-only/netif.o
CC [M] /tmp/vmware-config1/vmnet-only/bridge.o
CC [M] /tmp/vmware-config1/vmnet-only/procfs.o
CC [M] /tmp/vmware-config1/vmnet-only/smac_compat.o
CC [M] /tmp/vmware-config1/vmnet-only/smac_linux.x86_64.o
LD [M] /tmp/vmware-config1/vmnet-only/vmnet.o
Building modules, stage 2.
MODPOST
CC /tmp/vmware-config1/vmnet-only/vmnet.mod.o
LD [M] /tmp/vmware-config1/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-2.6.16.13-4-obj/x86_64/default'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-config1/vmnet-only'
The module loads perfectly in the running kernel.

insserv: Service network has to be enabled for service VMware
insserv: Service syslog has to be enabled for service VMware
insserv: exiting now!
illegal runlevel specified for vmware: r
Starting VMware services:
Virtual machine monitor done
Virtual ethernet done
Bridged networking on /dev/vmnet0 done
Host-only networking on /dev/vmnet1 (background) done
Host-only networking on /dev/vmnet8 (background) done
NAT service on /dev/vmnet8 done

The configuration of VMware Workstation 5.5.1 build-19175 for Linux for this
running kernel completed successfully.

You can now run VMware Workstation by invoking the following command:
"/usr/bin/vmware".

Enjoy,

--the VMware team


Nachdem ich das ausgeführt habe kann ich zwar VMWare normal starten, allerdings ist beim nächsten System start das selbe Problem.

[Hary00]

Kann mir den keiner helfen? Ich muss jedes mal das vm Modul erstellen und weis nicht, was ich dagegen machen kann, dass es bleibt.