On Tue, Oct 4, 2011 at 4:16 PM, Les Mikesell lesmikesell@gmail.com wrote:
On Tue, Oct 4, 2011 at 2:51 PM, Negative negativebinomial@gmail.com wrote:
Since the crashes can be duplicated and are only caused by this one combination of events, I don't know.
On another machine, I had a case where none of the kvm guests would boot.
It
turned out to be a conflict between libvirt and the nvidia proprietary driver. I used an old version of the video driver until Nvidia caught up. (It only affected amd processors.)
Do you have to use the local video at all? What happens if you use freenx and run in a session started from a remote NX client?
Doesn't freenx use X? I haven't installed but will try it.
What I did try was to leave X off on workstation and built a fedora guest. I also connected to the workstation from another machine via ssh and I tried running the virt-viewer via X-forwarding, it stayed up for about 10 or 15 minutes and crashed. Since I could see the console on the work station then, it showed a kernel panic.
After rebooting I opened a terminal via ssh and it seems ok -- up for about 30 minutes so far, I'll check in the morning.
The trouble with that is I usually connect to the workshop via vnc, so I'm not sure the guest will be of much use.