Login or Register to Ask a Question and Join Our Community


Solaris

ALOM wont work when KVM connected to Sun Fire V440 server

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris ALOM wont work when KVM connected to Sun Fire V440 server
# 1  
Old 10-14-2010
ALOM wont work when KVM connected to Sun Fire V440 server
Hi,

I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.

On the ALOM output (console -f) I can watch the server start to boot and then ithangs halfway through. The last ALOM messages I see before it freezes include one about probing IDE devices and then I get an error about USB device.

I saw another post on here for someone which had the same problem but it doesn't say how it was fixed.
console -f not working in ALOM

Is there a way of getting the ALOM and KVM screen up and running together? At the moment it's either one or the other.

Thanks in advance
Jimmy

Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies

2. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

3. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

4. Solaris

Connect using ALOM to Sun Fire V210

I have bought from eBay a second hand Sun Fire V210 server and I'm really stumped at the lack of complete instructions on how to connect to it. I don't have a Windows machine, I've only got Ubuntu and OS X computers. None of them have an old RS-232 port on them either. In saying that, I have... (12 Replies)
Discussion started by: danijeljames
12 Replies

5. Solaris

Sun Fire v440 Over heat Problem.

Dear Team, I need some expert advice to my problem. We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies

6. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

7. Solaris

error messages in Sun Fire V440

Hello, I am seeing error messages in V440 (OS = solaris 8). I have copied here : The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day.. I... (5 Replies)
Discussion started by: upengan78
5 Replies

8. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

9. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

10. Solaris

Sun Fire V440 and Patch 109147-39

Got an curious issue. I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on. The patch modified mainly the linker libraries and commands. ... (2 Replies)
Discussion started by: BOFH
2 Replies
Login or Register to Ask a Question

LEARN ABOUT FREEBSD

kvm

KVM(3)							   BSD Library Functions Manual 						    KVM(3)

NAME

     kvm -- kernel memory interface

LIBRARY

     Kernel Data Access Library (libkvm, -lkvm)

DESCRIPTION

     The kvm library provides a uniform interface for accessing kernel virtual memory images, including live systems and crash dumps.  Access to
     live systems is via sysctl(3) for some functions, and mem(4) and kmem(4) for other functions, while crash dumps can be examined via the core
     file generated by savecore(8).  The interface behaves similarly in both cases.  Memory can be read and written, kernel symbol addresses can
     be looked up efficiently, and information about user processes can be gathered.

     The kvm_open() function is first called to obtain a descriptor for all subsequent calls.

COMPATIBILITY

     The kvm interface was first introduced in SunOS.  A considerable number of programs have been developed that use this interface, making back-
     ward compatibility highly desirable.  In most respects, the Sun kvm interface is consistent and clean.  Accordingly, the generic portion of
     the interface (i.e., kvm_open(), kvm_close(), kvm_read(), kvm_write(), and kvm_nlist()) has been incorporated into the BSD interface.
     Indeed, many kvm applications (i.e., debuggers and statistical monitors) use only this subset of the interface.

     The process interface was not kept.  This is not a portability issue since any code that manipulates processes is inherently machine depen-
     dent.

     Finally, the Sun kvm error reporting semantics are poorly defined.  The library can be configured either to print errors to stderr automati-
     cally, or to print no error messages at all.  In the latter case, the nature of the error cannot be determined.  To overcome this, the BSD
     interface includes a routine, kvm_geterr(3), to return (not print out) the error message corresponding to the most recent error condition on
     the given descriptor.

SEE ALSO

     kvm_close(3), kvm_getargv(3), kvm_getenvv(3), kvm_geterr(3), kvm_getfiles(3), kvm_getloadavg(3), kvm_getprocs(3), kvm_getswapinfo(3),
     kvm_nlist(3), kvm_open(3), kvm_openfiles(3), kvm_read(3), kvm_write(3), sysctl(3), kmem(4), mem(4)

BSD
								  April 25, 2010							       BSD