anyone managed to install F18 or f19 beta under Virtualbox???

[Fernando Cassia]

Attempted 32-bit F18 XFCE install under 64bit Win7 host and Virtualbox
4.2.12 fails at the disk partitioning screen in anaconda with the error
"Failed to save storage configuration".

It seems I have hit the same scenario as this user
http://oxyphosphate3.rssing.com/chan-3353872/all_p101.html

The "solution" of "installing F17 then using FedUp to upgrade to F18" seems
like a bad joke...

If anaconda is broken, has anybody thought about refreshing the
LiveCD/install cd images??

I have also tried F19 beta, and wanted to select manual partitioning
selecting ext2, but Im unable to get past this screen, I cant even click on
existing partitions and select delete... I click and nothing happens...
http://img706.imageshack.us/img706/1414/aey.png

this has to be one of the most brain-damaged installers Ive seen...
FC

[Fernando Cassia]

On Tue, Jun 18, 2013 at 8:10 PM, Fernando Cassia  wrote:
> It seems I have hit the same scenario as this user
> http://oxyphosphate3.rssing.com/chan-3353872/all_p101.html

Sorry, pasted the wrong URL
http://forums.fedoraforum.org/showthread.php?p=1637597#post1637597

FC

[Dan Thurman]

On 06/18/2013 04:15 PM, Fernando Cassia wrote:
> On Tue, Jun 18, 2013 at 8:10 PM, Fernando Cassia <[e-mail]
> > wrote:
> It seems I have hit the same scenario as this user
> http://oxyphosphate3.rssing.com/chan-3353872/all_p101.html
>
>
> Sorry, pasted the wrong URL
> http://forums.fedoraforum.org/showthread.php?p=1637597#post1637597
> FC
>
> During times of Universal Deceit, telling the truth becomes a
> revolutionary act
> Durante épocas de Engaño Universal, decir la verdad se convierte en un
> Acto Revolucionario
> George Orwell

I gave up trying to install F18/9.  The installer is unable
to find and use an existing partition and thinks that
there is no storage space available.

I have yet to get a thumb drive to get around the
installer issue, and I am not sure it will work, considering
I maxed out all of the SATA ports.

Someone posted a step-by-step minimal install by using
a virtual partition and then transfer the contents to your
desired drive partition.

[Fernando Cassia]

On Tue, Jun 18, 2013 at 10:22 PM, Dan Thurman  wrote:
> I gave up trying to install F18/9.  The installer is unable
> to find and use an existing partition and thinks that
> there is no storage space available.

Thanks to everyone who replied. I think Dan is right. The only way I was
able to install (F19 beta) was after I removed all existing partitions...
in fact I removed the previous .vdi altogether and created a new vbox VM
with an empty 6GB .vdi, telling the anaconda to use the whole drive w LVM.

I originally wanted to use classic partitions and ext2 fs but I gave up.
The partitioning GUI in anaconda is borked beyond repair...

FC

[Ed Greshko]

On 06/19/13 12:40, Fernando Cassia wrote:
> On Tue, Jun 18, 2013 at 10:22 PM, Dan Thurman <[e-mail] > wrote:
> I gave up trying to install F18/9.  The installer is unable
> to find and use an existing partition and thinks that
> there is no storage space available.
>
>
> Thanks to everyone who replied. I think Dan is right. The only way I was able to install (F19 beta) was after I removed all existing partitions... in fact I removed the previous .vdi altogether and created a new vbox VM with an empty 6GB .vdi, telling the anaconda to use the whole drive w LVM.
>
> I originally wanted to use classic partitions and ext2 fs but I gave up. The partitioning GUI in anaconda is borked beyond repair...

Is this kind of what you wanted to achieve?

