(apologies if this doesn't get properly threaded into:
http://lists.nongnu.org/archive/html/qemu-devel/2019-04/msg03407.html)
> After upgrading host (Gentoo Linux) a Windows XP guest can't boot anymore.
>
> Some findings while testing:
>
> * XP image boots & works OK on an Intel machine (Gentoo Li
> Sorry Gabriele, Eduardo and Paolo pointed out that the patch was incomplete.
> I am not sure however how you are getting non zero data with the rdmsr on an
> AMD.
> Can you please try this instead ?
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index f524e7d929..cfec559aa3 100644
> --
env->features[FEAT_ARCH_CAPABILITIES]);
> -break;
> -}
> }
>
> /*
I'm getting the same error message at start time (patch applied to
official qemu-3.1.0-rc1 tarball):
8<
qemu: error: failed to set MSR 0x10a to 0x0
qemu:
/home/balducci/tmp/ins
> A colleague has confirmed this on his FX-8320 on Fedora 29 with the
> virt-next repo; so it's nothing that's special about your machine;
> it's 3.1 that really doesn't like the old AMDs.
ouch! does this mean that I must stop upgrading qemu or do you think
that some development work will be dire
hi
thanks for taking the time to reply
Dr. David Alan Gilbert writes:
> > I suspect that this might be some problem on my side, as I couldn't
> > find any similar report (apart some old (qemu-2.8.50) threads, that
> > didn't help)
>
> Not necessarily; can you tell me:
> a) At what point does it
hello
I'm building qemu from source and happily using it since a bit
(2.3.0)
Since 3.1.0-rc0 (including latest 3.1.0-rc1) I'm no more able to start
qemu, getting:
8<
install:115> qemu
qemu: error: failed to set MSR 0x10a to 0x0
qemu:
/home/balducci/tmp/i
