All: I''m currently using the older Python-based Xen tools on a cluster of machines, but we''re looking to transition to XCP as the platform of choice for our applications. However, I''ve run into one issue that''s sort of a blocker: paravirtual Linux domUs boot and run, but the console device is strangely broken. Most of the output reaches the connected user (some bytes are dropped), but any input is apparently completely lost. The VMs in question work perfectly with the older Xen environment, and as I mentioned, everything else seems to work identically. Is there something I need to do with XCP (we''re currently testing with a mix of 0.5 and 1.0, we''ll be moving totally to 1.0 in the near future, and this happens with both) to make this work right? A change in the domUs? We''re just using ''console=xvc0'' or ''console=hvc0'' as appropriate, and running a normal getty against the console device. Any suggestions would be appreciated, thanks. Regards, -- Derrik Pates demon@now.ai _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Kill all vncterm processes. On 24 June 2011 00:15, Derrik Pates <demon@now.ai> wrote:> All: > > I''m currently using the older Python-based Xen tools on a cluster of > machines, but we''re looking to transition to XCP as the platform of choice > for our applications. However, I''ve run into one issue that''s sort of a > blocker: paravirtual Linux domUs boot and run, but the console device is > strangely broken. Most of the output reaches the connected user (some bytes > are dropped), but any input is apparently completely lost. The VMs in > question work perfectly with the older Xen environment, and as I mentioned, > everything else seems to work identically. Is there something I need to do > with XCP (we''re currently testing with a mix of 0.5 and 1.0, we''ll be moving > totally to 1.0 in the near future, and this happens with both) to make this > work right? A change in the domUs? We''re just using ''console=xvc0'' or > ''console=hvc0'' as appropriate, and running a normal getty against the > console device. Any suggestions would be appreciated, thanks. > > Regards, > > -- > Derrik Pates > demon@now.ai > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> On 24 June 2011 00:15, Derrik Pates <demon@now.ai> wrote: >> >> All: >> I''m currently using the older Python-based Xen tools on a cluster of >> machines, but we''re looking to transition to XCP as the platform of choice >> for our applications. However, I''ve run into one issue that''s sort of a >> blocker: paravirtual Linux domUs boot and run, but the console device is >> strangely broken. Most of the output reaches the connected user (some bytes >> are dropped), but any input is apparently completely lost. The VMs in >> question work perfectly with the older Xen environment, and as I mentioned, >> everything else seems to work identically. Is there something I need to do >> with XCP (we''re currently testing with a mix of 0.5 and 1.0, we''ll be moving >> totally to 1.0 in the near future, and this happens with both) to make this >> work right? A change in the domUs? We''re just using ''console=xvc0'' or >> ''console=hvc0'' as appropriate, and running a normal getty against the >> console device. Any suggestions would be appreciated, thanks.On Thu, Jun 23, 2011 at 7:27 PM, David Markey <admin@dmarkey.com> wrote:> Kill all vncterm processes. >This is actually documented here: http://wiki.xensource.com/xenwiki/Xen_Cloud_Platform%3A_Access_to_VM_console -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users