[egreshko@localhost ~]$ df -T
Filesystem     Type     1K-blocks    Used Available Use% Mounted on
/dev/sda2      ext2      23348692 4210604  17952040  19% /
devtmpfs       devtmpfs    631784       0    631784   0% /dev
tmpfs          tmpfs       638828      88    638740   1% /dev/shm
tmpfs          tmpfs       638828     788    638040   1% /run
tmpfs          tmpfs       638828       0    638828   0% /sys/fs/cgroup
tmpfs          tmpfs       638828     100    638728   1% /tmp
/dev/sda3      ext2       5039616   14692   4768924   1% /home
/dev/sda1      ext2        604736   68236    505780  12% /boot
/dev/sda5      ext2       3023760    4512   2865648   1% /opt
[egreshko@localhost ~]$ cat /etc/fedora-release
Fedora release 19 (Schrödinger’s Cat)
[egreshko@localhost ~]$ uname -r
3.9.5-301.fc19.x86_64
[egreshko@localhost ~]$

Found that quite easy to accomplish.....

[Fernando Cassia]

On Wed, Jun 19, 2013 at 2:42 AM, Ed Greshko  wrote:
> Found that quite easy to accomplish.....

oh yes... but the gui refused to cooperate. At one point I managed to
define my own arrangement but upon exiting such screen I got an error
mesage like ""unable to save storage...something". I was too frustrated at
that point so I just gave up.

BTW: F19 took live 5-7 minutes of fiddling to save the new boot record to
the virtual HD before the final reboot.

The VM now shows:

Filesystem              Type      Size  Used Avail Use% Mounted on
/dev/mapper/fedora-root ext4      3.4G  2.4G  832M  75% /
devtmpfs                devtmpfs 1005M     0 1005M   0% /dev
tmpfs                   tmpfs    1009M   72K 1009M   1% /dev/shm
tmpfs                   tmpfs    1009M  708K 1009M   1% /run
tmpfs                   tmpfs    1009M     0 1009M   0% /sys/fs/cgroup
tmpfs                   tmpfs    1009M   32K 1009M   1% /tmp
/dev/sda1               ext4      477M   78M  375M  18% /boot

Since this system runs on a SSD I thought that using ext2 would minimize
writes to the vdi container, compared w other journaling filesystems like
ext3/4...

Remember this is F19 beta as F18 proved impossible to install...
FC

[Joe Zeff]

On 06/18/2013 11:23 PM, Fernando Cassia wrote:
> Since this system runs on a SSD I thought that using ext2 would minimize
> writes to the vdi container, compared w other journaling filesystems
> like ext3/4...

Thank you; I'd been wondering about that.

[Juan Orti Alcaine]

El 2013-06-19 06:40, Fernando Cassia escribió:
> On Tue, Jun 18, 2013 at 10:22 PM, Dan Thurman  wrote:
> > I gave up trying to install F18/9.  The installer is unable
> > to find and use an existing partition and thinks that
> > there is no storage space available.
>
> Thanks to everyone who replied. I think Dan is right. The only way I
> was able to install (F19 beta) was after I removed all existing
> partitions... in fact I removed the previous .vdi altogether and
> created a new vbox VM with an empty 6GB .vdi, telling the anaconda to
> use the whole drive w LVM.

I have installed F19 in VirtualBox without problems, and with existing 
partitions. Just click in "reclaim space" when you are prompted to 
select manual or automatic partitioning.

[Ed Greshko]

On 06/19/13 07:10, Fernando Cassia wrote:
> Attempted 32-bit F18 XFCE install under 64bit Win7 host and Virtualbox 4.2.12 fails at the disk partitioning screen in anaconda with the error "Failed to save storage configuration".

I'm running VirtualBox-4.2-4.2.12_84980 on an F18 host.

I have multiple F18 and F19 VMs installed and running just fine.  I've not yet tried F19-TC5, but I hear there may be problems with it.

[Ed Greshko]

On 06/19/13 09:37, Ed Greshko wrote:
> On 06/19/13 07:10, Fernando Cassia wrote:
> > Attempted 32-bit F18 XFCE install under 64bit Win7 host and Virtualbox 4.2.12 fails at the disk partitioning screen in anaconda with the error "Failed to save storage configuration".
>
> I'm running VirtualBox-4.2-4.2.12_84980 on an F18 host.
>
> I have multiple F18 and F19 VMs installed and running just fine.  I've not yet tried F19-TC5, but I hear there may be problems with it.

F19-TC5 now up and running in a VBox VM.  The only problem with TC5 is if you use netinstall or if you allow updates to be downloaded.  Then you run into an issue with mariadb-server.