So I installed my first KVM guest image (a prerelease of Ubuntu 9.10
that I had lying around) this morning (through virt-manager, as it
happens). Everything worked fine, the install was searingly fast
compared to the UML virtual machines I'm used to.
I got back to it this evening, restarted the
On 29 Nov 2009, Avi Kivity uttered the following:
66 0f 7f 07 movdqa %xmm0,(%rdi)
which we don't emulate.
x86-64 glibc 2.10 memset(), perhaps? On SSE-capable platforms that does
a whole bunch of
L(SSE0QB): movdqa %xmm0,-0xb0(%rdi)
L(SSE0QA): movdqa %xmm0,-0xa0(%rdi)
L(SSE0Q9):
On 29 Nov 2009, Avi Kivity stated:
Most likely, either this or something similar is called on a userspace
device driver. Can you check if this is triggered by starting X?
Damn thing hasn't recurred yet. I'll keep trying. (Obviously I'm not
properly replicating my original failure case.)
One
On 29 Nov 2009, Avi Kivity stated:
Most likely, either this or something similar is called on a userspace
device driver. Can you check if this is triggered by starting X?
*sigh* I just wasted twenty minutes trying to find some way, *any* way
to not start X under Ubuntu Karmic, so as to test
On 30 Nov 2009, Alejandro Riveira Fernández spake thusly:
When I install the infamous nvidia driver I use. « sudo stop gdm »
there are a start and restart aliases too see « man initctl ».
Aha! That's done it. New upstartish aliases I hadn't noticed...
FWIW, my qemu startup line (later
On 29 Nov 2009, n...@esperi.org.uk spake thusly:
One qemu-kvm-specific bug, definitely non-kernel-related, is this crash,
frequently encountered when hotadding more than one USB device (to an XP
guest, as it happens, but that doesn't look relevant here):
I also see a crash when using
So I've been using QEMU/KVM 0.12.5 happily to boot both various Linux
distributions and Windows XP. I upgraded to 0.13.0 (tip of stable-0.13
branch) to get virtio-serial (which recent libguestfses require).
I configured with --enable-vnc-thread because a quick perusal of relevant
list discussions
