search for: hvc0

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 2 times Apr 28 23:04...

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

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", whatever that is? Could it b...

...uot; on a fresh install because I don't like > boot > > messages being hidden from me, and now this other thing does it. I like > > details, I need the details, don't hide them from me. > > I feel the same way about 'rhgb quiet'. :-) > > The 'console=hvc0' setting doesn't hide them from you, it just sends > them somewhere you're not looking. > I'm looking at the system's console during installation. Sending it somewhere else is hiding it from me. > On bare metal, the console output can typically go two places: > 1....

...ating the system, rebooting, then trying to install Xen4CentOS it would fail to boot into the 4.9 kernel, sitting there with a blinking cursor indefinitely. I thought it was a failure with grub, but it turns out this was set in the grub config: GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 ..." So the kernel was loading successfully, but it was failing boot properly (hanging because it couldn't find the / file system, but that's a different story). Boot messages were not being displayed on my console because of the console=hvc0 setting, hampering the troubleshooting pro...

> This is what's defined in /etc/default/grub following the install of the > Xen: > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 > console=com1,tty loglvl=all guest_loglvl=all" > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > nomodeset" > > I didn't set these myself, this is what the xen package (or one of its > dependencies) is doing. > > I'm still not clear on why hvc0 is needed, or why it's being set, but what > I do know for sure is it was causing the boot me...

...fined in /etc/default/grub following the install of the > > Xen: > > > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo > com1=115200,8n1 > > console=com1,tty loglvl=all guest_loglvl=all" > > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > > nomodeset" > > > > I didn't set these myself, this is what the xen package (or one of its > > dependencies) is doing. > > It's the CentOS Xen package setting this. But the Xen option > "console=com1,tty" should make it suc...

...then trying to install Xen4CentOS it would fail to boot into the > 4.9 kernel, sitting there with a blinking cursor indefinitely. > > I thought it was a failure with grub, but it turns out this was set in the > grub config: > > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 ..." > > So the kernel was loading successfully, but it was failing boot properly > (hanging because it couldn't find the / file system, but that's a different > story). Boot messages were not being displayed on my console because of the > console=hvc0 setting, hampering...

...fined in /etc/default/grub following the install of the > > Xen: > > > > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo > com1=115200,8n1 > > console=com1,tty loglvl=all guest_loglvl=all" > > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen > > nomodeset" > > > > I didn't set these myself, this is what the xen package (or one of its > > dependencies) is doing. > > > > I'm still not clear on why hvc0 is needed, or why it's being set, but > what > > I do know...

...don't like >> > boot >> > messages being hidden from me, and now this other thing does it. I like >> > details, I need the details, don't hide them from me. >> >> I feel the same way about 'rhgb quiet'. :-) >> >> The 'console=hvc0' setting doesn't hide them from you, it just sends >> them somewhere you're not looking. > > > I'm looking at the system's console during installation. Sending it > somewhere else is hiding it from me. > >> >> On bare metal, the console output ca...

Jerry, Refer to console=hvc0 from (https://wiki.xen.org/wiki/Xen_FAQ_Console)which is dedicated for domO after Xen kernel loaded, so if it hangs it means somewhere the booting process with xen is not right. Suggest you to close look at the dmsg or log for debugging. Hope that helps and cheers. Xlord On Wed, May 17, 2017 at...

...ub following the install of the >> > Xen: >> > >> > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo >> com1=115200,8n1 >> > console=com1,tty loglvl=all guest_loglvl=all" >> > GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 earlyprintk=xen >> > nomodeset" >> > >> > I didn't set these myself, this is what the xen package (or one of its >> > dependencies) is doing. >> >> It's the CentOS Xen package setting this. But the Xen option >> "console=com1,...

...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 pv-ops-kernel from upstream: start with extra="console=hvc0 xencons=hvc0" hvc0 in /etc/inittab /dev/xvd for disks Best Regards, /LM

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 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 ] Enabling /etc/fstab swaps: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Starting system logger: [ OK ] Starting kernel logger: [ OK ] Start...

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

On Wed, 17 May 2017 14:09:57 -0700 Jerry <jerryubi at gmail.com> wrote: > Setting both hvc0 and tty is working as desired. Thanks again to everyone > that replied. I'm updating my kickstart script to include adding > console=tty in addition to the other. Should it be set by default then? Regards, Nerijus

I have this happening in Ubuntu precise also. When I upgraded from 12.04.1 to 12.04.4 it looks like my ipmi/serial/hvc0 console stopped working and the last message is: (XEN) Platform timer is 14.318MHz HPET From /etc/default/grub: GRUB_DEFAULT="Xen 4.1-amd64" GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLI...

...Virt-install, xm create with KS-Install and Converting a working HVM-Install did not suceed. The DomU is making IO, comsumes CPU-Time, but Console and Network are not reachable/working?! XENinified 2.6.34 uses xvc0 as console while pvops-enabled Kernels like the Stock (2.6.30.11) Fedora-Kernel use hvc0. It triple-checked the existence of /dev/hvc0, inittab, securetty but still no Console available Tried following Kernel-Params: extra = ''console=hvc0 earlyprintk=xen'' extra = ''console=hvc0 xencons=tty earlyprintk=xen'' extra = ''console=hvc0 xencons=hvc0...

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