similar to: hvc - hypervisor virtual console & virsh

Hello, When multiple hvc console ports are initialised and used via the virtio_console driver, I can interact with only the first console, the 2nd one doesn't respond. If I call hvc_kick() even if hvc_poll() returns 0, the 2nd console becomes responsive. I've checked that hvc_poll() receives data via get_chars() and feeds it to tty_insert_flip_char(). Any idea what could be going

Hello, When multiple hvc console ports are initialised and used via the virtio_console driver, I can interact with only the first console, the 2nd one doesn't respond. If I call hvc_kick() even if hvc_poll() returns 0, the 2nd console becomes responsive. I've checked that hvc_poll() receives data via get_chars() and feeds it to tty_insert_flip_char(). Any idea what could be going

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

Is there a way to get GRUB2 and the kernel to run a "serial" console under KVM? I'm running a Fedora 20 desktop, with libvirt-managed VMs. When I run a CentOS 6 VM, I can set both the boot loader and kernel up to use ttyS0 and get a console compatible with "virsh console". When I try the same with a CentOS 7 VM, it doesn't work. If I set it to ttyS0, I just

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

All: I''m currently using the older Python-based Xen tools on a cluster of machines, but we''re looking to transition to XCP as the platform of choice for our applications. However, I''ve run into one issue that''s sort of a blocker: paravirtual Linux domUs boot and run, but the console device is strangely broken. Most of the output reaches the connected user (some

Hello. I can''t start Virtual Machine, have the message: Waiting for root file system ... done. Gave up waiting for root device. Common problems ..... ALERT! /dev/xvda2 does not exist. Dropping to a shell! I have installed Xen 4 in a debian squeeze: # uname -a 2.6.32-5-xen-amd64 #1 SMP Wed Jan 12 05:46:49 UTC 2011 x86_64 GNU/Linux xen-hypervisor-4.0-amd64 4.0.1-2

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'm running a Fedora distro kernel (3.13.7-200.fc20.x86_64) in kvm with these options: -chardev null,id=hvc0,signal=off -device virtio-serial-pci -device virtconsole,chardev=hvc0,name=virtme_console -append console=hvc0 console=ttyS0 -nographic (There are more, but these are the interesting ones, I think.) Note that virtio_console is modular, which might be a problem. It blows up like

I'm running a Fedora distro kernel (3.13.7-200.fc20.x86_64) in kvm with these options: -chardev null,id=hvc0,signal=off -device virtio-serial-pci -device virtconsole,chardev=hvc0,name=virtme_console -append console=hvc0 console=ttyS0 -nographic (There are more, but these are the interesting ones, I think.) Note that virtio_console is modular, which might be a problem. It blows up like

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 had a quick try to make it work, but no success thus far. Should it be enough to apply the patch and then boot with "console=/dev/hvc0"? Also, why do you comment out the EARLY_PRINTK stuff in Kconfig? J

I had a quick try to make it work, but no success thus far. Should it be enough to apply the patch and then boot with "console=/dev/hvc0"? Also, why do you comment out the EARLY_PRINTK stuff in Kconfig? J

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

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

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

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

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

Hello, I have installed Ubuntu Interpid in pv domU. It boots fine, but I cannot get any console running. The boot hangs on: * Setting up console font and keymap... [ OK ] * Starting system log daemon... [ OK ] * Starting kernel log daemon... [ OK ] And then nothing happens. My config file looks like that: bootloader = ''/usr/bin/pygrub'' memory = 2048 name =