similar to: [PATCH] name the xencons driver

Hi all, I have a question on /etc/inittab for DomU booted with xencons parameter. I saw the following error messages when I appended xencons=ttyS to DomU boot option. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id

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)

Hi, I''m using Debian 5 (lenny) with Xen 3.2-1. When I try to start a Linux guest (installed with debootstrap like this <http://www.option-c.com/xwiki/Create_a_Debian_VM_with_debootstrap>), the VM hangs right after starting crond. This is exactly before the login prompt (which doesn''t come up). 1) In the internet, the solution is an /extra/ line in the configuration

Xen patchbot -unstable wrote: ># HG changeset patch ># User cl349@firebug.cl.cam.ac.uk ># Node ID 8fe8a99b1c2a6ea88624546ab625eaa0758e3a17 ># Parent e69cbfee4011da1648718f1f5cbe8dabb956e72a >New console transport and update xenconsoled. >Add a new console interface using a seperate shared page and event channel >instead of passing the console input/output over control

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. (Should be identical to this patch from last

On 3/8/23 22:45, Richard W.M. Jones wrote: > On Tue, Mar 07, 2023 at 09:40:26PM +0200, Andrey Drobyshev wrote: >> In case when we are injecting virtio-scsi device driver into the guest >> (rather than the default virtio-blk), make sure we write the right PCI ID >> value into the Windows guest registry. This is essential for the guest >> to be bootable afterwards.

There are registry entries that are needed to add some other drivers. Extracting them into a function will help adding SUSE VMDP support. --- v2v/windows_virtio.ml | 311 ++++++++++++++++++++++++++++---------------------- 1 file changed, 176 insertions(+), 135 deletions(-) diff --git a/v2v/windows_virtio.ml b/v2v/windows_virtio.ml index 14ffc51..8a0b529 100644 --- a/v2v/windows_virtio.ml +++

On Tue, Mar 07, 2023 at 09:40:26PM +0200, Andrey Drobyshev wrote: > In case when we are injecting virtio-scsi device driver into the guest > (rather than the default virtio-blk), make sure we write the right PCI ID > value into the Windows guest registry. This is essential for the guest > to be bootable afterwards. > > Originally-by: Roman Kagan <rkagan at virtuozzo.com>

To add this support, the existing code searches for either the viostor or the VMDP (Virtual Machine Driver Pack) files and updates the registry accordingly. Note that VMDP's block driver pvvxblk depends on the ballooning driver pvvxbn. --- v2v/convert_windows.ml | 59 ++++++++++++++++++++------ v2v/windows_virtio.ml | 113 +++++++++++++++++++++++++++++++++++++++++-------- 2 files changed,

In case when we are injecting virtio-scsi device driver into the guest (rather than the default virtio-blk), make sure we write the right PCI ID value into the Windows guest registry. This is essential for the guest to be bootable afterwards. Originally-by: Roman Kagan <rkagan at virtuozzo.com> Signed-off-by: Andrey Drobyshev <andrey.drobyshev at virtuozzo.com> ---

In case when we are injecting virtio-scsi device driver into the guest (rather than the default virtio-blk), make sure we write the right PCI ID value into the Windows guest registry. This is essential for the guest to be bootable afterwards. Originally-by: Roman Kagan <rkagan at virtuozzo.com> Signed-off-by: Andrey Drobyshev <andrey.drobyshev at virtuozzo.com> ---

If virtio-scsi is present among the tools for this version of Windows, prefer it over virtio-blk. Originally-by: Roman Kagan <rkagan at virtuozzo.com> Signed-off-by: Andrey Drobyshev <andrey.drobyshev at virtuozzo.com> --- mlcustomize/inject_virtio_win.ml | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/mlcustomize/inject_virtio_win.ml

On Mon, Nov 02, 2020 at 05:07:59AM +0000, Parav Pandit wrote: > > > > From: Leon Romanovsky <leon at kernel.org> > > Sent: Monday, November 2, 2020 1:46 AM > > > > From: Leon Romanovsky <leonro at nvidia.com> > > > > Remove exposed driver version as it was done in other drivers, so module > > version will work correctly by displaying the

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

To add this support, two things are needed: * make the existing code searches for either the viostor or the SUSE VMDP (Virtual Machine Driver Pack) files. * add a firstboot script setting up VMDP. Note that 2 firstboot scripts are intentionally added for the VMDP setup. This is due to windows potentially rebooting after loading the virtio block driver. It may happen that this reboot

Hello, im struggling with getting a Fedora 11 Domu up and running. My Host is a HP DL380 g6 with CentOS 5.5 and XEN 4 from gitco installed. The System runs several Linux-PV-DomUs like Debian Lenny, Ubuntu Lucid and CentOS-55 without any problems. But if i try to get stock F11 up and running. Using Virt-install, xm create with KS-Install and Converting a working HVM-Install did not suceed. The

I''m running xen 3.0.1 on the 2.6.12-26mdkxen0 mandriva kernel. (x86_64) When I set the serial line using the following configuration, my serial output is truncated as show in http://pastebin.ca/259403 title xen kernel (hd0,0)/xen.gz com1=115200n8 console=com1 xencons=serial module (hd0,0)/vmlinuz-2.6.12-26mdkxen0 root=/dev/sda2 module (hd0,0)/initrd-2.6.12-26mdkxen0.img The system is

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

Hi all: I am pretty new to xen, but ,thanks to you, I am learning fast :) I have a Dell Poweredge 2950 server running Debian Lenny as Dom0 named Asgard I have configured three DomU (Loki, Hermod and Thor) with DHCP support. All the machines (Dom0 and DomU''s) ask for an IP address to a DHCP server in the Office LAN. The DHCP server is configured to bind certain IP addresses to the Dom0

Hi I am trying to migrate an old printserver from one samba4 (4.8.11 on CentOS-6) server to a newer one (4.11.2 on CentOS-8) using net rpc printer migrate all The migration of queue, forms, securitty, settings works, during the migration of the drivers (net rpc printer migrate drivers)? the command dumps core at the first driver Here a level10 output ???? spoolss_AddPrinterDriver: struct