I have finally buckled down to learn to make a VM.
Now I probably bit off a bit much.
I am installing from my local repo. For some reason it said this is a test image. My netinst to this notebook did not say that. Something MAY be left over in my repo from the beta.
I then specified the URL of my updates repo. This worked fine both on this notebook and my Asus i386 notebook.
I then selected Xfce desktop and really a minimal set of tools, on 10Gb storage. The install started and for the last ~2 hours it has been sitting at 597/1241 on the install status. The message is installing yum.
I can access my repo server, though I don't see any activity on it.
I have been following the instructions at:
https://fedoraproject.org/wiki/Getting_started_with_virtualization
And am using the GUI virutual manager.
Finally finished. Took a number of hours. And the screen went from 597/1241 message to finished.
On 12/31/2014 11:37 AM, Robert Moskowitz wrote:
I have finally buckled down to learn to make a VM.
Now I probably bit off a bit much.
I am installing from my local repo. For some reason it said this is a test image. My netinst to this notebook did not say that. Something MAY be left over in my repo from the beta.
I then specified the URL of my updates repo. This worked fine both on this notebook and my Asus i386 notebook.
I then selected Xfce desktop and really a minimal set of tools, on 10Gb storage. The install started and for the last ~2 hours it has been sitting at 597/1241 on the install status. The message is installing yum.
I can access my repo server, though I don't see any activity on it.
I have been following the instructions at:
https://fedoraproject.org/wiki/Getting_started_with_virtualization
And am using the GUI virutual manager.
On Wed, 31 Dec 2014 12:44:11 -0500 Robert Moskowitz wrote:
Took a number of hours.
That may be a sign that the disk cache mode isn't set right. I find that "writeback" speeds things up a lot compared to some of the other settings.
On 12/31/2014 12:48 PM, Tom Horsley wrote:
On Wed, 31 Dec 2014 12:44:11 -0500 Robert Moskowitz wrote:
Took a number of hours.
That may be a sign that the disk cache mode isn't set right. I find that "writeback" speeds things up a lot compared to some of the other settings.
Please explain. What is this 'disk cache mode' you speak of? Is it part of the virutal machinery or my base installed OS?
Plus it did its reboot thing, but sat there with a blank screen. Which I cloesed after 15 min sitting there. Then the manager said that the virtual image was running. So I tried to force it to shutdown. But it reported that there was nothing to shutdown. I closed the VM GUI and will wait a bit before I check to see what is happening.
Once I get the VM working, I need to see how to access my base OS's data files. I hope there is an easy access method. It would be a pain if I have to rsync GB into the VM...
On Wed, 31 Dec 2014 12:53:21 -0500 Robert Moskowitz wrote:
Please explain. What is this 'disk cache mode' you speak of? Is it part of the virutal machinery or my base installed OS?
In virt-manager when you look at the VM properties (the light bulb icon), you can select different bits of virtual hardware and fiddle with things like the disk cache mode.
Annoyingly, however, all it ever says when you look at it at first is "default", so you have no clue what the default setting is. I experimented once a long time ago with all the different cache modes, and found writeback much faster than the default (or course, for all I know the default is now better, but I can't tell because I still can't find out what "default" means :-).
-
Robert Moskowitz -
Tom Horsley