KVM on SL5 and 6
I've been using KVM on SL5 for a year or two now, and so far found the guest performance great, but everything else about it barely ready for primetime. From the recent XEN postings re SL6, I found out that it may be because my only interaction with KVM has been through libvert and virt-manager. Is there a better way to do things? Some of the main things missing in SL5 KVM via virt-manager are the ability to get decent screen resolutions (seem to be limited to about 1280x1024) and anything like VMWare snapshots. We'd set up a test SL6 KVM host, and the screen resolution of guests seemed fixed, but I'm still disappointed at how undeveloped the KVM interface is compared to EVERY OTHER VM software I've ever used. Pointers, or even just how you use KVM would be greatly appreciated. I honestly don't see how RedHat thinks they're competing with Hyper-V or VMWare with the offerings I've seen. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University
samba printing sl 6 from virtual box MS Win XP Pro
Has anyone successfully made samba work using the vboxnet virtual internal LAN of VirtualBox to allow a MS Win client to print to the Linux CUPS printer under SL 6? If so, I greatly would appreciate a copy of your samba configuration file. With my configuration file, I get errors such as: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.4-68.el6_0.2] tree connect failed: NT_STATUS_LOGON_FAILURE using smbclient from the linux side. This failure also happens when I use 127.0.0.1 as the allowed IP address (ifconfig -a shows lo on this address), not just the IP of vboxnet0 that does not exist except when VirtualBox is running a guest OS. Also, if you have had success, how did you setup the password file for samba in terms of encryption, password program, etc.? I have attempted to use both swat and webmin, as well as manual editing, but still cannot get samba to work. Note that I do NOT want samba on any external IP address, but only on an internal network. I had gotten samba to work with VMWare a number of years ago, but my notes from that epoch are not solving the current problems. For lack of licensing funding, I cannot run VMWare workstation at this time. Yasha Karant
Re: Supermicro IPMI watchdog issues.
On 2011-07-19 22:04, Kelsey Cummings wrote: This isn't exactly an scientific linux issue but I hope that folks here may be more likely to be using IPMI then some of the other lists. We have a series of Supermicro systems w/IPMI running RHEL 5.5. We're using IPMI primarily to monitor psu status and for the hardware watchdog support teamed with the watchdog service. 3 or 4 out of 8 identical systems have exhibited hardware watchdog triggered resets for no apparent reason. Best we can tell, despite the OS and hardware being perfectly healthy (no other errors, and the systems work fine after the watchdog is disabled,) the hardware watchdog is triggering a reset on its own, and worse, the boxes do not appear to come back from it. Anyone else seen similar issue or have any input? I have seen it. Under OpenBSD, in fact. I ended up shutting off the hardware watchdog after failing to find a fix. -- Garrett Holmstrom
