Hi Kevin. It looks like that change has already been checked in on the
develop branch in October. Judging by the dates on the releases, I'd guess
that would be included on version 20.1 (September), although I haven't
verified that specifically. It should definitely be in the develop branch,
and
Hi all,
Returning to this thread, I had to apply Ryan's version of the patch Gabe
mentioned to successfully boot the X86KvmCPU in FS mode. Thus, I do think
we should merge it, unless there's something I'm missing.
Has someone submitted this patch for review or is anyone planning to? If
not, I'm
That's good to know, thanks, Ryan!
Is there any reason not to merge this? I know it's not a "perfect"
solution, but it would be nice if people didn't keep running into this
issue.
Bobby, can you test on both Intel and AMD (let me know if you need access
to an Intel machine). If it works, can you
Thanks Gabe! That worked.
diff --git a/src/arch/x86/fs_workload.cc b/src/arch/x86/fs_workload.cc
index 3f46eba..f895cb6 100644
--- a/src/arch/x86/fs_workload.cc
+++ b/src/arch/x86/fs_workload.cc
@@ -189,6 +189,12 @@ FsWorkload::initState()
// 32 bit data segment
SegDescriptor dsDesc =
As far as I know those patches should no longer be necessary, although I
haven't tried to run KVM on x86 recently. Other problems could be that KVM
isn't enabled in your BIOS or your operating system, or that the
permissions on the device file gem5 needs to start a VM isn't set properly.
Ayaz,
As far as I know, those patches were superseded by this one:
https://gem5-review.googlesource.com/c/public/gem5/+/12278
src/arch/x86/system.cc was deleted in master, and I can find bits of the
patch scattered around different files, so it kind of looks like it's been
applied already?
Hello Ryan,
I think, if you are using an Intel machine, you will still need to apply
those patches. The conversation on this issue might be useful for you:
https://github.com/darchr/gem5art-experiments/issues/60
-Ayaz
On Thu, Oct 15, 2020 at 5:20 PM Gambord, Ryan via gem5-users <
