Hello Anthony,
See my response below.
Jason
On 6/27/2017 12:36 PM, Anthony PERARD wrote:
On Tue, Jun 27, 2017 at 10:19:26AM +0100, Wei Liu wrote:
CC Anthony and Stefano
On Mon, Jun 26, 2017 at 01:55:56PM -0400, Jason Dickens wrote:
I would like to inquire about q35 support in Xen? As far
I would like to inquire about q35 support in Xen? As far as I have been
able to tell, this has not been done? In the Xen version that I've been
working with (4.4), libxl_dm overrides any "-machine" argument I try to
pass to QEMU with "-machine xenfv". (it appears this still existing in
the last
I'm trying to find a solution to an immediate VM crash which occurs by
simply adding "bios='ovmf' to my configuration?
I started with a standard Ubuntu install which contained Xen 4.6.0 and
had the crash. The VM works fine booting w/ SeaBIOS once the
configuration line is removed. It also work
On 9/30/2016 3:47 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Sep 30, 2016 at 03:20:09PM -0400, Jason Dickens wrote:
Thanks Konrad,
[CC-ing Xen-devel again.]
I think you and David have successfully answered my question and pointed me
to the key code. I have already verified that the device
reasons for the address chosen, and it works on other
hypervisors (e.g. KVM) so although it might be easiest to change the
address I really don't want to unless its the only way to keep from a
Xen modification entirely.
Jason
On 9/30/2016 9:53 AM, David Vrabel wrote:
On 30/09/16 14:35,
s,
Jason
P.S. Regarding device_model_args=
I'm already using this and QEMU seems quite satisfied as the device is
realized as expected it simply doesn't receive verified MMIO accesses
for the device.
On 9/30/2016 7:33 AM, Wei Liu wrote:
Hello
On Thu, Sep 29, 2016 at 09:35:21AM
Hello,
My name is Jason Dickens and I'm a Research Scientist here at
GrammaTech. Some of our research involves securing hypervisors and we
have needed to add to and/or modify Xen. I have been successful in
modifying the source for various purposes, but my question now is about
device
