Qemuctl -qemu vdeq kvm -name Gutsy-Desktop -boot c -m 512 -hda /home/all/VirtualMachines/Ubuntu-Gutsy-Desktop-x86.ovl -k en-gb -net nic,model=rtl8139,macaddr=56:44:45:30:30:31,vlan=0 -soundhw es1370 -usb -net vde,sock=/var/run/kvm0. I'm not sure what changed in the interim but obviously something did.
I eventually found that by adding "-no-acpi" to the launch command-line they would boot successfully.
You could also check if theres already a newer kernel. I then booted the images with modified grub settings to watch the kernel log and saw it fails to find a timer as reported here. If the kernel panics start after a recent kernel downgrade, return to the latest installed kernel. Optional file system tools permit managing file systems not included in. I then downloaded, built, and installed kvm-60 thinking it was some strange issue that hadn't manifested previously. It uses libparted from the parted project to detect and manipulate partition tables. Once you finish the repair (s), power off said Linux VM, and reattach the Virtual Hard Disk to the previously non-booting VM. Tried to boot them earlier using the same launch scripts as usual and the process hung with the CPU looping at 100% usage. You can replicate this by - 1) creating a new Linux VM, 2) Attach the Virtual Hard Disk file from the non-booting VM to this new Linux VM, and 3) Booting said Linux VM off of an Ubuntu 16.04 Iso. I have working guest images of Ubuntu Gutsy 7.10 x86 with kvm-51 but hadn't used them in a while. I'm experiencing the same problem on Ubuntu Gutsy 7.10 x86_64 (2.6.22-14-generic).
0 kommentar(er)
