> A couple of nits here, alc@ fixed the PV memory restrictions so the 850M
> limit isn't a thing anymore: [...]
Very good to hear that my statement was wrong/outdated :)
> And, I think, there is a 64bit PV config now in development at:
> http://svnweb.freebsd.org/base/projects/amd64_xen_pv/
>
Hi,
> I answer to this mail because it's related to the discussion in this thread.
> As told I have my Debian Dom0s and now I wan't to create a FreeBSD Xen PV
> DomU. Does I really need a HVM guest like described here:
> http://wiki.sysconfig.org.uk/display/howto/Xen+FreeBSD+8.2+DomU+%28PV%29+
Hi Lukas,
> [...] I don't know whether there is support for Xen Dom0 on FreeBSD.
Unfortunately there isn't.
> I read that NetBSD support Xen Dom0 [...]
I haven't tried myself, but apparently NetBSD works rather well as Dom0. That
has long been on my list of things to test, though :)
Not sure
> What gave you that idea? The patches in that directory are the differences
> between the 9.0-RELEASE source tree and the one I used to build the AMI.
Oh, must have been wishful thinking then that it might go into FreeBSD and not
remain a bunch of separate patches... :)
>> The csup'ed source
>
> Details at
> http://www.daemonology.net/blog/2012-01-16-FreeBSD-now-on-all-EC2-instance-types.html
That's fantastic news! Really great stuff, Colin, especially the support for
m1.small instances!
Just two questions if I may, with regards to the m1.small AMI in particular:-
There's a fol
> I'm experiencing dreadful performance (sync throughput less than 1MB/sec)
> with both replication options, and am not quite sure how to troubleshoot
> that, because the network speed between two DomU's is otherwise well beyond
> 50MB/sec.
Have done some further testing. This only happens w
>
> Both DomU's are running on the same physical machine (CentOS 5.5 x86_64 with
> Xen 4.3.3 on Intel i7), [...]
sorry, typo: Xen 3.4.3, not 4.3.3.
Cheers
C.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
a week ago), XENHVM kernel (with
Janne's patch).
Both DomU's are running on the same physical machine (CentOS 5.5 x86_64 with
Xen 4.3.3 on Intel i7), their NICs are using the same isolated bridge on Dom0.
Cheers
Carsten
Regards,
Carsten Heesch
cars...@hee
>> int max = 24 /* MAX_SKB_FRAGS + (rx->status <= RX_COPY_THRESHOLD) */;
I've just recompiled XENHVM setting this for a quick test:
> int max = MAX_SKB_FRAGS;
Before, I was receiving said error message a lot; now it's gone. Also,
throughput has massively increased!
My test setup was:
Oops, sorry for posting this twice. I thought it didn't go through
with the first attempt.
On 29 Oct 2009, at 23:27, Carsten Heesch wrote:
Hi guys,
After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I
somehow made an interesting observation:
Even if the FreeBSD domU
Hi guys,
After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow
made an interesting observation:
Even if the FreeBSD domU does absolutely nothing, each of the assigned
vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't
matter, if domU is running with 1
Hi guys,
After FreeBSD 8.0-RC2 is working well (for me) on Xen 3.3.1, I somehow
made an interesting observation:
Even if the FreeBSD domU does absolutely nothing, each of the assigned
vCPUs will be reported by xentop as using 15%-25% CPU time. It doesn't
matter, if domU is running with 1
ers to see positive feedback, while 8.0-RELEASE is
coming closer :-)
Cheers
Carsten
On 25 Oct 2009, at 00:31, Carsten Heesch wrote:
I realised that it's still possible to use 8.0-BETA* as a target for
freebsd-update. So I investigated a bit further. For whatever it's
worth:
Th
I realised that it's still possible to use 8.0-BETA* as a target for
freebsd-update. So I investigated a bit further. For whatever it's
worth:
The problems described earlier started with BETA-4.
BETA-3 is fine with both GENERIC and XENHVM kernel, except that I see
this on the console and
Hi guys,
I don't know really when the bug was introduced, but maybe I can help
narrowing it down.
I have similar problems as others reported: Running FreeBSD 8.0-RC1 as
a guest in a Xen 3.3.1 environment fails with either "kernel trap 12"
in an endless loop (using amd64) or "kernel trap
15 matches
Mail list logo
