Hmm... That's interesting. It could have something to do with the I/O hole
for x86 at 3-4GB. This is a huge pain for gem5's config scripts. We hack
around this in our config scripts (e.g., for gem5-resources). See
https://gem5.googlesource.com/public/gem5-resources/+/refs/heads/stable/src/npb/confi
Hi Jason：
I make two tests：
1. I write a test code follow "open /dev/kvm” "create vm” "create vcpu”，it
has no error；
2. I put allocate pmem and create vcpu in create_vm function in gem5，not
outside create_vm，it has no error.
so I suspect if the allocate pmem function in gem5
Hello,
I wonder if you have a maximum number of vcpus set on your host system.
Otherwise, I can't think of any specific limitation to creating vcpus.
Cheers,
Jason
On Tue, May 11, 2021 at 2:36 AM Liyichao wrote:
> Hi Jason:
>
>
>
> I use strace to follow the call stack, I find that th
Hmm, I don't immediately know what's going wrong. I would extend the panic
on line 559 of vm.cc to also print the error code number so you can look it
up. I believe you can use `errno` like normal after calling `ioctl`. For
instance, you could add `strerror(errno)` to the panic.
Cheers,
Jason
On
