11:43 a.m.
VirtualBox defaults to using the CDROM/DVD drive which is pretty
worthless unless you have a supply of blanks, I don't have many on hand
presently. I have been trying to make the USB function work without much
success.
Googling suggests group/user problems, I have bobg and root listed as
vboxusers.
The GUI has a USB menu which is always grayed, where I can create a
filter, it recognizes the Sandisk flash drive when entered, I click on
OK and nothing is saved apparently.
Now I've run across something in google that suggests an entry in fstab
may be required?
Has any one worked through this maze who can tell me how to make it work?
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
11:54 a.m.
Am 01.08.2013 18:43, schrieb Bob Goodwin ~ Zuni:
VirtualBox defaults to using the CDROM/DVD drive which is pretty worthless unless you
have a supply of blanks, I
don't have many on hand presently. I have been trying to make the USB function work
without much success.
Googling suggests group/user problems, I have bobg and root listed as vboxusers.
The GUI has a USB menu which is always grayed, where I can create a filter, it recognizes
the Sandisk flash drive
when entered, I click on OK and nothing is saved apparently.
Now I've run across something in google that suggests an entry in fstab may be
required?
Has any one worked through this maze who can tell me how to make it work?
what package?
USB support is simply not available for the OSE version
https://forums.virtualbox.org/viewtopic.php?f=2&t=22174
12:08 p.m.
On 01/08/13 12:54, Reindl Harald wrote:
Am 01.08.2013 18:43, schrieb Bob Goodwin ~ Zuni:
> VirtualBox defaults to using the CDROM/DVD drive which is pretty worthless unless you
have a supply of blanks, I
> don't have many on hand presently. I have been trying to make the USB function
work without much success.
>
> Googling suggests group/user problems, I have bobg and root listed as vboxusers.
> The GUI has a USB menu which is always grayed, where I can create a filter, it
recognizes the Sandisk flash drive
> when entered, I click on OK and nothing is saved apparently.
>
> Now I've run across something in google that suggests an entry in fstab may be
required?
>
> Has any one worked through this maze who can tell me how to make it work?
what package?
USB support is simply not available for the OSE version
https://forums.virtualbox.org/viewtopic.php?f=2&t=22174
Ok, I give up, wont waste any more effort on that then but it really
diminishes the usefulness of VB!
Thanks,
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
12:18 p.m.
On 08/01/2013 07:08 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
On 01/08/13 12:54, Reindl Harald wrote:
>
> Am 01.08.2013 18:43, schrieb Bob Goodwin ~ Zuni:
>> VirtualBox defaults to using the CDROM/DVD drive which is pretty worthless unless
you have a supply of blanks, I
>> don't have many on hand presently. I have been trying to make the USB
function work without much success.
>>
>> Googling suggests group/user problems, I have bobg and root listed as vboxusers.
>> The GUI has a USB menu which is always grayed, where I can create a filter, it
recognizes the Sandisk flash drive
>> when entered, I click on OK and nothing is saved apparently.
>>
>> Now I've run across something in google that suggests an entry in fstab may
be required?
>>
>> Has any one worked through this maze who can tell me how to make it work?
> what package?
> USB support is simply not available for the OSE version
>
> https://forums.virtualbox.org/viewtopic.php?f=2&t=22174
>
Ok, I give up, wont waste any more effort on that then but it really
diminishes the usefulness of VB!
Thanks,
Bob
Did you install the Vbox extension pack? It's needed for USB access,
even in the OSE version!
Joachim Backes
--
Fedora release 19 (Schrödinger’s Cat)
Kernel-3.10.4-300.fc19.x86_64
Joachim Backes <joachim.backes(a)rhrk.uni-kl.de>
https://www-user.rhrk.uni-kl.de/~backes
1:31 p.m.
On 01/08/13 13:18, Joachim Backes wrote:
> Ok, I give up, wont waste any more effort on that then but it
really
> diminishes the usefulness of VB!
>
> Thanks,
>
> Bob
>
Did you install the Vbox extension pack? It's needed for USB access,
even in the OSE version!
Joachim Backes
No, I didn't know it existed. But perhaps there is some way to Install
from the hard drive which would seem more logical? So far all I have
been able to do is install WinXP from a CD. OSX10.5 tries but drives the
cpu to 100% and seems to go nowhere after that.
I have the Fedora 19 DVD iso saved to my NFS. I can't seem to find any
way to make it install from that either short of saving it to a DVD firs
and don't know where to find answers to these questions. Perhaps I don't
have the right key words for Google?
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
1:42 p.m.
Am 01.08.2013 20:31, schrieb Bob Goodwin ~ Zuni:
On 01/08/13 13:18, Joachim Backes wrote:
>> Ok, I give up, wont waste any more effort on that then but it really
>> diminishes the usefulness of VB!
>>
> Did you install the Vbox extension pack? It's needed for USB access, even in the
OSE version!
>
> Joachim Backes
No, I didn't know it existed. But perhaps there is some way to Install from the hard
drive which would seem more
logical? So far all I have been able to do is install WinXP from a CD. OSX10.5 tries but
drives the cpu to 100% and
seems to go nowhere after that.
I have the Fedora 19 DVD iso saved to my NFS. I can't seem to find any way to make it
install from that either
short of saving it to a DVD firs and don't know where to find answers to these
questions. Perhaps I don't have the
right key words for Google?
* insert the iso-image in the virtual CD drive
* select to boot from CD in the *virtual BIOS*
nobody burns iso images to a physical media for use them in any VM
google: "virtualbox CD iso image"
http://www.youtube.com/watch?v=Oobxm02UrBE
5:05 p.m.
On 01/08/13 14:42, Reindl Harald wrote:
* insert the iso-image in the virtual CD drive
* select to boot from CD in the *virtual BIOS*
nobody burns iso images to a physical media for use them in any VM
google: "virtualbox CD iso image"
http://www.youtube.com/watch?v=Oobxm02UrBE
Ok, that was what I needed, the key words, not the youtube clip which is
worthless [my opinion].
But with the right keywords to stimulate Google, "virtualbox CD iso
image" I was able to find an obscure icon with a plus sign under
Settings > Storage that enabled me to choose the .iso file to install.
In this case the F-19 DVD iso. I've got a pretty blue screen with a
digital clock and calendar in the center and nothing else. But that's
progress, I'll wipe it out and start over eventually.
Thanks to all,
Bob
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
1:49 p.m.
Am 01.08.2013 20:31, schrieb Bob Goodwin ~ Zuni, Virginia, USA:
I have the Fedora 19 DVD iso saved to my NFS. I can't seem to find any
way to make it install from that either short of saving it to a DVD
firs and don't know where to find answers to these questions. Perhaps
I don't have the right key words for Google?
Bob
You don't have to burn your Fedora iso to a DVD to make the virtual
machine boot from it. You can add the iso directly as a "DVD" in the
mass storage tab of the virtual box gui, than you can select it as a
boot device (see section 5.9 "CD/DVD support" in the manual).
HTH
1:49 p.m.
On 8/1/2013 2:31 PM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
On 01/08/13 13:18, Joachim Backes wrote:
>> Ok, I give up, wont waste any more effort on that then but it really
>> diminishes the usefulness of VB!
>>
>> Thanks,
>>
>> Bob
>>
>
> Did you install the Vbox extension pack? It's needed for USB access,
> even in the OSE version!
>
> Joachim Backes
No, I didn't know it existed. But perhaps there is some way to Install
from the hard drive which would seem more logical? So far all I have
been able to do is install WinXP from a CD. OSX10.5 tries but drives the
cpu to 100% and seems to go nowhere after that.
I have the Fedora 19 DVD iso saved to my NFS. I can't seem to find any
way to make it install from that either short of saving it to a DVD firs
and don't know where to find answers to these questions. Perhaps I don't
have the right key words for Google?
Bob
The extension file (with the USB support) is available from the
Virtualbox site. The support is left out for those that do not wish to
supply 'free to use by individual' and those zealots (smile) that refuse
to use such software.
It is not complicated. You d/l the file and install it from the VBox
GUI. Then you attach your USB device and configure it (make it known)
again from the Vbox GUI. You can add other USB devices now or later.
After you start your VM and you then 'install' the extension into the
VM. XP will *probably* require a reboot for the driver(s) to be seen by
XP. Really simple.
The DOCS that come with Virtualbox and thee most simple to use with the
most complete directions I have ever seen. I suggest that you take a
look at them. :-)
--
David
1:54 p.m.
On Thu, 1 Aug 2013, Bob Goodwin ~ Zuni, Virginia, USA wrote:
On 01/08/13 12:54, Reindl Harald wrote:
>
> Am 01.08.2013 18:43, schrieb Bob Goodwin ~ Zuni:
>> VirtualBox defaults to using the CDROM/DVD drive which is pretty worthless
>> unless you have a supply of blanks, I
>> don't have many on hand presently. I have been trying to make the USB
>> function work without much success.
>>
>> Googling suggests group/user problems, I have bobg and root listed as
>> vboxusers.
>> The GUI has a USB menu which is always grayed, where I can create a
>> filter, it recognizes the Sandisk flash drive
>> when entered, I click on OK and nothing is saved apparently.
>>
>> Now I've run across something in google that suggests an entry in fstab
>> may be required?
>>
>> Has any one worked through this maze who can tell me how to make it work?
> what package?
> USB support is simply not available for the OSE version
>
> https://forums.virtualbox.org/viewtopic.php?f=2&t=22174
>
Ok, I give up, wont waste any more effort on that then but it really
diminishes the usefulness of VB!
Thanks,
Bob
I can read and write to a flash drive without problems. It worked out of the box for me.
I tried to post a screenshot, but it got held up in moderation. In the old versions of
VirtualBox, USB support was in the "guest additions" package, as I remember,
but I haven't had to install that for some time. I can't remember if you are
using the virtualbox.org package or the one in the repositories, but you may have to
install the exension pack. See: https://www.virtualbox.org/wiki/Downloads. But I gotta
say that I didn't have to do this when I installed it using apper. It just worked out
of the box.
billo
2:02 p.m.
On Thu, 1 Aug 2013, Bill Oliver wrote:
I can read and write to a flash drive without problems. It worked out of the
box for me. I tried to post a screenshot, but it got held up in moderation.
In the old versions of VirtualBox, USB support was in the "guest additions"
package, as I remember, but I haven't had to install that for some time. I
can't remember if you are using the virtualbox.org package or the one in the
repositories, but you may have to install the exension pack. See:
https://www.virtualbox.org/wiki/Downloads. But I gotta say that I didn't
have to do this when I installed it using apper. It just worked out of the
box.
billo
--
One more note. As I've mentioned before, I do a full wipe and installation
periodically on my machines. This can be a hassle if one is left re-installing other
virtual OSs as well. I have found that, with VirtualBox, I can simply back up the
./.VirtualBox directory and the "VirtualBox VMs" directory, and then copy them
back into my home directory after the reinstall of Linux. It works great. That way I
don't waste hours installing two or three operating systems whenever I install the
base Linux. The only problem I've had was a mild graphics incompatibility when moving
from an AMD chipset to an Intel one. That took some surgery to the XP registry, though I
don't remember exactly what I did any more.
Anyway, if you are re-installing XP every time you install Linux, and you don't want
to do it, then there's an easier way.
billo
2:08 p.m.
Am 01.08.2013 21:02, schrieb Bill Oliver:
One more note. As I've mentioned before, I do a full wipe and
installation periodically on my machines. This can
be a hassle if one is left re-installing other virtual OSs as well. I have found that,
with VirtualBox, I can
simply back up the ./.VirtualBox directory and the "VirtualBox VMs" directory,
and then copy them back into my home
directory after the reinstall of Linux
is virtualbox still so poor that you can't have simply all files
related to a VM inside a single directory and need to manage
virtual disks and iso-images that weird way as a few years ago?
[root@srv-rhsoft:~]$ ls /vmware/testserver/
insgesamt 12G
-rwx------ 1 vmware vmware 8,5K 2013-08-01 17:19 config.nvram
-rwx------ 1 vmware vmware 162 2013-03-02 19:53 disks-check.sh
-rwx------ 1 vmware vmware 162 2011-10-01 22:40 disks-defrag.sh
-rwx------ 1 vmware vmware 162 2011-10-01 22:40 disks-shrink.sh
-rwx------ 1 vmware vmware 69M 2013-08-01 17:38 boot.vmdk
-rwx------ 1 vmware vmware 8,2G 2013-08-01 21:04 dune.vmdk
-rwx------ 1 vmware vmware 3,6G 2013-08-01 21:04 system.vmdk
-rwx------ 1 vmware vmware 69 2013-07-29 21:13 config.vmsd
-rwx------ 1 vmware vmware 5,5K 2013-08-01 17:19 config.vmx
-rwx------ 1 vmware vmware 261 2012-06-12 18:48 config.vmxf
the .vmx contains the complete configuration inclduing paths to iso-images
the .nvram are te bios-settings
the vmdk. are virtual disks
[root@srv-rhsoft:~]$ cat /vmware/testserver/config.vmx
#!/usr/bin/vmware
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "9"
displayName = "Testserver"
guestOS = "fedora-64"
nvram = "config.nvram"
extendedConfigFile = "config.vmxf"
bios.forceSetupOnce = "false"
virtualHW.productCompatibility = "hosted"
monitor.virtual_mmu = "hardware"
monitor.virtual_exec = "hardware"
logging = "false"
debug="false"
vcpu.hotadd = "true"
mem.hotadd = "true"
maxvcpus = "8"
numvcpus = "8"
cpuid.coresPerSocket = "1"
sched.cpu.htsharing = "any"
sched.mem.pshare.enable = "false"
memsize = "3072"
MemTrimRate = "0"
MemAllowAutoScaleDown = "true"
prefvmx.minVmMemPct = "75"
mainMem.useNamedFile = "false"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
autostop = "softpoweroff"
debugStub.linuxOffsets =
"0x0,0xffffffff,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0"
uuid.location = "56 4d 63 d6 cb a3 ca 38-79 54 f5 c0 0a 80 78 0e"
uuid.bios = "56 4d 63 d6 cb a3 ca 38-79 54 f5 c0 0a 80 78 0e"
vc.uuid = "52 04 94 e1 76 1a 5b 97-2f fb 22 18 02 d6 8c a5"
vmotion.checkpointFBSize = "134217728"
tools.syncTime = "false"
tools.remindInstall = "false"
tools.upgrade.policy = "useGlobal"
isolation.tools.dnd.disable = "true"
isolation.tools.hgfs.disable = "true"
isolation.tools.copy.disable = "true"
isolation.tools.paste.disable = "true"
isolation.tools.setOption.disable = "true"
isolation.tools.setGUIOptions.enable = "false"
isolation.tools.log.disable = "true"
isolation.tools.diskWiper.disable="false"
isolation.tools.diskShrink.disable="false"
isolation.tools.unity.push.update.disable = "true"
isolation.tools.unity.disable = "true"
isolation.tools.hgfsServerSet.disable = "true"
isolation.tools.memSchedFakeSampleStats.disable = "true"
isolation.tools.getCreds.disable = "true"
guest.command.enabled = "true"
tools.guestlib.enableHostInfo = "false"
vmsafe.enable = "false"
vmxnet.noOprom = "true"
devices.hotplug = "false"
log.rotateSize = "100000"
log.keepOld = "10"
gui.exitOnCLIHLT = "false"
mks.enable3d = "false"
svga.autodetect = "false"
svga.maxWidth = "1024"
svga.maxHeight = "768"
svga.vramSize = "134217728"
scsi0.present = "true"
scsi0.virtualDev = "pvscsi"
scsi0.pciSlotNumber = "224"
scsi0.sasWWID = "50 05 05 66 cb a3 ca 30"
scsi0:0.present = "true"
scsi0:0.fileName = "boot.vmdk"
scsi0:0.redo = ""
scsi0:0.writeThrough = "false"
scsi0:0.allowGuestConnectionControl = "false"
scsi0:1.present = "true"
scsi0:1.fileName = "system.vmdk"
scsi0:1.redo = ""
scsi0:1.writeThrough = "false"
scsi0:1.allowGuestConnectionControl = "false"
scsi0:2.present = "true"
scsi0:2.fileName = "dune.vmdk"
scsi0:2.writeThrough = "false"
scsi0:2.redo = ""
scsi0:2.allowGuestConnectionControl = "false"
ethernet0.present = "true"
ethernet0.startConnected = "true"
ethernet0.connectionType = "custom"
ethernet0.vnet = "/dev/vmnet1"
ethernet0.allowGuestConnectionControl = "false"
ethernet0.virtualDev = "vmxnet3"
ethernet0.features = "1"
ethernet0.wakeOnPcktRcv = "false"
ethernet0.networkName = ""
ethernet0.addressType = "static"
ethernet0.address = "00:0C:29:76:12:E9"
ethernet0.pciSlotNumber = "160"
ethernet0.generatedAddressOffset = "0"
ethernet0.txbw.limit = "-1"
ethernet0.rxbw.limit = "-1"
ethernet0.linkStatePropagation.enable = "false"
ethernet1.present = "true"
ethernet1.startConnected = "true"
ethernet1.connectionType = "nat"
ethernet1.allowGuestConnectionControl = "false"
ethernet1.virtualDev = "vmxnet3"
ethernet1.features = "1"
ethernet1.wakeOnPcktRcv = "false"
ethernet1.networkName = ""
ethernet1.addressType = "static"
ethernet1.address = "00:0C:29:AC:D9:D0"
ethernet1.pciSlotNumber = "192"
ethernet1.generatedAddressOffset = "10"
ethernet1.linkStatePropagation.enable = "false"
pciBridge0.present = "true"
pciBridge4.present = "true"
pciBridge5.present = "true"
pciBridge6.present = "true"
pciBridge7.present = "true"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.functions = "8"
pciBridge6.functions = "8"
pciBridge7.functions = "8"
RemoteDisplay.vnc.enabled = "true"
RemoteDisplay.vnc.port = "5500"
RemoteDisplay.vnc.zlibLevel = "9"
RemoteDisplay.vnc.keymapFile = "/usr/lib/vmware/vnckeymap/de"
RemoteDisplay.vnc.key = "********************"
RemoteDisplay.maxConnections = "2"
checkpoint.vmState = ""
cleanShutdown = "FALSE"
replay.supported = "FALSE"
replay.filename = ""
unity.enableLaunchMenu = "false"
unity.customColor = "|23c0c0c0"
checkpoint.vmState.readOnly = "false"
usb.present = "false"
usb.generic.autoconnect = "false"
usb.pciSlotNumber = "-1"
usb.autoConnect.device0 = ""
usb.autoConnect.device1 = ""
usb.vbluetooth.startConnected = "false"
hpet0.present = "true"
vhv.enable = "true"
ide0:0.present = "true"
ide0:0.fileName = "auto detect"
ide0:0.deviceType = "cdrom-raw"
ide0:0.startConnected = "false"
vhv.hwv8 = "true"
softPowerOff = "FALSE"
vmx.buildType = "release"
vmci0.present = "true"
vmci0.id = "176191502"
vmci0.pciSlotNumber = "32"
scsi0:4.present = "false"
usb:0.present = "false"
usb:1.present = "false"
sound.present = "false"
ehci.present = "false"
floppy0.present = "false"
ide0:0.autodetect = "true"
2:35 p.m.
On Thu, 1 Aug 2013, Reindl Harald wrote:
Am 01.08.2013 21:02, schrieb Bill Oliver:
> One more note. As I've mentioned before, I do a full wipe and installation
periodically on my machines. This can
> be a hassle if one is left re-installing other virtual OSs as well. I have found
that, with VirtualBox, I can
> simply back up the ./.VirtualBox directory and the "VirtualBox VMs"
directory, and then copy them back into my home
> directory after the reinstall of Linux
is virtualbox still so poor that you can't have simply all files
related to a VM inside a single directory and need to manage
virtual disks and iso-images that weird way as a few years ago?
[snip]
I don't understand your complaint -- that there's a config directory *and* a disk
directory? I don't find that an overwhelming burden.
The command "cp -R" doesn't seem to be too onerous a way to transfer stuff
from machine to machine.
billo
2:56 p.m.
Am 01.08.2013 21:35, schrieb Bill Oliver:
On Thu, 1 Aug 2013, Reindl Harald wrote:
> Am 01.08.2013 21:02, schrieb Bill Oliver:
>> One more note. As I've mentioned before, I do a full wipe and installation
periodically on my machines. This can
>> be a hassle if one is left re-installing other virtual OSs as well. I have found
that, with VirtualBox, I can
>> simply back up the ./.VirtualBox directory and the "VirtualBox VMs"
directory, and then copy them back into my home
>> directory after the reinstall of Linux
>
> is virtualbox still so poor that you can't have simply all files
> related to a VM inside a single directory and need to manage
> virtual disks and iso-images that weird way as a few years ago?
>
> [snip]
I don't understand your complaint -- that there's a config directory *and* a disk
directory? I don't find that an
overwhelming burden.
The command "cp -R" doesn't seem to be too onerous a way to transfer stuff
from machine to machine
if you ever work with more than 20 virtual machines on serveral hosts
for testing, development as well as for production you will understand
3:58 p.m.
On Thu, 1 Aug 2013, Reindl Harald wrote:
Am 01.08.2013 21:35, schrieb Bill Oliver:
> On Thu, 1 Aug 2013, Reindl Harald wrote:
>> Am 01.08.2013 21:02, schrieb Bill Oliver:
>>> One more note. As I've mentioned before, I do a full wipe and
installation periodically on my machines. This can
>>> be a hassle if one is left re-installing other virtual OSs as well. I have
found that, with VirtualBox, I can
>>> simply back up the ./.VirtualBox directory and the "VirtualBox VMs"
directory, and then copy them back into my home
>>> directory after the reinstall of Linux
>>
>> is virtualbox still so poor that you can't have simply all files
>> related to a VM inside a single directory and need to manage
>> virtual disks and iso-images that weird way as a few years ago?
>>
>> [snip]
>
> I don't understand your complaint -- that there's a config directory *and* a
disk directory? I don't find that an
> overwhelming burden.
> The command "cp -R" doesn't seem to be too onerous a way to transfer
stuff from machine to machine
if you ever work with more than 20 virtual machines on serveral hosts
for testing, development as well as for production you will understand
Sorry, that's a pretty bullshit answer. Apps should work for the people who use them.
You are right -- it may be that there are all sorts of systems that work better for
people who run ten thousand machines on a thousand servers. I don't care. What I
care about is what suits *my* needs. And Virtualbox works great for me. It usually
installs with minimal hassle (current discussion notwithstanding), and it does what I want
it to do. I don't care about what's the most elegant. I don't care about
what's the most sophisticated solution. I don't care about showing how
technologically savvy a system administrator I am. What I care about is solving a problem
and moving on to more important things as quickly as I can. VirtualBox does that for me:
1) Download app. check
2) Click on icon. check
3) Put in OS disk. check
4) Click on icon. check
5) Drink a beer. check
6) Watch a bearded guy dance with a raccoon on YouTube. check.
7) Move on to next problem. check.
Your response is a little like responding to a post by me saying that I pruned the trees
in my garden, threw the limbs in my little Ford Ranger and hauled the trash to the dump
by arguing that a Mack Terrapro can haul 23,000 lbs of rotting garbage, has a much
sturdier transmission, an indestructable drivetrain and twin trumpet horns. Well, yeah.
Whatever. And if I ever have the need to haul 23,000 lbs of garbage on a regular basis,
and want to see my dog have seizures every time I honk the horn, I'll look into one.
Until then, I'm going to throw my stuff in the back of my Ranger and tool on down to
the landfill happy as I can be.
billo
4:17 p.m.
Am 01.08.2013 22:58, schrieb Bill Oliver:
On Thu, 1 Aug 2013, Reindl Harald wrote:
> Am 01.08.2013 21:35, schrieb Bill Oliver:
>> I don't understand your complaint -- that there's a config directory
*and* a disk directory? I don't find that an
>> overwhelming burden.
>> The command "cp -R" doesn't seem to be too onerous a way to
transfer stuff from machine to machine
>
> if you ever work with more than 20 virtual machines on serveral hosts
> for testing, development as well as for production you will understand
>
Sorry, that's a pretty bullshit answer
if i would gibve such a answer the hell would freeze over again on this list....
Apps should work for the people who use them. You are right -- it
may be
that there are all sorts of systems that work better for people who run ten thousand
machines
on a thousand servers
it works also better with *one* VM because you simply copy *one*
folder for a complete backup
I don't care. What I care about is what suits *my* needs. And
Virtualbox works great for me. It
usually installs with minimal hassle (current discussion notwithstanding)
i saw in the thread with vboxdrv after kernel-updates
while you type simply "vmware" as root and all kernel
modules are built, all services are started and you
are done
don't care about what's the most elegant. I don't care
about what's the most sophisticated solution.
I don't care about showing how technologically savvy a system administrator I am.
What I care
about is solving a problem and moving on to more important things as quickly as I can
mee too, that is why i throw away vbox on my notebook a few years ago
VirtualBox does that for me:
1) Download app. check
2) Click on icon. check
3) Put in OS disk. check
4) Click on icon. check
5) Drink a beer. check
6) Watch a bearded guy dance with a raccoon on YouTube. check.
7) Move on to next problem. check.
VMware doe sexactly the same but better organized
* a virtual machine has properties
* CD/DVD drives and virtual disks are propertys
* you insert a ISO in the properties of the drive
* no delaing with a "media manager"
Your response is a little like responding to a post by me saying that
I pruned the trees in my garden, threw the
limbs in my little Ford Ranger and hauled the trash to the dump by arguing that a Mack
Terrapro can haul 23,000
lbs of rotting garbage, has a much sturdier transmission, an indestructable drivetrain
and twin trumpet horns.
Well, yeah. Whatever. And if I ever have the need to haul 23,000 lbs of garbage on a
regular basis, and want to
see my dog have seizures every time I honk the horn, I'll look into one. Until then,
I'm going to throw my stuff
in the back of my Ranger and tool on down to the landfill happy as I can be
your response sounds like someone wich never saw other virtualization than vbox
and you are pissed off that others call it crap
http://www.phoronix.com/scan.php?page=news_item&px=OTk5Mw
Linux kernel developers have marked Oracle's VirtualBox Linux kernel driver as
"tainted crap" due to the overwhelming number of problems this module has
caused
well, the vmware guest drivers are in the linux upstream kernel....
2:47 p.m.
On 08/01/2013 11:43 AM, Bob Goodwin ~ Zuni, Virginia, USA wrote:
VirtualBox defaults to using the CDROM/DVD drive which is pretty
worthless unless you have a supply of blanks, I don't have many on hand
presently. I have been trying to make the USB function work without much
success.
Googling suggests group/user problems, I have bobg and root listed as
vboxusers.
The GUI has a USB menu which is always grayed, where I can create a
filter, it recognizes the Sandisk flash drive when entered, I click on
OK and nothing is saved apparently.
Now I've run across something in google that suggests an entry in fstab
may be required?
Has any one worked through this maze who can tell me how to make it work?
Bob
Uninstall the version you got from the Fedora repos and install the
version from virtualbox.org. Go to
https://www.virtualbox.org/wiki/Linux_Downloads and scroll down to
RPM-based Linux distributions.
Once you've got it installed, go to
https://www.virtualbox.org/wiki/Downloads and download VirtualBox 4.2.16
Oracle VM VirtualBox Extension Pack. From the Virtual Box GUI, use FILE
-> PREFERENCES to install the extension file you just downloaded.
--
-- Steve
3926
days inactive
3926
days old
16 comments
7 participants
participants (7)
-
Bob Goodwin -
David -
Joachim Backes -
Klaus-Peter Schrage -
Reindl Harald -
SternData -
William Oliver