similar to: DomU console appears to hang when starting

I installed xen 3.3.0 on a etch box from sources. I just modified the standard kernel cause of some hardware drivers. I installed xen-tools from backports (3.9-3~bpo40+1). To create a domU ist not the problem. I can connect via ssh and everything works fine. But when i start a domU with "xm create host.example.tld.cfg -c" to login to console from domU it hangs after the message

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: >

I''m running Xen 3.2 on Debian 5.0 (Lenny) and am having trouble booting up a Debian Etch DomU. It hangs at the end when it says "Starting periodic command scheduler: cron." It''s just completely frozen. At one point I set it sit for a few hours and got back into the console and it said something about "time went backwards" but I used the

Hello xen-users ! I am coming for help concerning the just released 4.0 version. Install has worked rather well on my Debian Lenny. I have just had a few bugs for which I have found the answer looking around on this list. I have created a Debian Lenny domU which boots up just fine. The only problem is that I am unable to get a console prompt when using "xm console nameofdomU". I do see

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

Hi, I have already set up a VM that can access the network using the NAT mode. The problem I have is that I''d like to create another VM that also has access to the network. The problem I get is that when a VM is started, the other one will refuse to start. Actually it starts, but when I want to "xm console" into it I get the following error message: "xenconsole: Could not

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

Hi, I was a server running Fedora 6. I want to migrate it to Xen on a Centos 5.1. Can I make something like dd if=/dev/sdaX of=fedora6.img (on FC6) and then on Centos 5.1 dd if=fedora6.img of=/dev/sdaX Could I run this system into Xen? Thanks in advance! -- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

Hi, I''m running Xen 4 on Slack64. I haven''t console login prompt to domU until I changed xvc0 to hvc0 on /etc/inittab file. No I have access to login but whenever I try to login I get this error from /var/adm/secure file root@darkstar:/var/adm# cat secure Apr 28 22:49:22 darkstar login[1286]: ILLEGAL ROOT LOGIN on `hvc0'' Apr 28 22:49:45 darkstar last message repeated

Hi, I keep seeing references to "xvda" in and around xen forums and postings.....what exactly is xvda (yes I''ve googled it and found no explanation)? Thanks M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

The following patches add RHEL 6 guest support to virt-v2v. This was actually quite a lot easier than I expected. * [PATCH 1/4] Update virt-v2v.conf for RHEL 6 virtio support * [PATCH 2/4] Check kudzu exists before attempting to disable it * [PATCH 3/4] Use dracut rather than mkinitrd if it's available * [PATCH 4/4] Properly convert RHEL 6 guest console

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

Hi All, I was hoping to pick someone''s brain about the best way of moving a Xen disk image (which has LVM''s inside of it) to a new block-device?  I have the target DRBD device ready but unsure what''s the best & safest way to do it. I was actually tempted to mount the Xen disk image in a dom0, and make it visible via loop devices and promote that DRBD node for

Hello everybody! My server with Ubuntu Hardy Heron x64 with Xen 3.2 hangs on when booting at "Starting local boot scripts (/etc/rc.local)". My /etc/rc.local is default and I can''t find out why it stops there. It''s possible to SSH to the server and everything works fine. I just can''t do anything from the physical server. I''ve googled but nothing have

Hi, I've tried to setup a new DomU on Lenny and I'm a little bit confused on which device names I should use for disks and console in the various DomU-kernels? Is it correct that: 2.6.18-xen-kernel from Etch start with no "extra" tty1 in /etc/inittab /dev/sd for disks 2.6.26-xen-kernel from Lenny: start with no "extra" hvc0 in /etc/inittab /dev/xvd for disks

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

Hello, I have been using Xen on a Debian Lenny server for quite some time. I decided to build a new Dom0 using identical hardware, but newest version of Xen from repositories with Debian Squeeze. I attempting to create a new DomU on the new host which is similar to an existing DomU running on the older Lenny host. The DomU is a three NIC firewall. Two of the NICs are virtualized. One NIC is a

Hello everyone: When i starting a linux domU, i get the error message: "xenconsole: Could not read tty from store: No such file or directory" #xm create -c /etc/xen/fc6.cfg Using config file ... ....... xenconsole: Could not read tty from store: No such file or directory ----------------- #xm list Name ID Mem VCPUs State Time(s) Domain-0 0 251

Hello All, After a few months of hiatus, we have resumed working on mips port of Xen. We are at the point of booting dom0 userland (init process and its children). The init process gets spawned and in turn forks off processes to run commands in /etc/rc.d/init.d/rcS. However, the getty process does not seem to run subsequently and hence the login prompt is not displayed. Dom 0 does not use the

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all