Ask your questions here.
Mon Oct 06, 2014 11:00 am
I tested a snapshot after burning it to a DVD, and it works just fine. However, when I test the .iso in qemu, it always goes into kernel panic, unable to mount filesystem. It complains that some configuration is missing.
Any idea?
Mon Oct 06, 2014 3:08 pm
It might help to copy the exact error message you got, but then again, it might not. I gave up using qemu for testing my isos long ago, because I don't have the patience for it - it's way too slow. I build and test in a VM using virtualbox. Some testing gets done by transferring the image to usb and booting on real hardware.
It occurs to me that you might need to tell qemu to enable PAE (if it will even do that.)
Mon Oct 13, 2014 5:06 pm
Sorry for the very delayed answer. I have been very busy.
So, I attach a screenshot. I was having better output before my last snapshot. Now it just ends like this, with the word "panic".
I can issue the command many ways (with the -cdrom option, etc.), but it behaves same:
qemu-system-x86_64 phantom-20141004_1345.iso
I use an amd64 build, so I don't have to enable Pae.
I tried to install Virtualbox under Sid, but unfortunately it's broken.
Mon Oct 13, 2014 6:45 pm
Sorry, but I don't know what any of that output means. To me, it looks like a kernel panic. If you have a wheezy installation, try booting the iso inside that. Maybe qemu is broken in sid right now, too.
Wed Oct 15, 2014 6:49 am
I finally managed to install virtualbox in sid. You have to install virtualbox-dkms explicitly, because it builds the kernel modules. The virtualbox package fails to install virtualbox-dkms properly. Then, you still have to install virtualbox-qt, if you want to have the virtualbox executable. It still gives errors during installation, but after the command "etc/init.d/virtualbox start", it works.
So... same result of qemu in virtualbox. It fails finding the disks. But... I am running it as a live-cd, and if I burn it and run it, it works. Well, I didn't try on another machine. Maybe of another machine it won't find /dev/sdb6 anyway. But doesn't it regenerate etc/fstab? And why does a live-cd need to find physical partitions? Am I using virtualbox wrong or is there a problem with refracta-snapshot? Something wrong with my screenshot, so I cannot add it. Anyway, it drops an initramfs promt.
Wed Oct 15, 2014 7:13 am
Finally, I have the screenshot too. Perhaps it is happening because I user encfs, but anyway it should run straight from the live-cd and not ask for the filesystem.
Wed Oct 15, 2014 9:36 pm
Are you building a snapshot in a system that's installed on an encrypted volume? I've had trouble doing that in the past and didn't spend much time trying to solve it.
Found these regarding ehci-orion. I don't know why you'd need that to boot a virtual CD, but maybe you need to build the initrd and/or the kernel. What kernel are you using?
https://lists.debian.org/debian-kernel/ ... 00009.htmlhttp://forum.doozan.com/read.php?2,13355,13362According to the bug report, the problem should have been fixed a year ago, and when I look at my own hook-functions file, I see ehci-orion listed, but I don't see it in modules.dep inside the initrd (including both the one in the snapshot and the one in the installed system that made the snapshot.)
Thu Oct 16, 2014 7:57 am
Yes, snapshot is from an encrypted volume. It was created just fine. What kind of problems did you experience?
I will have to check the ehci-orion thing. I'm using the latest kernel in sid if you dist-upgrade today, amd64.
Thu Oct 16, 2014 1:10 pm
When I made a snapshot from an encrypted system, the iso would not boot in virtualbox. It dropped me to the initramfs prompt (busybox). I don't think I ever tried it with CD or USB on real hardware. That was in 2012, and I haven't done anything with it since then -
refracta-installer-and-snapshot-used-on-other-distros-t111-20.html?hilit=encrypted%20snapshot&sid=6482363d4ecceb0e5841e235b10678a6#p1038
Wed Oct 22, 2014 10:31 am
Oh, it is my same behavior. I think I get what's happening. The Kernel always looks for the hardware it finds. So, it finds encrypted partitions and doesn't know what that is, and it just stops there. Definitely it's about missing kernel modules.
How do I add additional modules in the snapshot creation route?
By the way, found this:
https://lists.debian.org/debian-user/20 ... 00935.htmlI also found that ehci-orion was in the kernel and recent kernels moved it to a module. It affects not just encrypted partitions. There are live distros that were broken because of that...
Powered by phpBB © phpBB Group.
phpBB Mobile / SEO by Artodia.