On 12/22/12 07:29, Mark Felder wrote:
On Fri, 21 Dec 2012 12:26:36 -0600
Jay West jw...@ezwind.net wrote:
All our FreeBSD use is now under Xenserver 6.1. I was curious, given the
port of xe-guest-utilities that allows online migrations and such. after
installing those tools (thus PVM/64),
On 05/30/12 17:40, Sean Bruno wrote:
And, I think, there is a 64bit PV config now in development at:
http://svnweb.freebsd.org/base/projects/amd64_xen_pv/
This is prerequisite work for a dom0 on freebsd which is under
development. Stay tuned, things are happening!
Interesting, Sean!
FreeBSD
Hello,
89 processes: 4 running, 71 sleeping, 14 waiting
CPU: 77.1% user, 0.0% nice, 21.1% system, 1.8% interrupt, 0.0% idle
Mem: 151M Active, 194M Inact, 96M Wired, 3508K Cache, 60M Buf, 41M Free
Swap: 512M Total, 596K Used, 511M Free
PID USERNAME PRI NICE SIZERES STATETIME
On 05/07/12 11:50, Ivan Voras wrote:
Hi,
Is XENHVM usable on 9-STABLE amd64? I seem to recall some problems
early in 9-current.
I still see timekeeping problems with -RELEASE, altough switching to HTC
*appears to* mitigate the problem somewhat.
Other than that, the OS runs stable, but
On 09/15/11 05:43, Janne Snabb wrote:
On Mon, 12 Sep 2011, Justin T. Gibbs wrote:
I'm planning to ask RE for permission to merge the following netfront
fixes (listed below) into 9.0/head.
Assuming this is the same patch that I posted on the list after someone
sent it to me, it seems to
On 08/27/11 18:46, Ben C. wrote:
Hello,
Yes indeed. I've verified on 8.2 and BETA1. Seemingly exact same
issue. Running a NetBSD(-CURRENT) dom0. Happy to see progress but
it's not quite there yet I guess.
I've tried changing the model= line around and some other random,
brute-force
On 08/24/11 20:02, Sean Bruno wrote:
On Wed, 2011-08-24 at 02:24 -0700, DeuZa wrote:
I tried setting machdep_disable_rtc_set to 1, but it made no difference.
Hello,
Same thing here wth machdep_disable_rtc_set 1, always :
Aug 24 10:00:06 mouette kernel: rtc0: [XEN] xen_rtc_settime
On 08/23/11 14:25, Manuel Bouyer wrote:
Furthermore, I couldn't find an equivalent of independent_wallclock on
the dom0 (NetBSD - message cc'd to port-xen@netbsd)
What is independent_wallclock ?
A fine question. I think it's a linux/freebsd i386 sysctl that decouples
the domU clock from
On 08/22/11 22:17, Sean Bruno wrote:
Huh, this used to exist. But anyway, try this:
http://forums.freebsd.org/showpost.php?p=105415postcount=15
Sean
Hi Sean,
I tried setting machdep_disable_rtc_set to 1, but it made no difference.
Furthermore, I couldn't find an equivalent of
Hello,
During my tests with 9.0, I have found another issue that I would like
to bring your attention to.
On all three 9.0-BETA1 virtual machines installed (on a NetBSD dom0,
should it matter) I'm encountering the infamous 'runtime went backwards'
messages (the VM's been up for days, it seems
On 08/22/11 16:43, DeuZa wrote:
2011/8/22 Hugo Silva h...@barafranca.com
Hello,
Hello Hugo, I was in the same cas (I think)
I use a workaround on my VPS :
machdep.independent_wallclock: 1
And the ntpd is fine now, I know it's just a workaround, but practice for
running ntpd on Xen
On 05/25/11 17:20, Hugo Silva wrote:
On 05/24/11 21:14, Hugo Silva wrote:
On 05/24/11 14:45, Hugo Silva wrote:
Trying to ssh to the VM produces the error in the subject line on the
FreeBSD domU; It's impossible to login.
Some more information for those looking to reproduce this: the above
On 05/29/11 14:11, K. Macy wrote:
Just to verify, other guests (e.g. Linux || NetBSD) don't exhibit this
problems? It sounds almost as if xend isn't configuring the domain
properly.
Hello,
I'm not sure about Linux but a NetBSD 5.1 PV domU works fine. Others are
running Linux PV on NetBSD
On 05/25/11 10:40, Yann KEMPF wrote:
It's due to a NetBSD issue. NetBSD doesn't support multiple CPU and Xen
simultaneously.
That's for dom0 and NetBSD domUs. It is perfectly capable of running SMP
Linux PV, OpenIndiana, or SMP HVM guests.
___
On 05/25/11 12:55, Janne Snabb wrote:
On Tue, 24 May 2011, Sean Bruno wrote:
I've installed a netbsd-current dom0 and the 3.3.2 xen hypervisor on
Why such an old version? Wouldn't it make sense to use 4.1?
Xen 4.1 is a very recent package on pkgsrc, and the other alternative
(pkg) is
Hello,
NetBSD -current dom0
FreeBSD 8.2-STABLE domU.
Trying to ssh to the VM produces the error in the subject line on the
FreeBSD domU; It's impossible to login.
I found a few references in google, but nothing conclusive.
___
freebsd-xen@freebsd.org
On 05/24/11 17:16, Sean Bruno wrote:
I've made some significant progress on the freebsd.org xen hosting
machines (no dom0 support yet, but I'm working on it).
I've installed a netbsd-current dom0 and the 3.3.2 xen hypervisor on
xen1.freebsd.org and started up a freebsd-current DomU with the
On 05/24/11 14:45, Hugo Silva wrote:
Trying to ssh to the VM produces the error in the subject line on the
FreeBSD domU; It's impossible to login.
Some more information for those looking to reproduce this: the above is
with rxcsum and txcsum disabled in the xn interface: Without that, the
ssh
Hello,
Just as the subject says.
dom0 is NetBSD 5.99.49/Xen 3.3.2 and domU is FreeBSD 8.2-STABLE (same
happens with -RELEASE).
If I create a FreeBSD VM and use file:, XENHVM will boot to completion.
If I vnconfig that same file, then it will hang. On lvm storage it will
also hang.
So it seems
Ivan Voras wrote:
Hello,
Is anyone using FreeBSD on Citrix XenServer 5.6? Which version, i386
or amd64? Is it reliable?
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to
Ivan Voras wrote:
On 18 February 2011 15:06, Hugo Silva h...@barafranca.com wrote:
Performance seems to be acceptable. There's a gotcha with PF, which someone
else mentioned in this list recently. One has to disable tcp.tso to get
decent throughput.
Disabling it enabled a colleague who
Carsten Heesch wrote:
Athough I seem to be talking to myself here, I have good news for RC2!
It works!
Just did an freebsd-update -R 8.0-RC2 upgrade. Both GENERIC and
XENHVM kernels work without any problems.
Maybe somebody else can chime in an confirm that, too? Probably good
for the
22 matches
Mail list logo