Timeline for Virtualbox does not create snapshots from remote virtual disks
Current License: CC BY-SA 4.0
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2023 at 14:50 | vote | accept | martixy | ||
| May 22, 2023 at 14:46 | comment | added | martixy | I can, it seems. The manager is obnoxiously finicky with switching disks (if they're all named the same), but otherwise now there's no problem. 😁 | |
| May 22, 2023 at 14:30 | answer | added | Yisroel Tech | timeline score: 1 | |
| May 22, 2023 at 14:25 | comment | added | Yisroel Tech | Not sure it's a real answer... With the new VM created, can you now "mix and match"? In the old VM machine, maybe you messed manually with the config to try to have the snapshots and VM/VDI on different locations? | |
| May 22, 2023 at 14:19 | comment | added | martixy | I mean I could boot up from local virtual disks from multiple drives (as I said in the question I was considering whether it wanted the vdi on the same drive as the VM, but that turned out to not be the case). And since you spoke of details mattering - note that it had a problem with snapshots from remote locations. It was perfectly happy creating a snapshot of any vdi on a local drive. As for the solution - does that not go in an answer? (Tho admittedly we still do not know the root cause.) | |
| May 22, 2023 at 14:14 | history | edited | martixy | CC BY-SA 4.0 |
More info, I guess?
|
| May 22, 2023 at 14:08 | comment | added | Yisroel Tech | I am not sure what you really mean by "mix and match local VDIs", my suspicion that something was wrong with that VM in the first place (some config change in it that isn't correct) and therefore the snapshots on it were having issues. | |
| May 22, 2023 at 14:06 | comment | added | Yisroel Tech | I was talking about the info like that you tried creating it in CLI and it said Snapshot taken, or that creating it from fresh does work. While they are answers to my picking your brain... they're relevant details to your question for someone to be able to try to answer it, so always Edit them in to your question. | |
| May 22, 2023 at 13:56 | comment | added | martixy | I had not tried that. But that seems to resolve the problem. Also, I'm not sure what info you're talking about. I included everything that's not just me confirming things already said. But thank you for the help. Never would have guess that recreating the machine would have something to do with it, given that I can mix and match local vdis with ease. Perhaps it really is a bug? | |
| May 22, 2023 at 13:36 | comment | added | Yisroel Tech | Please add the additional info to the question instead of (only) having them in the comments. Maybe it's some config issue with the particular machine you have there. Have you tried creating a new VM from fresh on the network drive and do a snapshot on it? | |
| May 22, 2023 at 13:31 | comment | added | martixy | "Snapshot taken". And yes. | |
| May 22, 2023 at 13:27 | comment | added | Yisroel Tech | "Snapshot created" or "Snapshot taken"? (Details matter very much when trying to figure out an issue.) And does it show a UUID after that? | |
| May 22, 2023 at 13:26 | comment | added | martixy | I must admit, I have never been asked "Are you sure?" so many times before. Tho if you were looking for an error in the terminal, none appears. Just says "Snapshot taken". But we do get the same error in the log file. | |
| May 22, 2023 at 13:16 | comment | added | Yisroel Tech |
Another way to maybe get a better immediate error reading, try creating the snapshot from the command line utility, by running (open command prompt or change directory to C:\Program Files\Oracle\VirtualBox) VBoxManage snapshot <uuid|vmname> take <snapshot-name> (e.g. VBoxManage snapshot "My VM Name" take test_snapshots)
|
|
| May 22, 2023 at 13:13 | comment | added | martixy | Yes. @YisroelTech | |
| May 22, 2023 at 13:10 | comment | added | Yisroel Tech | Are you sure this error is from when (trying to be) creating the snapshot? It's off but the state issue doesn't make sense to be related (as being Powered Off is the perfect state for a snapshot.) | |
| May 22, 2023 at 13:06 | comment | added | martixy | Interesting. So far vbox has been more than happy to yell at me for every error, so it did not occur to me to look for the logs. For some reason this one is silently ignored. It's not often you run into a situation where google returns less than 20 results. :) None of them are helpful either. | |
| May 22, 2023 at 12:55 | history | edited | martixy | CC BY-SA 4.0 |
Logs!
|
| May 22, 2023 at 12:37 | comment | added | Yisroel Tech |
What are the logs saying? Try to take the snapshot and then copy/check the log VBoxSVC.log from %UserProfile%\.VirtualBox folder (on Windows)
|
|
| May 22, 2023 at 12:17 | history | edited | martixy | CC BY-SA 4.0 |
More info
|
| May 22, 2023 at 12:15 | comment | added | Ramhound | @martixy - You should edit your question to clarify it instead of submitting a comment | |
| May 22, 2023 at 12:10 | comment | added | martixy |
Entirely and sadly @YisroelTech. (Well it does put some random .nvram file in there, but no snapshot.)
|
|
| May 22, 2023 at 12:06 | comment | added | Yisroel Tech | "There is no snapshot taken" when going to Snapshots on the VM it's empty? | |
| May 22, 2023 at 11:40 | history | asked | martixy | CC BY-SA 4.0 |