similar to: CentOS 7 kernel console under KVM?

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

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

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

Hi, I''m using Debian 5 (lenny) with Xen 3.2-1. When I try to start a Linux guest (installed with debootstrap like this <http://www.option-c.com/xwiki/Create_a_Debian_VM_with_debootstrap>), the VM hangs right after starting crond. This is exactly before the login prompt (which doesn''t come up). 1) In the internet, the solution is an /extra/ line in the configuration

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

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

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

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

I asked this a few weeks ago but didn''t get a response, so at the risk of being a nag, I''ll abbreviate and restate. I know there are other Xen specific debuggers, but I want to know if there''s any reason why SGI''s kdb, http://oss.sgi.com/projects/kdb, should not be included in a dom0 pv-ops kernel? While the patches apply cleanly and build, the result is that

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 =

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?

Hello! I updated a Xen domU using linux-image-2.6.24-1-xen-686, adapted the Xen configuration (add ``extra = "console=hvc0"'' and use xvdX devices -- where is all this documented, by the way?) and it boots and I can log in via SSH, but I don't get a login session anymore on the domU's Xen console. Is this a known issue? Regards, Thomas -------------- next part

HI, everyone I''m trying to create a paravirtualized domU on Ubuntu 10.04 dom0. I follow Professional Xen Virtualization<http://www.amazon.com/Professional-Xen-Virtualization-William-Hagen/dp/0470138114/ref=sr_1_1?ie=UTF8&qid=1345713852&sr=8-1&keywords=professional+xen+virtualization>, create filesystem image file, clone host''s root filesystem, and create