Cole,
On 2014-05-31 16:31, Cole Robinson wrote:
On 05/30/2014 08:03 PM, Philip Rhoades wrote:
People,
For the last few versions of Fedora (x86_64) I have been going through
this
process:
- install a new SATA drive as /dev/sda
- boot to the previous Fedora now on /dev/sdb
- create a new virtual system using the latest Fedora on the new
physical
drive on /dev/sda
- get the new virtual Fedora on /dev/sda as ready as possible
- then re-boot to the new live system on /dev/sda
This process has been working fine for the last few versions but now
for going
from F19 to F20 and booting on the new F20 the process stops at:
[OK] Reached target Paths
[OK] Reached target Basic System
I can still do a live boot on /dev/sdb and run the new F20 as a virt
machine
using physical drive /dev/sda OK but it was a nice process to reduce
down time
to be able to get the new Fedora as ready as possible as a virtual
machine and
then reboot it as the live machine. Has something changed that stops
me doing
this now?
It's hard to say, there's a lot of variables here. Something is
obviously
going wrong, maybe you can get systemd to give you more debugging info:
http://freedesktop.org/wiki/Software/systemd/Debugging/#index1h1
I would assume it's something to do with some stable /dev disk path
changes
between running in the VM and running on physical hardware, so maybe
poke into
fstab
Someone else pointed to the problem - they had had the same problem with
a straight DVD install where the drive order was automatically changed
for some reason: indeed you were on the right track, the kernel line in
the boot menu had the wrong device name when I switched from a non
virtual boot (the emergency boot line was OK?!), using the UUID of the
drive partition instead fixed the problem.
Thanks!
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: p...@pricom.com.au
_______________________________________________
virt mailing list
virt@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt
