From: Anthony Liguori <anthony@codemonkey.ws>
To: Bruce Rogers <brogers@suse.com>,
qemu-devel@nongnu.org, jasowang@redhat.com
Subject: Re: [Qemu-devel] libvirt fails to start guest with latest code checkins
Date: Fri, 01 Feb 2013 16:16:22 -0600 [thread overview]
Message-ID: <87ip6bznm1.fsf@codemonkey.ws> (raw)
In-Reply-To: <510BD16002000048000D4B30@novprvoes0310.provo.novell.com>
Bruce Rogers <brogers@suse.com> writes:
> I get the following error message starting a linux guest via
> libvirt with the latest qemu git head:
>
> brogers2:/ # virsh start sles11
> error: Failed to start domain sles11
> error: internal error process exited while connecting to monitor: WARNING: failed to find acpi-dsdt.aml
> qemu-kvm: -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:59:31:da,bus=pci.0,addr=0x3: Property 'virtio-net-pci.netdev' can't find value 'hostnet0'
>
> I bisected it to this commit:
Can you provide full details and logs? I cannot reproduce this with a
simple invocation.
The 'qemu-kvm:' suffix suggests that you aren't just using a straight
qemu.git. Are you carrying any patches that may be affecting this?
Regards,
Anthony Liguori
>
> brogers@brogers1:~/osr/git/qemu> git bisect good
> 264986e2c8f14a0f4a32ac6f1e083905833a5fc7 is the first bad commit
> commit 264986e2c8f14a0f4a32ac6f1e083905833a5fc7
> Author: Jason Wang <jasowang@redhat.com>
> Date: Wed Jan 30 19:12:34 2013 +0800
>
> tap: multiqueue support
>
> I'm not sure if it's at all related to the windows networking problem also
> just reported.
>
> Bruce
>
next prev parent reply other threads:[~2013-02-01 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 21:29 [Qemu-devel] libvirt fails to start guest with latest code checkins Bruce Rogers
2013-02-01 22:16 ` Anthony Liguori [this message]
2013-02-01 22:41 ` Bruce Rogers
2013-02-02 0:03 ` Laszlo Ersek
2013-02-02 0:05 ` Bruce Rogers
2013-02-02 0:14 ` Anthony Liguori
2013-02-02 0:09 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip6bznm1.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=brogers@suse.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.