On 06/17/2010 08:01 AM, stan wrote:
> I haven't tried a stock kernel for a long time, so maybe the problem is
> gone now. It is so easy to compile a kernel that is custom I just keep
> doing it. Because the config has turned off so much cruft I don't use,
> it only takes about 10 to 15 minutes fo
On 06/16/2010 08:34 PM, Bruno Wolff III wrote:
> On Wed, Jun 16, 2010 at 18:24:05 -0700,
> Joe Conway wrote:
>>
>> But if I do nothing, my choices are:
>> 1) hope to get lucky on some future kernel update
>> 2) buy new hardware
>> 3) live with not using sc
On 06/16/2010 05:39 PM, Sam Varshavchik wrote:
> Based on the assumption that you are experiencing a kernel crash, there
> are two ways of obtaining diagnostics:
>
> 1) A serial console. Going retro, getting a null-modem adapter, and
> connecting the serial port of the ailing machine with the seri
I have had a problem with kernel freezes for several months. It started
when I first moved to the 2.6.31 kernel on Fedora 12. At that time it
was relatively infrequent. When the 2.6.32 kernel came out, the problem
became very bad -- every night when cron.daily runs the kernel would
hang. Note that
On 06/04/2010 10:56 AM, Christoph A. wrote:
> I was also looking for an answer to this question yesterday and got a hint:
>
> http://lists.fedoraproject.org/pipermail/users/2010-June/374160.html
>
> 1) set the video model to vga
> 2) within the VM: 'yum install system-config-display'
> -> use it
On 06/04/2010 10:43 AM, Dale J. Chatham wrote:
> Using virtual machine manager
> fedora core 13 vm
>
>
> How do I change the display resolution in the virtual machine? 1024x768
> seems to be all I can get.
>
> I've scoured every way I can think of, Fedora docs, VMM docs, KVM, etc.
Switch the
On 05/04/2010 09:05 AM, Jim wrote:
> Has anyone been successful installing Windows 7 on a Fedora 12 KVM ?
Yes
> Did you have any difficulties or sticking points ?
It has been a couple of months now, but none that stick out in my mind.
HTH,
Joe
signature.asc
Description: OpenPGP digital sign
On 03/17/2010 05:49 PM, Joe Conway wrote:
> On 03/17/2010 05:44 PM, Tom Horsley wrote:
>> On Wed, 17 Mar 2010 17:28:42 -0700
>> Joe Conway wrote:
>>
>>> A bit more sleuthing and I found that the culprit is dhclient. I am
>>> using a dynamically assigned ad
On 03/17/2010 06:02 PM, Tom Horsley wrote:
> On Wed, 17 Mar 2010 17:49:18 -0700
> Joe Conway wrote:
>
>> Interestingly I cannot even find dhclient among the listed components here:
>>
>> https://bugzilla.redhat.com/enter_bug.cgi?format=guided&product=Fedor
On 03/17/2010 05:44 PM, Tom Horsley wrote:
> On Wed, 17 Mar 2010 17:28:42 -0700
> Joe Conway wrote:
>
>> A bit more sleuthing and I found that the culprit is dhclient. I am
>> using a dynamically assigned address (pinned to a static IP at my dhcp
>> server), and I b
On 03/12/2010 01:59 PM, Tom Horsley wrote:
> On Fri, 12 Mar 2010 13:53:18 -0800
> Joe Conway wrote:
>
>> But it now shows up on both my host machine and independently on a
>> fedora 12 virtual machine. Both are x86_64. Are you running x86_64?
>
> Yep. 64 bit fedo
On 03/12/2010 01:35 PM, Tom Horsley wrote:
> On Fri, 12 Mar 2010 13:27:31 -0800
> Joe Conway wrote:
>
>> Anyone have any idea what package would determine the default MTU for a
>> bridged network device?
>
> I can't help with that, but my fully updated f12 system
On 03/11/2010 04:20 PM, Joe Conway wrote:
> Interestingly after a reboot:
>
>
> # brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.18a9051f09f0 no eth0
>
> # ifconfig
> br0
On 03/11/2010 04:37 PM, Tom Horsley wrote:
> On Thu, 11 Mar 2010 16:20:04 -0800
> Joe Conway wrote:
>
>> So I can at least work around the issue this way after starting the VM,
>> but still don't understand the root cause.
>
> The vnet0 may be coming from th
On 03/11/2010 02:52 PM, Joe Conway wrote:
> On 03/11/2010 02:31 PM, Rick Stevens wrote:
>> Check all interfaces under "ifconfig -a" and see if any of the participants
>> in the
>> bridge have a small MTU. IIRC, the smallest MTU will be propagated
>> to the b
On 03/11/2010 02:31 PM, Rick Stevens wrote:
> On 03/11/2010 02:14 PM, Joe Conway wrote:
>> In the last few days I've noticed network connectivity issues from
>> multiple virtual machines (fedora, centos, winxp) running on a fedora 12
>> host. What seemed odd was that
In the last few days I've noticed network connectivity issues from
multiple virtual machines (fedora, centos, winxp) running on a fedora 12
host. What seemed odd was that I could ping by host name, showing that
both the basic network functionality as well as DNS was working. What
was failing was br
17 matches
Mail list logo
