2:31 p.m.
Hi virt, im stumped... any help would be appreciated.
I normally create my VMs like this:
base="http://mirror.pnl.gov/fedora/linux/releases/20/Fedora/x86_64/o...
sudo virt-install --hvm --name $vm_name$i --ram 4000 \
--disk path=/VirtualMachines/$vm_name$i,size=30 \
--location $base -x "ks=http://xxx.os21.ks$kx"
HOWEVER... I'm finding that my VMs dont boot after i restart the Host.
My question is: Where is virt-install writing the boot disk to?
I get a error message that the "boot failed" because the hard disk, is
not a bootable disk.
But I can't imagine where else to boot from ? Because I point
my --location of the original boot to the source code repo itself....
ANY help would be appreciated thanks!
3:02 a.m.
Jay Vyas <jayunit100(a)gmail.com> writes:
Hi virt, im stumped... any help would be appreciated.
I normally create my VMs like this:
base="http://mirror.pnl.gov/fedora/linux/releases/20/Fedora/x86_64/o...
sudo virt-install --hvm --name $vm_name$i --ram 4000 \
--disk path=/VirtualMachines/$vm_name$i,size=30 \
--location $base -x "ks=http://xxx.os21.ks$kx"
HOWEVER... I'm finding that my VMs dont boot after i restart the Host.
My question is: Where is virt-install writing the boot disk to?
I don't see anything wrong in your command line and it should just work.
How does your kickstart file look like? And your domain XML definition
(you can get it with "virsh dumpxml $vm_name$i")?
Regards,
Giuseppe
4:24 a.m.
Hi Giuseppe and thanks for the response............ Heres some more info:
Here is my kickstart... maybe the "--bootloader" argument is wrong in some
way?
# Put this in pastebin or some other public url
# Kickstart file automatically generated by anaconda.
#version=DEVEL
install
cdrom
lang en_US.UTF-8
keyboard us
network --onboot yes --device eth0 --bootproto dhcp --noipv6
timezone --utc America/New_York
rootpw --iscrypted
$6$9bRPXTZZMy0FNl2A$lgY.MS3pZ.0PVg4o3AQeJOydPwGVphdKT07tHlJUmdoRTz4UQQ/L54ny0QHkdubMquqkr4jw37DxmM0FL5kRn1
selinux --enforcing
authconfig --enableshadow --passalgo=sha512
firewall --service=ssh
#Disable graphical stuff
skipx
#text
# 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
Some more details: This is what my "df" output is
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup-lv_root
26552588 2244364 22959412 9% /
tmpfs 1978444 0 1978444 0% /dev/shm
/dev/sda1 495844 33710 436534 8% /boot
On Tue, Apr 22, 2014 at 4:02 AM, Giuseppe Scrivano <gscrivan(a)redhat.com>wrote:
Jay Vyas <jayunit100(a)gmail.com> writes:
> Hi virt, im stumped... any help would be appreciated.
>
> I normally create my VMs like this:
>
> base="http://mirror.pnl.gov/fedora/linux/releases/20/Fedora/x86_64/o...
>
> sudo virt-install --hvm --name $vm_name$i --ram 4000 \
> --disk path=/VirtualMachines/$vm_name$i,size=30 \
> --location $base -x "ks=http://xxx.os21.ks$kx"
>
> HOWEVER... I'm finding that my VMs dont boot after i restart the Host.
>
> My question is: Where is virt-install writing the boot disk to?
I don't see anything wrong in your command line and it should just work.
How does your kickstart file look like? And your domain XML definition
(you can get it with "virsh dumpxml $vm_name$i")?
Regards,
Giuseppe
--
Jay Vyas
http://jayunit100.blogspot.com
4:50 a.m.
Jay Vyas <jayunit100(a)gmail.com> writes:
# 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
in the kickstart file generated by libosinfo for Fedora 20
(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
4:53 a.m.
Hi Giuseppe... ! Thanks for the hint. ill try it.
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 option part biosboot --fstype=biosboot --size=1.
However, in the case that a disk has an existing biosboot partition, adding
a "part biosboot" option is unnecessary."
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 ?
On Tue, Apr 22, 2014 at 5:50 AM, Giuseppe Scrivano <gscrivan(a)redhat.com>wrote:
Jay Vyas <jayunit100(a)gmail.com> writes:
> # 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
in the kickstart file generated by libosinfo for Fedora 20
(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
5:06 a.m.
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(a)gmail.com> wrote:
Hi Giuseppe... ! Thanks for the hint. ill try it.
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 option part biosboot --fstype=biosboot --size=1.
However, in the case that a disk has an existing biosboot partition, adding
a "part biosboot" option is unnecessary."
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 ?
On Tue, Apr 22, 2014 at 5:50 AM, Giuseppe Scrivano <gscrivan(a)redhat.com>wrote:
> Jay Vyas <jayunit100(a)gmail.com> writes:
>
> > # 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
>
> in the kickstart file generated by libosinfo for Fedora 20
> (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
--
Jay Vyas
http://jayunit100.blogspot.com
3870
days inactive
3874
days old
5 comments
2 participants
participants (2)
-
Giuseppe Scrivano -
Jay Vyas