Re: Linux on EFI systems
By: Android8675 to Khelair on Tue Apr 22 2014 10:15:02
> Care to elaborate on what causes VB to eat drives? I keep a snapshot of my B
> on a network drive, but I'd rather not have to restore my system in the near
> future, if it is in fact a big issue. Running WinXP Guest on Win7/x64 Host,
> also have Debian Wheezy Guest running.
Well, I'm not sure exactly what it is that causes VB to eat the
drives, honestly. I do know that when there are hard crashes, or
anything of the sort, the probability increases to near 100% when a VM
is active, though. I've been able to restore to a recent snapshot
_most_ of the times, but the last couple proved that that isn't a 100%
failsafe, either. The time before last it was a newly installed
machine, no work had gone into configuring it yet, so I didn't really
worry about it, I just reinstalled. The time after that, though, it had
gone through heavy customization and a lot of custom installed software
and the like. I got really bent out of shape about that one, because I
didn't have my incremental backup working right on that machine yet at
the time. So I ended up getting onto the VirtualBox dev mailing lists,
and I was told flat out by them that the snapshots are not meant for
restoring corrupt drive or Virtual Machine images. After that I just
moved my crap to physical hardware and said eff it.
I would really suggest setting up some sort of incremental
backup at least nightly on those VMs, preferably storing backups on a
network drive or something geographically separated (off of the same
physical machine, of course). Next time I really need a virtualization
solution, I'm pretty sure I'm just going to pirate VMWare. I had very,
very few problems with it when I was using it to run a ton of virtual
drives for the infrastructure that I worked at 7 years ago, and it was
reliable enough to pretty much ensure 100% uptime.
-- guh up the effbomb down wif yr bad self
---
■ Synchronet ■ Tinfoil Tetrahedron BBS telnet://bismaninfo.hopto.org:8023/ 1:28
2/1057
|
