and also, while im at it ... one more detail might be interesting: rebooting the machine works just fine --- only the VMs fail when i reboot the host.
any specific thoughts on that ?On Tue, Apr 22, 2014 at 5:53 AM, Jay Vyas <jayunit100@xxxxxxxxx> wrote:
Hi Giuseppe... ! Thanks for the hint. ill try it.So maybe you are suggesting that, the Kickstart file needs to define the boot info, because im installing from source and not from an ISO ?
So from the docs, I'm seeing this:
"As of Fedora 16 there must be a biosboot partition for the bootloader to be installed successfully onto a disk that contains a GPT/GUID partition table, which includes disks initialized by anaconda. This partition may be created with the kickstart optionpart biosboot --fstype=biosboot --size=1. However, in the case that a disk has an existing biosboot partition, adding a "part biosboot" option is unnecessary."
On Tue, Apr 22, 2014 at 5:50 AM, Giuseppe Scrivano <gscrivan@xxxxxxxxxx> wrote:Jay Vyas <jayunit100@xxxxxxxxx> writes:in the kickstart file generated by libosinfo for Fedora 20
> # The following is the partition information you requested
> # Note that any partitions you deleted are not expressed
> # here so unless you clear all partitions first, this is
> # not guaranteed to work
> # Uncommented by j
> zerombr
> clearpart --all
> autopart
> #ip=192.168.122.99
> network --bootproto=static --ip=192.168.122.100 --netmask=255.255.255.0 --gateway=192.168.122.1 --nameserver=192.168.122.1
> bootloader --location=mbr --timeout=5 --append="rhgb quiet"
> ....
> %end
(osinfo-install-script fedora20), I see this line:
part biosboot --fstype=biosboot --size=1
Could you try adding it to your kickstart file just after "clearpart"?
Giuseppe
--
Jay Vyas
http://jayunit100.blogspot.com
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
