similar to: /dev/tty*: not a character device after reboot

Hi *, as this is my first post I want to say hello to everybody. Well, and unfortunatly I''ve already got a question for you: I''ve installed a guest domain (OS: CentOS 4) on my xen-machine and it''s para-virtualised (just to provide the information ;) ). After the installation and mount the image containing the guest to copy the necessary modules for the xen-kernel,

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)

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

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

Hi, This is my setting: I have a Logical Volume /dev/VG/suse with Suse installed. I have added it to the grub and I can boot it and works perfectly fine. Now I am running /dev/VG/root which is running Xen0. I have created a Xen config file to boot a VM with disk: /dev/VG/suse. In other words I want to boot /dev/VG/suse as a virtual machine. Below is what I am getting at boot time :

Hi all, I installed a paravirt CentOS 5.4 domU on a CentOS 5.4 dom0 environment. I compiled the domU kernel with framebuff console. But I couldn’t using VNC to connect to the domU console. The kernel boot message could print on the vnc console. But after the boot process, the console appears on the text console in dom0 again. The configfile is as follows: vfb = [

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

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 all, my domU guests stop booting in my new 3.2 (kernel 2.6.18.8) xen installation when run perfectly in my other 3.0.2 (2.6.16) xen server. whe i start the domU with "xm create" i get these messages: Using config file "./debian.4-0.xen3.cfg". Started domain debian.4-0 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table

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

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

Hi. Here is the short version: If dom0 experiences a short (< 120 second) network outage the guests whose disks are on iSCSI LUNs get (seemingly) unrecoverable IO errors. Is it possible to make Xen more resiliant to such problems? And now the full version: We''re testing Xen on iSCSI LUNs. The hardware/software configuration is: * Dom0 and guest OS: SLES10 x86_64 * iSCSI LUN on

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

This is slightly off topic since I am all the way upto the login prompt, but I appeal to you all because you probably have experience in this: I am passing a diskless workstation a compressed root filesystem that is copied from a server (chopped down). I am only intereted in text consoles being available on the client (runlevel 3). The diskless workstation goes well up to the login: RedHat

First let me say that I'm not a sysadmin, but am simply wearing that hat this week so please excuse my ignorance. I need to temporarily move some virtual servers from a CentOS-KVM platform to a CentOS-XEN platform while I do some upgrades to the CentOS box. I've created a local LV, and used DD and SCP to transfer the block device from the VKM machine to the XEN machine. For quite a

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

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

hello, I am using 2.6.21, lguest-2.6.21-307.patch.gz and an image from http://uml.nagafix.co.uk/Fedora7/Fedora7-x86-root_fs.bz2 the console hangs, is this expected or caused by the image? I can still ssh to it or if I boot in single user mode the console is available but running init3 and it's hung. also is it possible to get the last gz patch released for 2.6.21?

hello, I am using 2.6.21, lguest-2.6.21-307.patch.gz and an image from http://uml.nagafix.co.uk/Fedora7/Fedora7-x86-root_fs.bz2 the console hangs, is this expected or caused by the image? I can still ssh to it or if I boot in single user mode the console is available but running init3 and it's hung. also is it possible to get the last gz patch released for 2.6.21?

Hi, Trying to get vga console and a serial console to both work. I can get either one to fully work but not both. When using serial, I do still get a login prompt on the vga, But not all the boot up output. Seems like half to the vga and the rest to the serial port I added lines to /etc/inittab # console port T0:12345:respawn:/sbin/agetty -L ttyS0 115200 And added to /etc/lilo.conf