The patch for QEMU that has been mentioned in comment #38 has been
merged already, so I'm marking this as Fix-Released there.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The commit in question is marked for stable:
commit 841c2be09fe4f495fe5224952a419bd8c7e5b455
Author: Maxim Levitsky
Date: Wed Jul 8 14:57:31 2020 +0300
kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host
To avoid complex and in some cases incorrect logic
Thanks @Babu for the clarifications!
I really hope that the qemu patch makes it in v6.0 - then I can better consider
picking it up as backport for qemu (already have a bug about that in bug
1921754 - therefore I'm setting the qemu task here as invalid)
The last step I can provide for the kernel
David used "5.6.0-1042.46-oem", the closest I had was "5.6.0-1052-oem"
so I tried that one.
With that my win10 install immediately crashed into the reported issue.
So to summarize:
1. I can reproduce it
2. Chances are high that it is fixed by kernel commit 841c2be0 "kvm: x86:
replace kvm_spec_ct
@Christian,
Yes. This following patch fixes the problem
https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01020.html
I saw your ping on the patch. I am not sure why it is not picked up. I am going
ping them today.
>If I might ask - how does the kernel fix you referenced interact with th
Finally I'm able to test on a Threadripper myself now.
Note: In regard to the commit that Babu identified - I'm on kernel
5.10.0-1020-oem so that patch would be applied already. I need to find
an older kernel to retry with that as well
(on that new kernel) I did a full Win10 install and it worked
Thanks Babu/Igor for chiming in!
@Babu
That exposed STIBP but not IBRS - isn't that what you tried to solve (for
userspace) in qemu via a v2 for the Rome chips?
=> https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg01020.html
I was recently pinging that, as it wasn't merged into the qemu 6
I remember seeing something similar before. This was supposed to be
fixed by the linux kernel commit.
commit 841c2be09fe4f495fe5224952a419bd8c7e5b455
Author: Maxim Levitsky
Date: Wed Jul 8 14:57:31 2020 +0300
kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host
# git descr
On Wed, 07 Apr 2021 13:00:23 -
David Ober <1915...@bugs.launchpad.net> wrote:
> I have not done any of what you are asking so not exactly sure how to
> change those values, been looking and reading but not finding what I
> want so thought it might be better to just ask how to do what yo are
>
I have not done any of what you are asking so not exactly sure how to
change those values, been looking and reading but not finding what I
want so thought it might be better to just ask how to do what yo are
asking. I did try CPU type EPYC and that did get past the error I am
seeing on install
--
On Sat, 03 Apr 2021 16:52:13 -
Christian Ehrhardt <1915...@bugs.launchpad.net> wrote:
> That is awesome David,
> qemu64 is like a very low common denominator with only very basic CPU
> features.
> While "copy host" means "enable all you can".
Also it's worth to try setting real CPU topolog
Ok, so you should be able to drop these lines one by one:
If that does not yet make it work, add those one by one (removing the features
of the named type)
/usr/bin/qemu-system-x86_64
kvm
pc-i440fx-hirsute
x86_64
efi
/usr/share/OVMF/OVMF_CODE_4M.fd
rom
pflash
yes
no
no
EPYC-Rome
AMD
That is awesome David,
qemu64 is like a very low common denominator with only very basic CPU features.
While "copy host" means "enable all you can".
We can surely work with that a bit, but until I get access to the same
HW I need you to do it.
If you run in a console `$virsh domcapabilities` it
I was playing around with this and find that if I change the
Configuration under CPUs from the default (uncheck "Copy host CPU
configuration") and select qemu64 in the Model drop down box I can get
it to work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks David,
I have no threadripper around atm, I think I can next week get hands on an EPYC
Rome, but that isn't 100% the same.
But gladly you tried this on the latest qemu 5.2 and since it is failing there
as well it might be worth to also report it upstream. That is a great community
which
** Attachment added: "security.png"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1915063/+attachment/5480895/+files/security.png
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am not using a virtio based drive so that should not be par of the issue, I
normally do not use the virtio iso until windows is installed to clear errors
in the device manager
I tried using even the version 5.2 from the hirsute release and that also is
not working
As a test I tried doing this
I started my tests on 21.04 Hirsute as that is what I had around.
qemu 1:5.2+dfsg-6ubuntu2 virt-manager 1:3.2.0-3 ovmf 2020.11-2
That started up the installer just fine no matter if I used SATA or virtio for
the root disk.
Next I tried Focal (as reported)
qemu 1:4.2-3ubuntu6.14 virt-manager 1:2.2
Info:
If the ISO is not auto-boointg (depends on some setup detail e.g. how you add
your extra CD images) you can still manually load the Windows EFI loader like:
FS0:
cd EFI
cd BOOT
BOOTX64.EFI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
I was just recently for a different case installing a Win10 guest and had the
ISOs available.
So I was trying to install an OVMF based one through virt-manager as you asked.
ISOs
- win10 20H2_v2
- virtio iso 0.1.190
I used the default "new guest" of virt-manager and then went into
"customize
I'm subscribing Christian to this bug, who is our QEMU expert.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915063
Title:
Windows 10 wil not install using qemu-system-x86_64
To manage notificatio
** Package changed: linux (Ubuntu) => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915063
Title:
Windows 10 wil not install using qemu-system-x86_64
To manage notifications about th
We believe that the latest version of Windows doesn't play nice with the
older version of QEMU - it seems Windows is broken somewhere between
4.2.0-2 and 5.0.0-6 on AMD Ryzen based processors (which is what we have
on the P620).
What are the recommendations for the best way for a Ubuntu customer t
apport information
** Tags added: apport-collected focal
** Description changed:
Steps to reproduce
install virt-manager and ovmf if nopt already there
copy windows and virtio iso files to /var/lib/libvirt/images
Use virt-manager from local machine to create your VMs with the disk, CP
25 matches
Mail list logo
