Hi all !
I''ve been playing with Xen 4.0.1 from tarball together with 2.6.37 as
dom0 and
have a problem - I am able to see Xen boot messages and dom0 ones on console but
have no interaction with getty after dom0 finish booting. I''ve probably
missed
something in GRUB configuration. Here is what I have now :
......
kernel /boot/xen4.0.gz console=vga vga=mode-0x0f00,keep
module /boot/vmlinuz-2.6.37xen root=/dev/sda5 ro console=hvc0 console=tty0
With that conf I would like to have boot messages (Xen + dom0) visible and
ability to log on. Am I thinking right ?
Maybe I should set something while compiling Xen itself or dom0 kernel ?
Cheers,
Balan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi all !
I''ve been playing with Xen 4.0.1 from tarball together with 2.6.37 as
dom0 and
have a problem - I am able to see Xen boot messages and dom0 ones on console but
have no interaction with getty after dom0 finish booting. I''ve probably
missed
something in GRUB configuration. Here is what I have now :
......
kernel /boot/xen4.0.gz console=vga vga=mode-0x0f00,keep
module /boot/vmlinuz-2.6.37xen root=/dev/sda5 ro console=hvc0 console=tty0
With that conf I would like to have boot messages (Xen + dom0) visible and
ability to log on. Am I thinking right ?
Without all these xen and kernel console stuff I get blank screen as soon as
dom0 start booting.
Maybe I should set something while compiling Xen itself or dom0 kernel ?
Cheers,
Balan
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Mike Viau
2011-Jan-14 14:31 UTC
RE: [Xen-users] Re: Xen 4.0.1 + 2.6.37 missing input from console
> On Fri, 14 Jan 2011 04:26:44 -0800 <a_balandis@yahoo.com> wrote: > > Hi all ! > > I''ve been playing with Xen 4.0.1 from tarball together with 2.6.37 as dom0 and > have a problem - I am able to see Xen boot messages and dom0 ones on console but > > have no interaction with getty after dom0 finish booting. I''ve probably missed > something in GRUB configuration. Here is what I have now : > > ...... > kernel /boot/xen4.0.gz console=vga vga=mode-0x0f00,keep > module /boot/vmlinuz-2.6.37xen root=/dev/sda5 ro console=hvc0 console=tty0 > > With that conf I would like to have boot messages (Xen + dom0) visible and > ability to log on. Am I thinking right ? > Without all these xen and kernel console stuff I get blank screen as soon as > dom0 start booting. > > Maybe I should set something while compiling Xen itself or dom0 kernel ? >What video card does your system use? You can try adding nomodeset to your kernel line that begins with module so, module /boot/vmlinuz-2.6.37xen root=/dev/sda5 ro console=hvc0 console=tty0 nomodeset -M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Mike, Thanks for your involvement. I have NVidia Quadro NVS140M (Thinkpad T61p). I''ve just tried "nomodeset" and unfortunately it doesn''t help. Do you have any other clues ? Maybe I missed something when I was compiling the kernel (or hypervisor) ? Strange that dom0 does output nothing to console without mentioned extra kernel parameters. Cheers -- View this message in context: http://xen.1045712.n5.nabble.com/Re-Xen-4-0-1-2-6-37-missing-input-from-console-tp3341230p3341733.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike Viau
2011-Jan-14 18:38 UTC
RE: [Xen-users] Re: Xen 4.0.1 + 2.6.37 missing input from console
> On Fri, 14 Jan 2011 10:26:10 -0800 <a_balandis@yahoo.com> wrote: > > Thanks for your involvement. I have NVidia Quadro NVS140M (Thinkpad T61p). > I''ve just tried "nomodeset" and unfortunately it doesn''t help.It appears you are using a laptop based on your video card which also happens to be the same one I am using. Perhaps you could post your lspci -vvv -s 01:00.0 output to be certain. If this is the case the kernel at: http://xenbits.xen.org/people/ianc/2.6.32-29+xen0/ works perfectly for native (bare-metal) and dom0 operation as well.> > Do you have any other clues ? Maybe I missed something when I was compiling > the kernel (or hypervisor) ? > Strange that dom0 does output nothing to console without mentioned extra > kernel parameters. >I am not aware of the intricate details (perhaps a developer could elaborate) of what these ''extra'' kernel parameters so in the kernel code, but there was an entire page created on the subject so work was done to make this work. http://wiki.xensource.com/xenwiki/XenPVOPSDRM -M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here is output from lspci :
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad T61
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at d6000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at d4000000 (64-bit, non-prefetchable) [size=32M]
Region 5: I/O ports at 2000 [size=128]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [78] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
<512ns, L1 <4us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1,
Latency L0 <512ns, L1 <4us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM L0s Enabled; RCB 128 bytes Disabled- Retrain-
CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Virtual Channel <?>
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information <?>
Kernel driver in use: nvidia''s
Kernel modules: nvidia
It''s generated from the same vmlinuz-2.6.37xen kernel but run on
bare-metal.
I will try suggested 2.6.32. Before I''ve used Lenny''s Xen
3.2.1 + 2.6.26 and
everything works perfectly. Now it''s time to try 2.6.32 with 4.0.1.
I haven''t seen that wiki doc before so I must read it up.
Cheers
--
View this message in context:
http://xen.1045712.n5.nabble.com/Re-Xen-4-0-1-2-6-37-missing-input-from-console-tp3341230p3341837.html
Sent from the Xen - User mailing list archive at Nabble.com.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Mike Viau
2011-Jan-14 20:25 UTC
RE: [Xen-users] Re: Xen 4.0.1 + 2.6.37 missing input from console
> On Fri, 14 Jan 2011 11:52:57 -0800 <a_balandis@yahoo.com> wrote: > > > Here is output from lspci : > > 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev > a1) (prog-if 00 [VGA controller]) > Subsystem: Lenovo ThinkPad T61 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 16 > Region 0: Memory at d6000000 (32-bit, non-prefetchable) [size=16M] > Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M] > Region 3: Memory at d4000000 (64-bit, non-prefetchable) [size=32M] > Region 5: I/O ports at 2000 [size=128] > Capabilities: [60] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ > Queue=0/0 Enable- > Address: 0000000000000000 Data: 0000 > Capabilities: [78] Express (v1) Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s > <512ns, L1 <4us > ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- > Unsupported- > RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- > TransPend- > LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, > Latency L0 <512ns, L1 <4us > ClockPM- Suprise- LLActRep- BwNot- > LnkCtl: ASPM L0s Enabled; RCB 128 bytes Disabled- Retrain- > CommClk+ > ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- > LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ > DLActive- BWMgmt- ABWMgmt- > Capabilities: [100] Virtual Channel <?> > Capabilities: [128] Power Budgeting <?> > Capabilities: [600] Vendor Specific Information <?> > Kernel driver in use: nvidia''s > Kernel modules: nvidia > > It''s generated from the same vmlinuz-2.6.37xen kernel but run on bare-metal.Thats ok. Our outputs are slightly different but that is because I assume you did not run the command as root or with sudo. Regardless I am almost certain are video hardware is identical. Therefor I am confident that perticular 2.6.32 kernel with 4.0.1 will work for you (fingers crossed). -M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I tried 2.6.32 package and it works out-of-the-box with 4.0.1. Though there are no extra parameters added either to hypervisor or dom0 GRUB configuration, they both display booting messages on console and getty finally attaches to tty. All that let me think that something is wrong with my 2.6.37 configuration - console (terminal) driver, settings, etc. When I cope with this issue I will let know. Thanks for help ! -- View this message in context: http://xen.1045712.n5.nabble.com/Re-Xen-4-0-1-2-6-37-missing-input-from-console-tp3341230p3342457.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users