Public bug reported: Binary package hint: kvm
Ubuntu hardy heron 8.04 amd64 I've used this guide to get my virtualization kit: https://help.ubuntu.com/community/KVM KVM backend, libvirt-bin toolbox and virt-manager as the graphical manager. I have installed successfully the FreeBSD 7.0-RELEASE as a guest operating system. The problem appears to be when rebooting the machine, specifically: a) After the installing FreeBSD using the 7.0-release iso image. Upon finishing the FreeBSD installation (default values), I exited the installation and the machine was rebooted. I noticed the error. b) If I execute the reboot command within the guest operating system, the machine reboots and I notice the same error. The error is: "hptrr: no controller detected Trying to mount root from ufs:/dev/ad0s1a Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> e.g. ufs:da0s1a ? List valid disk boot devices <empty line> Abort manual input" I don't know if it's related, but I also cannot reboot using the virsh reboot command: $ virsh --connect qemu:///system reboot freebsd Connecting to uri: qemu:///system libvir: error : this function is not supported by the hypervisor: virDomainReboot error: Failed to reboot domain freebsd The shutdown command does not work. When I execute the libvirt shutdown command: $ virsh --connect qemu:///system shutdown freebsd Connecting to uri: qemu:///system Domain freebsd is being shutdown ...but the virtual machine does not shutdown. The only thing that helps in this case is to destroy (kill) the virtual machine, and start it again. $ virsh --connect qemu:///system destroy freebsd Connecting to uri: qemu:///system Domain freebsd destroyed $ virsh --connect qemu:///system start freebsd Connecting to uri: qemu:///system Domain freebsd started ...now the virtual machine works Attached the screenshots of the two cases. ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- kvm - guest freebsd 7 - reboot problems https://bugs.launchpad.net/bugs/239107 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
