On 12/13/2010 04:26 PM, Adam Williamson wrote: > On Mon, 2010-12-13 at 16:14 -0500, Clyde E. Kunkel wrote: >> By long, I mean about 60 secs for the network to come up once I see the >> startup cmd and for reboot, I can go get a cup of coffee and come back >> to see the boot process finally underway. >> >> For the network slowness I wonder if this is related: I see that >> something is recreating /etc/hosts with an IP address that does not >> match what ifconfig has. I haven't touched how the network is setup >> with installation defaults since, oh, maybe Fedora 2. >> >> For restart, I do see a msg that says: Suspending testsuite: and then >> an increasing counter that is in the MBs. I can eventually kill it with >> several Ctrl-Alt-Del's. > > you've got a VM running. if you shut down with a VM running, libvirt now > nicely suspends it for you rather than just killing it dead. But this > takes some time. > > if you don't care about the contents of your VM(s), there's a libvirt > config option somewhere which turns this off. Amazing! virt-manager did not show the vm. However, I could connect to "testsuite" and turn it off and uncheck the start on boot. Reboot now stops for awhile at a dbus msg, but this may be related to the fact that I turned off bluetooth activation using systemctl as I see some dbus msgs prior to about a bad parameter. Now, any insights into what is going on with network activation? I see some bzs about the hosts file, but nothing about a fix. Regards, OldFart -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
