On Wed, May 17, 2017 at 2:17 PM, Nerijus Baliunas <
neri...@users.sourceforge.net> wrote:
> On Wed, 17 May 2017 14:09:57 -0700 Jerry wrote:
>
> > Setting both hvc0 and tty is working as desired. Thanks again to
> everyone
> > that replied. I'm updating my kickstart script
On Wed, 17 May 2017 14:09:57 -0700 Jerry 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?
On Wed, May 17, 2017 at 8:54 AM, Jerry wrote:
>
>
> On Wed, May 17, 2017 at 8:44 AM, George Dunlap wrote:
>
>> On Wed, May 17, 2017 at 4:20 PM, Jerry wrote:
>> > This is what's defined in /etc/default/grub following the install of the
On Wed, May 17, 2017 at 1:45 PM, Sarah Newman wrote:
> On 05/17/2017 01:30 PM, Jerry wrote:
>
> > For some reason each of the 5, 6 & 7 releases have issues with the
> mpt2sas
> > driver (there isn't enough swiotlb allocated by default for the driver to
> > work properly, and the
On 05/17/2017 01:30 PM, Jerry wrote:
> For some reason each of the 5, 6 & 7 releases have issues with the mpt2sas
> driver (there isn't enough swiotlb allocated by default for the driver to
> work properly, and the units for that parameter changed between 5 and 6).
> It's like this driver has bad
On Wed, May 17, 2017 at 10:07 AM, Sarah Newman wrote:
> On 05/16/2017 09:04 PM, Jerry wrote:
>
> >
> > Turns out dracut was unable to mount the root file system. So I went
> back
> > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in
> > its initramfs
On 05/16/2017 09:04 PM, Jerry wrote:
>
> Turns out dracut was unable to mount the root file system. So I went back
> into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in
> its initramfs file... and it wasn't:
>
>
> $ sudo lsinitrd -k 4.9.25-27.el7.x86_64 | grep mpt
>
On Wed, May 17, 2017 at 8:44 AM, George Dunlap wrote:
> On Wed, May 17, 2017 at 4:20 PM, Jerry wrote:
> > 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
>
On Wed, May 17, 2017 at 4:20 PM, Jerry wrote:
> On Wed, May 17, 2017 at 2:39 AM, George Dunlap wrote:
>>
>> On Wed, May 17, 2017 at 4:26 AM, Jerry wrote:
>> > I always disable "rhgb quiet" on a fresh install because I don't like
>> >
On Wed, May 17, 2017 at 08:37:13AM -0700, Jerry wrote:
> On Wed, May 17, 2017 at 8:25 AM, Konrad Rzeszutek Wilk <
> konrad.w...@oracle.com> wrote:
>
> > > This is what's defined in /etc/default/grub following the install of the
> > > Xen:
> > >
> > >
On Wed, May 17, 2017 at 8:25 AM, Konrad Rzeszutek Wilk <
konrad.w...@oracle.com> wrote:
> > 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
> 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"
>
>
On Wed, May 17, 2017 at 2:39 AM, George Dunlap wrote:
> On Wed, May 17, 2017 at 4:26 AM, Jerry wrote:
> > I always disable "rhgb quiet" on a fresh install because I don't like
> boot
> > messages being hidden from me, and now this other thing does it. I
On Wed, May 17, 2017 at 3:02 AM, Mark L Sung wrote:
> 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.
>
I
On Wed, May 17, 2017 at 3:43 AM, PJ Welsh wrote:
> On Tue, May 16, 2017 at 10:26 PM, Jerry wrote:
>
>> Howdy,
>>
>> I recently went through a frustrating experience trying to get Xen 4
>> running on a CentOS 7 system. After a fresh install, fully updating
On Tue, May 16, 2017 at 10:26 PM, Jerry wrote:
> Howdy,
>
> I recently went through a frustrating experience trying to get Xen 4
> running on a CentOS 7 system. After a fresh install, fully updating the
> system, rebooting, then trying to install Xen4CentOS it would fail to
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.
On Tue, May 16, 2017 at 8:21 PM, Sarah Newman wrote:
> Hi,
>
> We were hoping to attend an IRC meeting this morning but it looks like
> that didn't happen. Has this been moved to once a month or was this a
> special week?
>
Hi, we skipeed it yesterday having nothing specific to
18 matches
Mail list logo