On 02/14/2012 07:03 PM, Yang Bai wrote:
Hi all,
Since on X86, bios is always at the end of the address space, so I
have some thought about how to implement the seabios support for kvm
tool.
1. using kvm__register_mem to map the end of address space to the
guest then copy the code of seabios to this mem region. Just emulating
the bios chip.
2. leave the bios code alone and don't touch the guest's address
space. If the guest accesses the address belonging to the bios, it
will be an IO request and we can emulate the IO access to the bios
chip.
Any ideas about this?
Can I ask what's the purpose of mapping BIOS code to guest? Any usage?
Shouldn't BIOS's behavior be emulated by hypervisor? Thanks.
-cody
And question: How could I set the first instruction address after we
issue the vmlaunch instruction?
Thanks,
Yang
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
