On 10/10/2012 04:47 PM, Shawn Furrow wrote:
I am using QEMU 1.1.0, the latest libvirt (from the git repo, but I've also tried release 0.10.0). Host os is Ubuntu 10.04 and the VM os is also 10.04.
I am getting the qemu version from qemu-system-x86_64 --version so I know its the one that is recognized from path.
Could you check 'virsh dumpxml guest0 | grep emulator' and check what's the qemu being ran by libvirt? Then take that path and run it with '<binary> -M ?' and check if the 'pc-1.1' is there. To fix your issue, try 'virsh edit guest0' and change the 'pc-1.1' to 'pc'.
As far as I know, no other versions have been installed on the host machine.
Shawn
On Wed, Oct 10, 2012 at 10:25 AM, Kashyap Chamarthy <kchamart@redhat.com <mailto:kchamart@redhat.com>> wrote:
On 10/10/2012 07:22 PM, Shawn Furrow wrote: > Hi all, > > I have been using Libvirt for several months now and I have only had minimal problems. I > had a particular setup and was starting up multiple guests just fine. However, with > seemingly no changes I now get the following error when trying to start a guest: > > virsh start guest0 > error: Failed to start domain guest0 > error: internal error Process exited while reading console log output: Supported machines are: > pc Standard PC (alias of pc-0.12) > pc-0.12 Standard PC (default) > pc-0.11 Standard PC, qemu 0.11 > pc-0.10 Standard PC, qemu 0.10 > isapc ISA-only PC > > Apparently, the machine argument settings were changed in recent versions of Libvirt. Or > at least that is what it seems. My guest's OS settings were: > > <os> > <type arch='x86_64' machine='pc-1.1'>hvm</type> > <boot dev='hd'/> > </os> > > > After getting this error I tried setting the machine argument to one of the "supported" > ones. Then I get this error: > > virsh start guest0 > error: Failed to start domain guest0 > error: Unable to read from monitor: Connection reset by peer > > Anyone have any ideas as to why this happened all of a sudden? I was not having any > problems before.
A couple of questions: - What libvirt version? - What OS/version? - What qemu-kvm version?
Can you reproduce the same issue with latest libvirt and qemu-kvm ? (that's what I have on my F18 machine -- libvirt-0.10.2-3.fc18.x86_64, qemu-kvm-1.2.0-11.fc18.x86_64) ?
That's the machine type I have.
# grep machine /etc/libvirt/qemu/f17jeos-3.xml <type arch='x86_64' machine='pc-1.2'>hvm</type>
>From the looks of it, I guess you have a fairly older versions of qemu-kvm?(or whatever your distro calls the binary as?)
> > Thanks, > Shawn > > -- > Virginia Tech > Bradley Department of Electrical and Computer Engineering > B.S. Electrical Engineering > B.S. Computer Engineering > > > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com <mailto:libvirt-users@redhat.com> > https://www.redhat.com/mailman/listinfo/libvirt-users >
-- /kashyap
-- Virginia Tech Bradley Department of Electrical and Computer Engineering B.S. Electrical Engineering B.S. Computer Engineering
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users