similar to: Tinc not starting but not complaining either

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, Dom0 = Debian_Base (192.168.0.1) DomU = Debian_SQL (192.168.0.2) DomU = Debian_WEB (192.168.0.3) Debian_Base -> Debian_SQL [OK] Debian_Base -> Debian_WEB [OK] Debian_SQL -> Debian_Base [ERROR] Debian_WEB -> Debian_Base [ERROR] Debian_SQL <-> Debian_WEB [ERROR] [ERROR] = ssh "Host key verification failed" Check your entry in /etc/inittab and check this

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

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

Kernel parameters aside (console=ttyUSB0 console=tty0), I am trying to get a login console working on a USB-to-serial adapter. systemctl enable serial-getty at ttyUSB0.service systemctl start serial-getty at ttyUSB0.service This works without issue on Debian 8. However when running the same on CentOS 7, my logs are filled with: May 16 12:44:58 localhost.localdomain systemd[1]: Starting Serial

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

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

hi All, I'm new to this list and also not a professional libvirt user:) I'm trying to use it for running a container. This is my config: <domain type='lxc'> <name>test</name> <uuid>d3667da2-061a-7b20-a29c-3afc798a257e</uuid> <memory>500000</memory> <currentMemory>500000</currentMemory> <vcpu>1</vcpu> <os>

于 2014年07月08日 12:06, Eric Blake 写道: > On 07/07/2014 10:02 PM, Qiang Guan wrote: >> Hi , >> >> Is there anyway to get uuid info inside a lxc container which is created >> by libvirt_lxc? >> >> For kvm, we can use dmidecode or lshw to get this info inside vm. Is >> there any tools >> to do this thing for libvirt lxc? > Per the docs: >

I checked by Alpha this morning after it's been running fine for a while and saw this on the terminal (hand transposed): Jun 14 08:54:55 erwin getty[2087] : getty : retreiving gettytab entry 'default': Device not configured Jun 14 08:54:55 erwin getty[2087] : getty : retreiving gettytab entry 'Pc': Device not configured Jun 14 08:54:55 erwin getty[2087] : getty : retreiving

Hello all, Saturday night, after a couple of shots of bourbon, I realized that I had an old PC sitting in the garage that I could use as an Asterisk gateway if I just blew the dust off it and reloaded it with a modern Linux distribution. In my characteristically impulsive manner, I grabbed it and started cleaning it up so that I could put it in my office without my wife having a fit. The

Thanks for these explanations - it all makes sense, that is, the default behavior for a process that does not capture SIGQUIT is to quit and perform a core dump (https://en.wikipedia.org/wiki/Unix_signal#SIGQUIT). Then the remaining question, as Luke says, is: should R handle this signal? For instance, in interactive mode, SIGQUIT could maybe bring up: Possible actions: 1: abort (with core

Hello List, how much run should i give xen0 if the only service that runs is sshd ? ~# free              total       used       free     shared    buffers     cached Mem:        127032     124952       2080          0       7776      89688 -/+ buffers/cache:      27488      99544 Swap:      1048816          0    1048816 Tasks:  33 total,   2 running,  31 sleeping,   0 stopped,   0 zombie

Dear "someone who can help", I am having a problem with SAMBA and SWAT (although I'm not sure SWAT is part of the problem...) I get two instances of "smbd" when ever it is started on this system. From SWAT I can only stop it ONE time. After that, each time I attempt to stop the SMBD daemon from SWAT it simply starts TWO more instances of the daemon (or something

This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS but the symptoms are identical. Try 'systemctl enable console-getty.service' then 'systemctl start console-getty.service' or, if it is headless (serial console only), 'systemctl enable serial-getty at ttyS0.service' then 'systemctl start serial-getty at ttyS0.service' assuming it's

I did try other console and it did not work. I did go from 6.7 to 6.8 but with centos not redhat. On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) < robert.styma at nokia.com> wrote: > Try another console like ALT-F2. See if you have a black screen login > prompt. I opened a bug with RedHat for a system that when I went from 6.7 > to 6.8 booted but would not start

Hi, We have a pretty serious problem with our news server crashing during the expire cronjob. This happened with 4.7-RELEASE, so we upgraded to 4.8-RELEASE recently, hoping that the problem might be fixed, but it isn't. The machine is a Compaq DL360-G2. I've searched the PR database as well as the mailing list archives for the panic string, but didn't find anything. What makes the

Hello, I''ve got a problem to get a serial output on grub, xen, linux-xen0 and getty. The serial works fine with grub, xen and linux-xen0, but I''m unable to start a console, where I''m able to login. I dont''t get any output. If I change only the getty from ttyS0 to ttyS1 than I''m able to login.. At the attachment you can see what I see through a serial,

I can't seem to get my serial terminal to work with my new system. I had a serial terminal connected to my old system that worked great and copied /boot.config, /boot/loader.conf and /etc/ttys settings over from it. The new system has a Gigabyte GA970A-UD3 board with just a serial header on the board. I bought a serial connector backplate in an electronics store and connected it to the