Also the scope of word processing is pretty well understood while virtualization is still rapidly evolving. I understand your complaints and I share them. However, we are closer to resolution than you think.
The static validation using XML Schema proved to be very inflexible as we are basically unable to augment the XML file and still use it with a previous version. Also the complicated referencing between the global and the VM XML files make it more likely to corrupt data and harder to fix the corruption.
We will simplify that. We have made good experience with "manual" validation for the upcoming OVF support and we think that is the best solution. This means we will only have to address some of the issues and not the biggest one portability. Somebody familiar with SQLite could actually give it a try and see how it works out. Terry, a couple of things I'd like to add to Achim's comments, which I agree with, for what it's worth.
For one, you seem to worried that we're going to throw away stands-compliant XML parsing. This is not the case. We will continue to use our parsing based on libxml2, which works well.
What doesn't work well is that we throw the VirtualBox XML files against a very strict version-specific XML schema, which makes our XML files dependent on a particular VirtualBox version and requires converting between these versions, which is not backward-compatible. This will need fixing, and we will do this according to the old principle "be liberal in what you accept and strict in what you write. Secondly, using a database does not solve the problems we have.
Also, the problems with atomic commits are independent of whether we use XML or sqlite: we can mess up the consistency either way. A transactional database only guarantees that individual commits are atomic, but for one, we have our doubts about sqlite from past experience, and secondly, we need to fix our data model, not the storage, to make commits atomic. There's one big advantage of using databases, which is why Firefox switched to using sqlite: high-speed random access.
Firefox needs to look through lots and lots of history entries, cookies and bookmarks, which is why I guess they switched. I'm not sure about sqlite and the iPod, but I know my GB iPod has a lot of metadata on it, so I guess sqlite makes a lot of sense there too. But reading, parsing and writing the very small XML files sequentially is clearly not a use case for a database.
Finally, as Achim said, being able to fix issues with a text editor is a huge benefit of using XML. All in all, sqlite can only give us speed, which we don't need. It doesn't fix the problems we need to fix. But we agree on those problems, it seems.
However the physical implementation are quite secondary and entirely your choice, just not something to get into a tizzy about. Also if you are staying with the libxml2 parser, then ignore my related comments. As you point out the major issue here is the logical date model and transaction design, and fixing that.
We should not be separating update and commitment of the central registry and the machine registry by validation steps that can raise errors and get the two out of sync. The main point that I am taking away from this is that the is already aware of these issues and are already planning to address them. This drive then has to be mounted in the VM to be able to save data from testdisk there. How to clonehd the Current State of a disk:.
I used the following simple approach:. Worked well for me. The disk corruption was only hindering boot, there was no data loss in my home folder. Found my corrupt vdi file to be recoverable using 7-Zip , hope this simple method too helps someone. Ubuntu Community Ask! Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Recover files from a broken Virtualbox machine. Asked 7 years, 10 months ago. Active 1 year, 1 month ago. Viewed 52k times. I tried using Windows to clone it, but got an error: I tried the same from the working VM via a shared folder of the USB drive, and it started the cloning.
Any ideas? Improve this question. Takkat, that sounds cool. How can I do that? Takkat, I did it and mounted it using gnome nautilus, but I believe it mounted a two month old version of the machine.
The problem here is not how to recover the disk but how to do it merged with the snapshot. If you try to clone your vdi it would have another uuid an the snapshot will not work with it and you would loose the latest data. I don't use snapshots in a regular basis because I have had corrupted disks in the past and I was able to recover the base disk but lost always the deltas.
I hope someone here gives a good recipe to recover both the base and the delta. This is for next time: never store data on virtual machine, always mount an external drive Try to clone the most recent snapshot, not the original disk.
You should use Vboxmanage clonehd See serverfault. Show 1 more comment. Active Oldest Votes. Of the command line In case we use Ubuntu as a host we can convert our. Choose a directory on your Ubuntu VM's mounted partition s to hold rescued data: Press c to start copying the data from the broken. Notes: In case we can not see our files with the [Quick Search] option in 6. Improve this answer. Community Bot 1. Takkat Takkat k 50 50 gold badges silver badges bronze badges. For the hardware that is older, VirtualBox is a first-rate solution for the process of virtualization.
Note While running the VirtualBox on a machine that has around 2 GB or more RAM, the disk space gets quickly eaten up as well as the memory gets speedily consumed by this VirtualBox, which is a virtualization software; so, one should do it on a hard disk that has 10 GB of space as a minimum to spare.
The RAM was maxed in the past to around 2G. So, there was quite enough memory space for allocating to the Guest OSs.
0コメント