I tracked this down, eventually. Under RHEL/CentOS 7.2, the rootfs was
limited to the size of available memory. Under 7.3, there's an
artificial restriction of 50% of total system memory. The default size
of a VM under "virt-manager" is 1G, which creates a ~500MB rootfs in the
installer.
> I just tried a kickstart setup for the first time since 7.3 and got an
> error similar to the error in this unresolved Fedora bug report:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1278260
>
> Has anyone successfully done a kickstart setup using 7.3 on x86_64?
I have with an http based ks
From: John Doe jd...@yahoo.com
4. OT: fs corruption ont he USB keys...
I copy the iso file on the key (no error message), then compare it to the
original and some random differences appear.
I have corruption problems with both the i386 (3.7GB) and x86_64 (4.2GB) DVD
iso files.
But I
From: Fabian Arrotin fabian.arro...@arrfab.net
John Doe wrote:
I am creating CentOS install usb keys and, apart from a few problems, it
mostly works...
1. OT: My server HP does not seem to want to boot on it if I set the write
protection on.
2. Anaconda tries to fetch the ks.cfg too
From: John Doe jd...@yahoo.com
4. OT: fs corruption ont he USB keys...
I copy the iso file on the key (no error message), then compare it to the
original and
some random differences appear. I noticed in the logs:
ext2_new_block: Allocating block in system zone - block = 65536
John Doe wrote:
Hi,
I am creating CentOS install usb keys and, apart from a few problems, it
mostly works...
1. OT: My server HP does not seem to want to boot on it if I set the write
protection on.
2. Anaconda tries to fetch the ks.cfg too early... It detects sda, then
detects the
Paolo Supino wrote / napísal(a):
On Wed, Sep 3, 2008 at 5:52 PM, Marco Fretz [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
hi,
we had the same problem with newer HP pcs and servers (broadcom nics).
pxe works well on broadcom, the install not. doesn't matter if you're
Paolo Supino wrote / napísal(a):
On Thu, Sep 4, 2008 at 8:27 AM, Romeo Ninov [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Paolo Supino wrote / napísal(a):
On Wed, Sep 3, 2008 at 5:52 PM, Marco Fretz
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Paolo Supino wrote:
On the other hand if you were right about it than RHEL/CentOS/Fedora
installation would be unsuitable in any multihome configuration
because it would map ETH devices differently (albeit once in a while)
which means one whould have to swtich the cables because of network
On Thu, Sep 4, 2008 at 9:52 AM, Romeo Ninov [EMAIL PROTECTED] wrote:
Paolo, this problem occur only in RHEL/CentOS/other RH based distros and not
in Slack, SuSE, Debian, etc. I was not going deeper in the problem, but that
is the reality. BTW: You can play with MAC address in incfg files, but
I've /never/ seen RHEL/CentOS or any of its predecessors renumber
ethernet ports on a working system..
Yeah, I have never seen it renumber either?
I've seen it number them
backwards, such that eth0 was the port labeled '1' outside the chassis
and eth1 was port '0', but it was extremely
John R Pierce wrote:
Paolo Supino wrote:
On the other hand if you were right about it than RHEL/CentOS/Fedora
installation would be unsuitable in any multihome configuration
because it would map ETH devices differently (albeit once in a while)
which means one whould have to swtich the
On Thursday 04 September 2008 18:04:49 MHR wrote:
If you can take the time to scroll down to the bottom of an email to
answer it properly (i.e., bottom post), then you can trim it on the
way down. If your email automatically bottom-posts, then I guess you
just need to do some courtesy
On Thu, 2008-09-04 at 18:51 +0100, Anne Wilson wrote:
In addition, if you use kmail highlighting the section that you want
to reply
to will give you a clean start with only the appropriate bit copied,
like
this :-) It doesn't work if you need to intersperse many comments,
but where
On Thursday 04 September 2008 20:02:25 William L. Maltby wrote:
On Thu, 2008-09-04 at 18:51 +0100, Anne Wilson wrote:
In addition, if you use kmail highlighting the section that you want
to reply
to will give you a clean start with only the appropriate bit copied,
like
this :-) It
On Tue, Sep 2, 2008 at 8:44 PM, Richard Karhuse [EMAIL PROTECTED] wrote:
On 9/2/08, Paolo Supino [EMAIL PROTECTED] wrote:
:
Hi Joseph
After sending the last reply I fixed the kickstart config files and
added --boot=yes to the network statement of eth0, but going through the
hi,
we had the same problem with newer HP pcs and servers (broadcom nics).
pxe works well on broadcom, the install not. doesn't matter if you're
using kickstart or manual install.
the problem was in centos 4.2. after updating the install environment to
4.5 the problem was gone... so it was a
On Wed, Sep 3, 2008 at 5:52 PM, Marco Fretz [EMAIL PROTECTED] wrote:
hi,
we had the same problem with newer HP pcs and servers (broadcom nics).
pxe works well on broadcom, the install not. doesn't matter if you're
using kickstart or manual install.
the problem was in centos 4.2. after
Paolo Supino wrote:
The situation got me so aggravated that I was contemplating resurrecting
my old private distro (not going to do that) that does things in a much
simpler way.
I'm virtually certain it's not using the NIC you think it is,
try the other NICs, and find out which NIC maps to
This is a VERY common problem. I see it all the time.
I also can confirm this *very* typical behavior.
Paolo,
Remind me what the issue is that prevents you from working through
this based on the known existence? Its been muddied somewhere through
the thread...
jlc
On Wed, Sep 3, 2008 at 11:47 PM, nate [EMAIL PROTECTED] wrote:
Paolo Supino wrote:
The situation got me so aggravated that I was contemplating
resurrecting
my old private distro (not going to do that) that does things in a much
simpler way.
I'm virtually certain it's not using the
On Wed, Sep 3, 2008 at 11:49 PM, Joseph L. Casale [EMAIL PROTECTED]
wrote:
This is a VERY common problem. I see it all the time.
I also can confirm this *very* typical behavior.
Paolo,
Remind me what the issue is that prevents you from working through
this based on the known existence?
Paolo Supino wrote:
Hi Nate
3: After the error comes up I get the HTTP setup configuration screen with
the source website (in IP) and CentOS directory as I entered them in the
pxeconfiguration file and as it appears in the kickstart configuration file
and all I have to do is press the 'OK'
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] wrote:
Paolo Supino wrote:
Hi Nate
3: After the error comes up I get the HTTP setup configuration screen
with
the source website (in IP) and CentOS directory as I entered them in the
pxeconfiguration file and as it appears in the
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] wrote:
Paolo Supino wrote:
Hi Nate
3: After the error comes up I get the HTTP setup configuration screen
with
the source website (in IP) and CentOS directory as I entered them in the
pxeconfiguration file and as it appears in the
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Paolo Supino wrote:
Hi Nate
3: After the error comes up I get the HTTP setup configuration
screen with
the source website (in IP) and
On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED] wrote:
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] mailto:
[EMAIL PROTECTED] wrote:
Paolo Supino wrote:
Hi Nate
3: After the error comes up I get the HTTP setup
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
mailto:[EMAIL
On Tue, Sep 2, 2008 at 3:07 PM, Romeo Ninov [EMAIL PROTECTED] wrote:
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED] mailto:
[EMAIL PROTECTED] wrote:
Paolo Supino wrote / napísal(a):
On Tue, Sep 2, 2008 at 8:14 AM, nate
Network autoconfiguration failed, most likely there is not
a compatible driver for the network card in your system.
Paolo,
You are using multihomed systems, I remember a problem with pxe booting
whereby the install switched to the wrong nic and setup may fail as a result.
How are you statring
On Tue, Sep 2, 2008 at 4:01 PM, Joseph L. Casale
[EMAIL PROTECTED]wrote:
Network autoconfiguration failed, most likely there is not
a compatible driver for the network card in your system.
Paolo,
You are using multihomed systems, I remember a problem with pxe booting
whereby the install
WHat do you mean?
Do you boot from one of the NICS, or a CD, or what?
If you boot from a NIC via a TFTP server, you may be encountering the issue
I describe which simply needs a kernel arg to fix you up.
jlc
___
CentOS mailing list
CentOS@centos.org
On Tue, Sep 2, 2008 at 4:18 PM, Joseph L. Casale
[EMAIL PROTECTED]wrote:
WHat do you mean?
Do you boot from one of the NICS, or a CD, or what?
If you boot from a NIC via a TFTP server, you may be encountering the issue
I describe which simply needs a kernel arg to fix you up.
jlc
Paolo Supino wrote:
I boot via NIC0 and my configurations are as follows:
pxe (for node3):
Just to rule it out try plugging in all NICs to the same
switch/VLAN and kickstart again and see if it works better.
Sometimes the NIC detected as eth0 at PXE time is not the
same NIC as at
I boot via NIC0 and my configurations are as follows:
Yeah, that's what I thought.
Have a look at:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html
http://kbase.redhat.com/faq/FAQ_80_531.shtm
The latter might shed some light. I am thinking you
On Tue, Sep 2, 2008 at 5:04 PM, nate [EMAIL PROTECTED] wrote:
Paolo Supino wrote:
I boot via NIC0 and my configurations are as follows:
pxe (for node3):
Just to rule it out try plugging in all NICs to the same
switch/VLAN and kickstart again and see if it works better.
Sometimes the
On Tue, Sep 2, 2008 at 5:10 PM, Joseph L. Casale
[EMAIL PROTECTED]wrote:
I boot via NIC0 and my configurations are as follows:
Yeah, that's what I thought.
Have a look at:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html
Paolo Supino wrote:
It's a nice thing and I thought of doing it, but it's impractical and here
is why: I have 42 systems in this cabinet. Each system as 4 NICs and I only
have 1 48 port switch. If I had the additional switches to stack I would
have done it a long time ago (and I would have
On Tue, Sep 2, 2008 at 5:10 PM, Joseph L. Casale
[EMAIL PROTECTED]wrote:
I boot via NIC0 and my configurations are as follows:
Yeah, that's what I thought.
Have a look at:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html
On 9/2/08, Paolo Supino [EMAIL PROTECTED] wrote:
:
Hi Joseph
After sending the last reply I fixed the kickstart config files and
added --boot=yes to the network statement of eth0, but going through the
consoles of each of the systems to see if the installation completed
successfully I
Paolo Supino wrote:
Has anyone encounter this problem and has a solution for it?
Network autoconfiguration failed, most likely there is not
a compatible driver for the network card in your system.
If there is a driver disk for that NIC you can use that, what
I typically have done in the past
Hi Nate
Autoconfiguration failure makes sense, but it's not a drivers issue:
1: It's a broadcom tg3 driver that is well supported in the kernel.
2: the kernel fetches successfully the kickstart configuration file I supply
it in the command line and
3: After the error comes up I get the HTTP
42 matches
Mail list logo
