I have just had this problem and it took me a while to figure out how to fix it, when it really ought to be up there in lights, so here is my attempt to help anyone else having the same issue.
I just rebooted my remote server, which uses KVM to create a test bed Linux install, for the first time since I put the whole KVM kit-and-kaboodle on it. But when I tried to restart the KVM client I got an error message:
Error starting domain: internal error Network 'default' is not active.
So here is how to fix that:
sudo virsh net-start default
sudo virsh net-autostart default
After a whole day of struggling with some very flaky technology and an 11 year old laptop, I have now built (cross-compiled to i386, in fact) and booted a working linux 3.0 kernel – if you want to try them as Debian packages (caveat emptor of course) then you can download them from here (slow link, be warned):
- Kernel image:
- Kernel headers:
These are built for my use – so if you want some other features you’ll have to build your own. They come from a bog standard kernel – follow the link from http://newgolddream.dyndns.info/blog if you want the sources.
The flakiness was nothing to do with the kernel but the hardware, and as I need to low spec laptop for my MSc project, so I guess I will have to suffer for my art.
Update: Now with (some) networking support – indeed I am typing this update on a Linux 3.0-rc1 machine, which must make this one of the world’s first Linux 3 blogs.
- Linux 3.0 (cartesianproduct.wordpress.com)
- Linus Renames 2.6.40 Kernel To Linux 3.0, Announces Release Candidate (linux.slashdot.org)
- Install/uninstall .deb files (sandeepbhalla.wordpress.com)
- Scott Moser: Upgrading an EBS Instance (ubuntu-smoser.blogspot.com)
- Kernel compilation and pesky mouse -2 (flossexperiences.wordpress.com)
- Darktable Photo Workflow – debian amd64 packages (kaigaraonline.wordpress.com)