I assume then, that the i386 PV instance cannot do more than 1 CPU at
this time?
sean
Started domain ref8-xen32 (id=120)
WARNING: loader(8) metadata is missing!
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2011 The FreeBSD Project.
On 07/26/11 11:35, Sean Bruno wrote:
I assume then, that the i386 PV instance cannot do more than 1 CPU at
this time?
Correct. SMP support was clearly started but never completed.
I note that if I scale the i386 PV Xen kernel past 855MB, I get an insta
panic at boot. I assume that there's
On Tue, 2011-07-26 at 12:01 -0700, K. Macy wrote:
It's an artifact of the initialization code and how the xen domain
builder configures the initial mapped memory. I've come against this
and fixed this issue in the past but I guess either the domain builder
has changed or the initial code has
Correct, I put much of the infrastructure in place but did not end up
debugging it in to existence.
Cheers
On Tuesday, July 26, 2011, Sean Bruno sean...@yahoo-inc.com wrote:
I assume then, that the i386 PV instance cannot do more than 1 CPU at
this time?
sean
Started domain ref8-xen32
On Tue, 2011-07-26 at 11:58 -0700, Colin Percival wrote:
On 07/26/11 11:35, Sean Bruno wrote:
I assume then, that the i386 PV instance cannot do more than 1 CPU at
this time?
Correct. SMP support was clearly started but never completed.
I note that if I scale the i386 PV Xen kernel
It's an artifact of the initialization code and how the xen domain builder
configures the initial mapped memory. I've come against this and fixed this
issue in the past but I guess either the domain builder has changed or the
initial code has bit rotted. I can't commit so ask Colin if he can fix.
Probably not doing it right. When I switched from pure HVM to PV on the
i386 VMs in the cluster, VNC stopped working all together. Did I do it
wrong?
I've tried the following:
vnc = 1
vncdisplay = 1
vncunused = 1
vncpasswd=''
and
vfb = [ type = vnc, vncdisplay = 1, vncunused = 1,
On 07/26/11 14:48, Sean Bruno wrote:
Probably not doing it right. When I switched from pure HVM to PV on the
i386 VMs in the cluster, VNC stopped working all together. Did I do it
wrong?
Is it possible to use PV with VNC? I thought under PV there wasn't any
emulated console, just the Xen
On Tue, Jul 26, 2011 at 03:04:48PM -0700, Colin Percival wrote:
On 07/26/11 14:48, Sean Bruno wrote:
Probably not doing it right. When I switched from pure HVM to PV on the
i386 VMs in the cluster, VNC stopped working all together. Did I do it
wrong?
Is it possible to use PV with VNC?
On Tue, 2011-07-26 at 15:18 -0700, Luke S. Crawford wrote:
On Tue, Jul 26, 2011 at 03:04:48PM -0700, Colin Percival wrote:
On 07/26/11 14:48, Sean Bruno wrote:
Probably not doing it right. When I switched from pure HVM to PV on the
i386 VMs in the cluster, VNC stopped working all
I can't quite tell what's happening (perhaps its ntpd and Xen something
here), but this appears on the VM console about every 10 seconds.
[XEN] hypervisor wallclock nudged; nudging TOD.
[XEN] hypervisor wallclock nudged; nudging TOD.
if the system is completely idle, I see:
26 Jul 15:56:02
I think that sort of makes sense to me. That is, there would need to be
a PV framebuffer driver for PV mode to use it. I guess.
Someone(TM) just needs to port the driver. FBs are fairly trivial to
support.
Cheers
Sean
___
I'm almost done building a test reference system in the Yahoo portion of
the FreeBSD cluster. Nothing special, but I'm trying to get you folks
some testing resources that are capable of being used for testing and
development of Xen.
The emails I'm sending are just the bits of things that I'm
13 matches
Mail list logo
