similar to: 2.6.25: xm console doesn''t work: "XENBUS: Device with no driver: device/console/0"

Hello, my name is Viktor. I use kernel-2.6.38.5 as dom0. I can''t get access to console dom0. There is a blank screen after xen-4.1.0.gz loading. But dom0 is loaded and I have got it from ssh and it works fine. I just see nothing at monitor screen. Why? May be I have error in my grub.conf settings, please help! My video card: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series]

Hi, I am writing a small doc for people new to Xen. to be able to compile Xen from sources on Ubuntu. Please suggest some improvements for this how to or mistakes that you can point out. There is a technique of virtualization known as Xen and a hypervisor known as Xen. Like you have Firefox,Open Office,VLC and other softwares on your computer similary there is a software known as Xen.

Hi I''m putting together a Dom0 and three DomU (all Gentoo) with kernel 3.5.7 and Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0 works fine so far, however, I''m stuck trying to create DomUs. It appears the xvda1 device on DomU is not created or accessible: Parsing config file dom1 domainbuilder: detail: xc_dom_allocate:

I have ported the development code of the open source ChromiumOS project to 64-bit. Google Chrome OS will be officially released in late 2010, and it will be based on the Chromium OS project. My 64-bit build of ChromiumOS is called ChromiumOS64. The project is hosted at http://www.chromiumos64.org/ The current kernel configuration for ChromiumOS64 is as follows: CONFIG_XEN=y

I have ported the development code of the open source ChromiumOS project to 64-bit. Google Chrome OS will be officially released in late 2010, and it will be based on the Chromium OS project. My 64-bit build of ChromiumOS is called ChromiumOS64. The project is hosted at http://www.chromiumos64.org/ The current kernel configuration for ChromiumOS64 is as follows: CONFIG_XEN=y

Here is my output: Console: colour dummy device 80x25 console [tty0] console [hvc0] installing Xen timer for CPU 0 Detected 1806.840 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 3613.68 BogoMIPS (lpj=7227360) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line) Apic siabled by BIOS Grant table initialized NET: Registering protocol

Hi, Looks like this patch broke automated builds due to a lack of a matching line in the defconfigs. Below is a patch that makes this a module for xen and xen0, unconfigured for xenU. That might not be the best thing here however. Thanks kurt Signed-off-by: Kurt Hackel <kurt.hackel@oracle.com> ===================================================== diff -r cd744c5ec950

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1. However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU can not boot with tapdisk. I am wondering it is something related to the blktap driver. *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot process hanged at a prompt: XENBUS:

# HG changeset patch # User fujita.tomonori@lab.ntt.co.jp # Node ID 7111077b493ea53ef055ce38098f8af67f87d749 # Parent ed8d345449c176cb5fe0ccff4299da782eb63c08 SCSI frontend and backend drivers'' common Makefile and header Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> diff -r ed8d345449c1 -r 7111077b493e buildconfigs/linux-defconfig_xen0_x86_32 ---

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

[root@localhost onkar]# which xend /usr/sbin/xend [root@localhost onkar]# uname -a Linux localhost.localdomain 2.6.31.12 #1 SMP Wed Mar 31 09:51:44 IST 2010 i686 i686 i386 GNU/Linux [root@localhost onkar]# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend",

I have two Xen 3.0.2 domains, both are using network-bridge, both servers are in the same network. dom0_A, domU_A - first Xen server (dom0 and domU) dom0_B, domU_B - first Xen server (dom0 and domU) I cannot ping or connect from one dom0_A to dom0_B nor domU_B. arping works fine though. I can ping and connect from domU_A to dom0_B and domU_B, though. I have changed

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am new to XEN. Try to move from vmware and Virtualbox (I use both now). Unfortunately, Debian Squeeze no longer support xen (out of the box no dom0) So I am trying to make it myself. I have installed xen 3.4.2 from source, did make world and installed. Got the kernel source from from the git repository with the xen patches following the xen

Use the compiler to verify printf formats and arguments. Fix fallout. Signed-off-by: Joe Perches <joe at perches.com> --- drivers/block/xen-blkback/xenbus.c | 2 +- include/xen/hvc-console.h | 4 +++- include/xen/xenbus.h | 2 ++ 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/block/xen-blkback/xenbus.c

Use the compiler to verify printf formats and arguments. Fix fallout. Signed-off-by: Joe Perches <joe at perches.com> --- drivers/block/xen-blkback/xenbus.c | 2 +- include/xen/hvc-console.h | 4 +++- include/xen/xenbus.h | 2 ++ 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/block/xen-blkback/xenbus.c

Use the compiler to verify printf formats and arguments. Fix fallout. Signed-off-by: Joe Perches <joe at perches.com> --- drivers/block/xen-blkback/xenbus.c | 2 +- include/xen/hvc-console.h | 4 +++- include/xen/xenbus.h | 2 ++ 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/block/xen-blkback/xenbus.c

Hi, I''m trying to run Xen 3.0 on my amd64 UP machine. So far xen0 is working fine but there is a problem with mounting rootfs on xenU kernel. Is there something else that needs to be compiled into xenU 3.0 kernel? $ grep XEN kernel-xenU-x86_64-3.0.config CONFIG_XEN=y CONFIG_ARCH_XEN=y # XEN # CONFIG_XEN_PRIVILEGED_GUEST is not set # CONFIG_XEN_PHYSDEV_ACCESS is not set