similar to: domU only booting with extra = ''xencons=tty1''

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

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

After startup of the DomU with xm create mydomu.cfg ­c The startup always stops, when starting the Cron-Daemon. [ 1.810477] EXT3 FS on xvda1, internal journal Loading kernel modules...done. Cleaning up ifupdown.... Setting up networking.... Activating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 done. Mounting local filesystems...done. Activating swapfile

Hi Pasi, if I don''t change the tty to hvc it will stopped on Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root Kernel 2.6.31.13 on i686 (console) localhost login: root After I change it to hvc0 followed the twiki page the log is Remounting root filesystem in read-write mode: [ OK ] Mounting local filesystems: [ OK

I just installed xen-linux-system-2.6.26-1-xen-amd64 2.6.26-7 on a freshly installed Debian Lenny AMD64 system, and when I create a Debian Lenny DomU with xen-tools I cannot attach to a console nor log in with SSH. When running # xm create -c test.cfg the system starts booting, but it seems to "freeze" after the kernel has booted. Googling a bit, shows that I seem to have the problem

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 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''m using VNC to show vm''s linux boot. I see lines like [ 1.053298] EXT3-fs: INFO: recovery required on readonly filesystem. [ 1.053686] EXT3-fs: write access will be enabled during recovery. [ 1.494490] kjournald starting. Commit interval 5 seconds etc. But à the end of booting, it stop. No prompt login. With "xm console vm" I have the boot login. I

Hello everyone, I''m quite a newbie with Xen and I''m currently having an issue. I run Xen 4 on Debian Squeeze x64 and I''m trying to build an OpenFiler DomU from the Xen domU filesystem tarbal they provide (See http://www.openfiler.com/community/download/). I downloaded the tarball and run ''tar xzpvf /root/soft/openfiler-2.3-x86_64.tar.gz'' to extract

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

I am trying to get a CentOS 6.3 serial console to work with IPMI SOL. I think I have everything working but maybe the wrong baud rate on the getty: $ ipmitool -I lanplus -U root -H 10.0.0.14 sol activate Password: [SOL Session operational. Use ~? for help] ?????????? 10.0.0.14 is the DRAC IP address of the CentOS 6.3 box. It accepts the password and connects me to the console but then when I

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

I followed the book called "Professional Xen Virtualization" written by William von Hagen,and published by Wiley Publishing,Inc. Here are some configuration files: #cat /xen/ubuntu/ubuntu.xen3.cfg kernel = "/boot/vmlinuz-2.6.18-128.1.16.el5xen" ramdisk = "/boot/initrd-2.6.18-128.1.16.el5xen-no-scsi.img" memory = "512" name = "Ubuntu804" vif =

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 Everyone, In the guest image I download from stacklet, a Ubuntu 10.04 x86_64 DomU, in /var/log/auth.log, I see: /dev/hvc0: No such file or directory listed a lot of times. I''m not experiencing any problems, however it makes looking through logs for auditing purposes a bit annoying. Any ideas what this is? I think it has something to do with the "Hypervisor Console",

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

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 All... I have installed xen 3.3. I m running a Virtual Machine using an image file that has fedora 8 installed in it. When i view the Virtual Machine using VNC Viewer or on the browser using tight vnc,there appears 2 pointers .I need to solve this problem. Kindly suggecst me the correct solution. Waiting for responses. -- Thanks and Regards Anitha

Hi Fi, cmdline: console=hvc0 systemd.wants=getty at hvc0 Connect via virt-manager - View / Text Consoles / Text Console no.: Fedora 24 (Rawhide) Kernel 4.3.0-0.rc3.git2.4.fc24.x86_64 on an x86_64 (hvc0) localhost login: root Last login: Fri Oct 2 17:28:36 on hvc0 # tty /dev/hvc0 # systemctl status getty at hvc0.service ? getty at hvc0.service - Getty on hvc0 Loaded: loaded