Log Server install using OVA file under Xenserver 7.2
Posted: Mon Oct 22, 2018 12:05 pm
Wanted to try out Log server last week as I am retiring a machine
that has been used as a syslog server off and on for a few years.
We run Xenserver here, 7.2 and I grabbed the latest VMWare image of Log Server
and installed it via Import feature of XenCenter.
I have not used this feature very often, only two other times and they were
for Xen images directly.
The import failed twice, and I think left behind two 100G disk allocations, but
that was on me for not going through the setup correctly with network info
on the initial import.
At any rate Log server is installed, but when doing a normal boot it drops to dracut
shell, but booting to the Rescue image it boots up fine. I think due to the way the file
system is referenced as dmesg shows that references to hda need to be changed to xvda.
Thing is the rescue image boots and shows /dev/xvda1 as /boot.
I don't know how to fix this one yet, and am unsure if it is fixable, or if I should just spin
up a new CentOS image and install LS from scratch and not waste my time with dracut.
Anyone seen this before or know if this is fixable? Or not bother?
Thanks,
Keith
that has been used as a syslog server off and on for a few years.
We run Xenserver here, 7.2 and I grabbed the latest VMWare image of Log Server
and installed it via Import feature of XenCenter.
I have not used this feature very often, only two other times and they were
for Xen images directly.
The import failed twice, and I think left behind two 100G disk allocations, but
that was on me for not going through the setup correctly with network info
on the initial import.
At any rate Log server is installed, but when doing a normal boot it drops to dracut
shell, but booting to the Rescue image it boots up fine. I think due to the way the file
system is referenced as dmesg shows that references to hda need to be changed to xvda.
Thing is the rescue image boots and shows /dev/xvda1 as /boot.
I don't know how to fix this one yet, and am unsure if it is fixable, or if I should just spin
up a new CentOS image and install LS from scratch and not waste my time with dracut.
Anyone seen this before or know if this is fixable? Or not bother?
Thanks,
Keith