The 32 bit hosts are already a second class citizen especially with
support for running 64 bit guests under TCG. We are also limited by
testing as actual working 32 bit machines are getting quite rare in
developers personal menageries. For TCG supporting newer types like
Int128 is a lot harder
Jakob Bohm writes:
> Unfortunately, the rushed implementation of the SPF+DKIM+DMARC
> combination meant that handling of mailing lists wasn't properly
> integrated in the specifications. Which in turn resulted in some
> pretty horrible implementation ideas by both the DMARC group (having
> each
yes. fully bridged access via a tap is what I was looking for...but I
don't see anything on your command line identifying the guest network
as cadence_gem: no model=cadence_gem. Is it implicit?
I prefer to run all guests under bridged-tap so that they can be seen
by the host network...I guess
Hello everyone! I would like to thank you all for the project and the
tool developed across these years. I am a fan of yours! This is very
important to make the new technology era a better and open place to
work and live with!
I´m facing a weird listing image file behaviour (or at least I
I need to emulate the xilinx-zynq cortex-a9 since my hardware won't be
here anytime soon.
In experimenting and reading it looks like the cadence_gem driver is
only available when using the -net nic,model=cadence_gem option, and
not as a -device driver option. This seems to negate the ability to
On Tue, Sep 24, 2019 at 02:45:10PM -0500, Andrew Martin wrote:
> Hi Berto,
>
> Thank you for the detailed explanation! It is also worth noting that
> I am planning on hosting this qcow2 on a ZFS dataset (and ZFS does
> some in-memory caching with the ARC as well); does that have an
> impact on
El 25/9/19 a les 10:44, Alyssa Ross ha escrit:
> Jakob Bohm writes:
>
>> Unfortunately, the rushed implementation of the SPF+DKIM+DMARC
>> combination meant that handling of mailing lists wasn't properly
>> integrated in the specifications. Which in turn resulted in some
>> pretty horrible
On Wed, Sep 25, 2019 at 11:24:12AM -0400, Kent Dorfman wrote:
> yes. fully bridged access via a tap is what I was looking for...but I
> don't see anything on your command line identifying the guest network
> as cadence_gem: no model=cadence_gem. Is it implicit?
Instantiation of the device is
On Wed, Sep 25, 2019 at 08:52:45AM -0400, Kent Dorfman wrote:
> This seems to negate the ability to
> set up the guest in a fully bridged network configuration where it is
> seen as a generic station on the host network. I need a fully bridged
> network connection.
FWIW, on Xilinx's fork of
Thanks for the input!
Could you post your complete startup command sequence for the VM? I'm
trying to get a handle on whether I would need to create DTB files for
the image. Also I've noted that qemu can be picky about command
option ordering.
Thanks
On 9/25/19, Alexei Colin wrote:
> On Wed,
On Wed, Sep 25, 2019 at 12:46:40PM -0400, Kent Dorfman wrote:
> Thanks for the input!
>
> Could you post your complete startup command sequence for the VM? I'm
> trying to get a handle on whether I would need to create DTB files for
> the image. Also I've noted that qemu can be picky about
Also noticed that you are using a xilinx fork of the qemu package.
Would prefer to NOT use their fork, as I'm very much opposed to having
to register on corporate websites to acquire and use OS tools. Have
any xilinx specific enhancements made it back into the main
repository? does version 4.x
On 25/09/2019 17:05, Julianno Nogueira wrote:
Hello everyone! I would like to thank you all for the project and the
tool developed across these years. I am a fan of yours! This is very
important to make the new technology era a better and open place to
work and live with!
I´m facing a
- Original Message -
> From: "Alberto Garcia"
> To: "qemu-discuss"
> Sent: Wednesday, September 25, 2019 8:05:50 AM
> Subject: Re: Large qcow2 performance
> On Tue, Sep 24, 2019 at 02:45:10PM -0500, Andrew Martin wrote:
>> Hi Berto,
>>
>> Thank you for the detailed explanation! It is
14 matches
Mail list logo
