--- Tommy Thorn
M. Ranjit Mathews wrote:
When I start the virtual machine, it says fd0 doesn't seem to be a floppy drive and that I can start the virtual machine without a floopy drive.
Sounds like a the virtual machine floppy is not configured correctly. Look in your .vmx file, it should contain something like
floppy0.fileName = "/dev/fd0"
It's in there: #!/usr/bin/vmware config.version = "7" virtualHW.version = "3" scsi0.present = "TRUE" memsize = "320" scsi0:0.present = "TRUE" scsi0:0.fileName = "SUSE82.vmdk" ide1:0.present = "TRUE" ide1:0.fileName = "/dev/cdrom" ide1:0.deviceType = "cdrom-raw" floppy0.fileName = "/dev/fd0" Ethernet0.present = "TRUE" sound.present = "TRUE" displayName = "SUSE82" guestOS = "suse" priority.grabbed = "normal" priority.ungrabbed = "normal"
If it does and you still have trouble, try looking for clues in the vmware.log file.
I don't know what to make of it: Feb 26 13:48:38: vmx| Creating thread 'Floppy', type 16 from self, pid=3997 Feb 26 13:48:38: vmx| VTHREAD declare thread 5 "Floppy" Feb 26 13:48:38: vmx| Created AIO Floppy pid=3997 sharedArea=0x55fe0000 size=0xa000Feb 26 13:48:42: Floppy| Linux_Floppy: Cannot determine status of /dev/fd0: Input/output error. Feb 26 13:48:42: Floppy| Msg_Post: Warning Feb 26 13:48:42: Floppy| [msg.floppy.invalidfilename] The filename "/dev/fd0" does not appear to be a valid floppy drive. Feb 26 13:48:42: Floppy| Please either change the filename in your configuration, Feb 26 13:48:42: Floppy| or correct "/dev/fd0" so that it points to a valid floppy device. Feb 26 13:48:42: Floppy| ---------------------------------------- Feb 26 13:48:48: vmx| Msg_Post: Warning Feb 26 13:48:48: vmx| [msg.device.startdisconnected] Device floppy0 will start disconnected.
When the boot proceeds gets to the cdrom, an oops message from the kernel appears and to get things back to normal, I have to restart the host system (dual Opteron 240)
Yes, I believe that might be a known problem currently without a workaround. However, the more detail you can provide on the oops the better. It possible it's a Linux kernel bug.
Oops 0002. vmware.log says: Feb 26 13:48:51: vcpu-0| UHCI: Global Reset Feb 26 13:48:51: vcpu-0| UHCI: HCReset Feb 26 13:48:51: vcpu-0| UHCI: HCReset Feb 26 13:48:52: mks| Caught signal 11 -- tid 4004 Feb 26 13:48:52: IO#4| Caught signal 11 -- tid 4003 Feb 26 13:48:52: mks| SIGNAL: eip 0x5586ff16 esp 0xfedff77c ebp 0xfedff794 Feb 26 13:48:52: IO#4| SIGNAL: eip 0x5586ff16 esp 0xfefff9cc ebp 0xfefff9e4 Feb 26 13:48:52: mks| SIGNAL: eax 0xfffffffc ebx 0xfedff7dc ecx 0x4 edx 0xa esi 0x78 edi 0x558cd160 Feb 26 13:48:52: IO#4| SIGNAL: eax 0xfffffffc ebx 0xfefffa04 ecx 0x1 edx 0x64 esi 0x78 edi 0x558cd160 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff77c : 0x08343474 0x010100b4 0xfedff794 0x0833c574 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefff9cc : 0xfefff9ac 0x00000010 0x00000000 0xfefffa04 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff78c : 0x00000004 0xfedff7ec 0xfedff9f4 0x081d1beb Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefff9dc : 0x559f7a48 0x083a8d58 0xfefffa14 0x081cdd48 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff79c : 0xfedff7dc 0x00000004 0x0000000a 0x08110de0 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefff9ec : 0xfefffa04 0x00000001 0x00000064 0x081ce278 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff7ac : 0x08410ce8 0x04a0000c 0x08411948 0x00000000 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefff9fc : 0x00000061 0x0000030d 0x0000030c 0x00000001 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff7bc : 0x01000050 0x00000000 0x08410f18 0x00000009 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefffa0c : 0x559f7a48 0x04000906 0xfefffa54 0x081cd71f Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff7cc : 0x00000003 0x00000002 0x00000000 0x00000009 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefffa1c : 0x559f7a48 0x0000ffff 0x00000000 0x00000000 Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff7dc : 0x00000023 0x00000001 0x0000006a 0x00000001 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefffa2c : 0x00000000 0x00000000 0x559f7670 0x0000030d Feb 26 13:48:52: mks| SIGNAL: stack 0xfedff7ec : 0x00000015 0x00000001 0x0000000b 0x00000001 Feb 26 13:48:52: IO#4| SIGNAL: stack 0xfefffa3c : 0x559f7a48 0x0000000a 0x05000a06 0x083a8d24 Feb 26 13:48:52: mks| Backtrace: Feb 26 13:48:52: IO#4| Backtrace: Feb 26 13:48:52: mks| Backtrace[0] 0xfedff3a8 eip 0x81d456a Feb 26 13:48:52: IO#4| Backtrace[0] 0xfefff5f8 eip 0x81d456a Feb 26 13:48:52: mks| Backtrace[1] 0xfedff418 eip 0x81d4323 Feb 26 13:48:52: IO#4| Backtrace[1] 0xfefff668 eip 0x81d4323 Feb 26 13:48:52: mks| Backtrace[2] 0xfedff49c eip 0x555bfbb1 Feb 26 13:48:52: IO#4| Backtrace[2] 0xfefff6ec eip 0x555bfbb1 Feb 26 13:48:52: mks| Backtrace[3] 0xfedff794 eip 0x557c3bf8 Feb 26 13:48:52: IO#4| Backtrace[3] 0xfefff9e4 eip 0x557c3bf8 Feb 26 13:48:52: mks| Backtrace[4] 0xfedff9f4 eip 0x81d1beb Feb 26 13:48:52: IO#4| Backtrace[4] 0xfefffa14 eip 0x81cdd48 Feb 26 13:48:52: mks| Backtrace[5] 0xfedffa44 eip 0x81d1484 Feb 26 13:48:52: IO#4| Backtrace[5] 0xfefffa54 eip 0x81cd71f Feb 26 13:48:52: mks| Backtrace[6] 0xfedffa64 eip 0x81d12b8 Feb 26 13:48:52: IO#4| Backtrace[6] 0xfefffa84 eip 0x807286c Feb 26 13:48:52: mks| Backtrace[7] 0xfedffa84 eip 0x810f4d2 Feb 26 13:48:52: IO#4| Backtrace[7] 0xfefffaf4 eip 0x81ce8d3 Feb 26 13:48:52: mks| Backtrace[8] 0xfedffaf4 eip 0x81ce8d3 Feb 26 13:48:52: IO#4| Backtrace[8] 0xfefffbd4 eip 0x555b90f0 Feb 26 13:48:52: mks| Backtrace[9] 0xfedffbd4 eip 0x555b90f0 Feb 26 13:48:52: IO#4| Backtrace[9] 00000000 eip 0x55878c77 Feb 26 13:48:52: mks| Backtrace[10] 00000000 eip 0x55878c77 Feb 26 13:48:52: IO#4| Unexpected signal: 11. Feb 26 13:48:52: mks| Unexpected signal: 11. Feb 26 13:48:52: IO#4| Loop on signal 11 -- tid 4003 at 0x080631f8. Feb 26 13:48:52: mks| Backtrace: Feb 26 13:48:52: IO#4| AIO panic loop Feb 26 13:48:52: mks| Backtrace[0] 0xfedff2d8 eip 0x805a99c Feb 26 13:48:52: mks| Backtrace[1] 0xfedff3a8 eip 0x81d45ce Feb 26 13:48:52: mks| Backtrace[2] 0xfedff418 eip 0x81d4323 Feb 26 13:48:52: mks| Backtrace[3] 0xfedff49c eip 0x555bfbb1 Feb 26 13:48:52: mks| Backtrace[4] 0xfedff794 eip 0x557c3bf8 Feb 26 13:48:52: mks| Backtrace[5] 0xfedff9f4 eip 0x81d1beb Feb 26 13:48:52: mks| Backtrace[6] 0xfedffa44 eip 0x81d1484 Feb 26 13:48:52: mks| Backtrace[7] 0xfedffa64 eip 0x81d12b8 Feb 26 13:48:52: mks| Backtrace[8] 0xfedffa84 eip 0x810f4d2 Feb 26 13:48:52: mks| Backtrace[9] 0xfedffaf4 eip 0x81ce8d3 Feb 26 13:48:52: mks| Backtrace[10] 0xfedffbd4 eip 0x555b90f0 Feb 26 13:48:52: mks| Backtrace[11] 00000000 eip 0x55878c77 Feb 26 13:48:52: mks| Core dump limit is 0 kb. Feb 26 13:48:52: IO#3| VTHREAD thread 9 start exiting Feb 26 13:48:52: IO#3| VTHREAD thread 9 exiting, 7 left Feb 26 13:48:52: vmx| VTHREAD thread 0 start exiting Feb 26 13:48:52: vmx| VTHREAD thread 0 exiting, 6 left Feb 26 13:48:52: IO#2| VTHREAD thread 8 start exiting Feb 26 13:48:52: IO#2| VTHREAD thread 8 exiting, 5 left Feb 26 13:48:52: IO#1| VTHREAD thread 7 start exiting Feb 26 13:48:52: IO#1| VTHREAD thread 7 exiting, 4 left Feb 26 13:48:52: mks| Attempting to dump core... Feb 26 13:48:52: vcpu-0| VTHREAD thread 4 start exiting Feb 26 13:48:52: vcpu-0| VTHREAD thread 4 exiting, 3 left Feb 26 13:48:53: mks| Child process 4006 failed to dump core (status 0x6). Feb 26 13:48:53: mks| Msg_Post: Error Feb 26 13:48:53: mks| [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (mks)
If I remove fd0 and cdrom from the virtual machine definition, the boot sequence makes it to a PXE boot; there's no more Oops.
QUESTION: How can I give the virtual machine access to a floppy drive and CDROM (I have an NEC BD2500 DVD-RW/ CD-RW)?
It sounds like your cdrom is correctly attached.
Is there a defined procedure to copy the DVD to a file and access it as a DVD from vmware? One complication is that I might want to install from 2 DVDs rather than do a minimal install.
/Tommy
-- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com