similar to: [PATCH] Paravirt framebuffer use xvc as console [4/5]

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187 Signed-off-by: Jeremy Katz

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

[back on list] > > How about one other thing to try first. Have you got a serial > > line connected to the machine? > > I can connect one if needed. Great -- probably easier than writing down the VGA text console. The user manual gives details of how to configure the serial line. > > Have you built from source before? > > Actually I''m building from

Thread stealing is not nice, even if the subject is generic. > Related question - what physical device does /dev/xvc0 refer to? What can > I > connect to get to the agetty running on this device? > xvc0 is a xen virtual console and does not correspond directly to a physical device that I am aware of. Yves-Gaël Chény seemed to have answered the second part of the question: >

Changeset 762:a070228ac76e ("add hvc compatibility mode to xencons" added this call just for the HVC case, without giving any reason why HVC would be special in this regard. Use the call for all cases. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/drivers/xen/console/console.c +++ b/drivers/xen/console/console.c @@ -214,8 +214,6 @@ static int __init xen_console_init(void)

Full_Name: Amos Waterland Version: 2.8.1 OS: Ubuntu Linux Submission from: (NULL) (68.175.8.163) I calculated the covariance for a small data set as follows: X <- c(1,2,3,4) Y <- c(3,3,4,3) cov(X,Y) [1] 0.1666667 But when doing the computation with pencil and paper I get: ((-1.5)*(-0.25) + (-0.5)*(-0.25) + (0.5)*(0.75) + (1.5)*(-0.25))/4 [1] 0.125 Microsoft Excel 2003 covar() also

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Friends, I just installed xen/dom0 on my amd64 quad core phenom processor. dom0 boot up was successfull. When I used ''xm create -c /home/guest.conf'' to create a xen guest, the guest screen hanged after "Starting local". Im not getting the login prompt. Please help me solve this. Im just one step away from a normal guest bootup. My guest fstab,

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hello, I don't have advanced on the NHW Project this past month, but I have definitely validated its characteristics and this new version. The NHW Codec preserves or enhances image neatness and sharpness, which translates that on good quality images the NHW Codec is globally better than HEVC, and on degraded (with blur, artifacts) images it is worse than HEVC because it lacks of precision. I

Hi, Get these now: this one with non-pae builds: arch/i386/kernel/built-in.o: In function `APIC_init_uniprocessor': (.init.text+0x6357): undefined reference to `setup_boot_clock' this on both pae and non-pae (CONFIG_MAGIC_SYSRQ=y): drivers/built-in.o: In function `xencons_rx': (.text+0x17f09): undefined reference to `sysrq_enabled' cheers, Gerd -- Gerd Hoffmann

Hi, Get these now: this one with non-pae builds: arch/i386/kernel/built-in.o: In function `APIC_init_uniprocessor': (.init.text+0x6357): undefined reference to `setup_boot_clock' this on both pae and non-pae (CONFIG_MAGIC_SYSRQ=y): drivers/built-in.o: In function `xencons_rx': (.text+0x17f09): undefined reference to `sysrq_enabled' cheers, Gerd -- Gerd Hoffmann

You're welcome! On Tue, Jul 10, 2018, 4:50 AM Raphael Canut <nhwcodec at gmail.com> wrote: > Hello Dave, > > Thank you very much for your help! > > Cheers, > Raphael > > 2018-07-10 9:39 GMT+02:00 Dave Johnson Games <davefilms.us at gmail.com>: > >> Let me do some looking. >> >> On Mon, Jul 9, 2018, 4:55 PM Raphael Canut <nhwcodec at

Hello, I successfuly run Centos 5.1 domU in Centos 5.1 dom0. But I still have some minor issues/errors/warnings while booting I'd like to fix and here are my questions: 1. How to disable loading usb host controler module: [...from dmesg... ] Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 insmod: error inserting '/lib/uhci-hcd.ko': -1 No such