tuxd3v | can anyone run this, ofcourse with his changes, and check if the mini.iso starts? | 00:11 |
---|---|---|
tuxd3v | https://paste.debian.net/hidden/5ebfb4e5/ | 00:11 |
tuxd3v | I'm going crazy with this.. | 00:11 |
zmoment | I understand you, perfectly! | 00:12 |
zmoment | tuxd3v: where's the problem? | 00:15 |
zmoment | it's booting for installation, so far, so good | 00:15 |
tuxd3v | it doesn't launch the mini.iso to try to show the menu were you can install and do other stuff..the menu doesn't apear to me :/ | 00:16 |
tuxd3v | I had a process running for several hours here and indeed...nothing hapens, but the process don't die.. | 00:17 |
tuxd3v | don't know what to say :/ | 00:17 |
zmoment | I just used the mini.iso that I had and renamed to match the name in your script, and did the same thing creating an empty disk image. | 00:17 |
tuxd3v | do you manage to see the mini.iso menu? | 00:18 |
zmoment | yes. Double check if the mini.iso is the correct one. I removed the absolute paths and have all the disks in a directory where the script is. | 00:19 |
tuxd3v | damm, so the proble is somewhere in my machine, but where..?:S | 00:20 |
tuxd3v | many many thanks for your check | 00:20 |
zmoment | it's already asking for root password, guess it's been quicker than mine installations... | 00:22 |
zmoment | tuxd3v: it stopped Out of memory: Kill process 229 (debconf) score 64 or sacrifice child | 00:26 |
tuxd3v | ho.. | 00:26 |
tuxd3v | so 512MB is not eoungh | 00:26 |
tuxd3v | enough.. | 00:26 |
tuxd3v | but even so, it should show the mini.iso menu, don't you agree? | 00:27 |
zmoment | it only had 320M I think | 00:27 |
tuxd3v | ho.. | 00:27 |
tuxd3v | even with 320 it showed the menu to you right? | 00:27 |
tuxd3v | ok, so now it gives me this errors: https://paste.debian.net/hidden/e5b780a2/ | 00:30 |
zmoment | yes | 00:35 |
tuxd3v | many thanks | 00:35 |
tuxd3v | it could be something else... I am in Chimaera, maybe there are some incompatibilities in some binaries yet.. | 00:36 |
zmoment | humm, it starts to smell like my problems | 00:36 |
zmoment | tuxd3v: this has some info about qemu options https://fosdem.org/2018/schedule/event/vai_qemu_jungle/attachments/slides/2539/export/events/attachments/vai_qemu_jungle/slides/2539/qemu_cli_jungle.pdf | 12:47 |
koleygr | Hi | 13:01 |
koleygr | Can somebody please tell me how to login in my new arm installation on a pri4? | 13:01 |
koleygr | I can't find the user na me and password ... Just installed on a usb disk via dd command from devuan OS and seems to work ... but can't find username and password to login | 13:03 |
gnarface | they're probably in the readme | 13:17 |
gnarface | it might be root:toor though | 13:17 |
koleygr | Thanks for the answer ... but tried that and didn't worked | 13:19 |
koleygr | it says something about no password ... but tried this too and didn't worked | 13:19 |
koleygr | I will come back... Thanks anyway | 13:20 |
tuxd3v | zmoment, thanks.. | 16:20 |
tuxd3v | the thing is the command in your computer works, but in mine don't :/ | 16:20 |
tuxd3v | I will experiment with the pflash boot0 and boot 1 to see if that solves.. | 16:21 |
Tenkawa | tuxd3v: whats the output of cat /proc/cpuinfo on yours? | 16:43 |
Tenkawa | your cpu could be missing the extensions | 16:43 |
Tenkawa | just pastebin one core's flags and vmx sections | 16:45 |
Tenkawa | if it doesn't have something like this theres likely your problem: | 16:46 |
Tenkawa | vmx flags: vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple pml ept_mode_based_exec | 16:46 |
tuxd3v | the thing is, for a 32 bits mini.iso works, for 64 bits don't | 17:03 |
tuxd3v | but it could be indeed related to that stuff.. | 17:03 |
tuxd3v | the cpu is old | 17:03 |
Tenkawa | yeah your cpu has to support virt extensions | 17:15 |
zmoment | Tenkawa: regardin the mapping of drives, I found this for virsh: | 18:07 |
zmoment | virsh attach-disk Guest1 --persistent /dev/sdc1 vdc | 18:07 |
zmoment | it means that /dev/sdc1 will always be /dev/vdc at the guest | 18:07 |
zmoment | for qemu, I didn't find anything. But I'm trying the convenience -hda or -hdb | 18:08 |
Tenkawa | virsh can handle all the mgmt functions | 18:08 |
Tenkawa | https://linux.die.net/man/1/virsh | 18:09 |
Tenkawa | been around since the redhat days | 18:09 |
Tenkawa | very useful | 18:09 |
zmoment | yes, but I prefer qemu machinery as I may use it in other non-Linux systems | 18:13 |
Tenkawa | qemu-attach Attach to existing QEMU process | 18:15 |
Tenkawa | qemu-monitor-command QEMU Monitor Command | 18:15 |
Tenkawa | read the manpage | 18:15 |
Tenkawa | it "does" use qemu | 18:15 |
Tenkawa | I pasted thar right from that link I just posted | 18:16 |
Tenkawa | er that | 18:16 |
Tenkawa | list the values supported, but the most common are: | 18:17 |
Tenkawa | xen:/// | 18:17 |
Tenkawa | this is used to connect to the local Xen hypervisor, this is the default | 18:17 |
Tenkawa | qemu:///system | 18:17 |
Tenkawa | connect locally as root to the daemon supervising QEmu and KVM domains | 18:17 |
Tenkawa | qemu:///session | 18:17 |
Tenkawa | connect locally as a normal user to his own set of QEmu and KVM domains | 18:17 |
Tenkawa | lxc:/// | 18:17 |
zmoment | Meanwhile, my debian installation that got the disk as vdb, this time rebooted after the installation and renamed it to vda. Now, it's at the initramfs prompt and I couldn't correct the issue. uefi-grub-initramfs oh dear. | 18:26 |
Tenkawa | zmoment: did it eject the iso/cdrom? if so thats why | 18:42 |
Tenkawa | your device ordering has changed | 18:42 |
zmoment | yes, I removed the line. I could keep it with a blank file maybe or reconfigure initramfs. | 18:44 |
tuxd3v | zmoment, change the fstab to vda, in that way you can remove the line :) | 19:57 |
tuxd3v | its what I have done in my 32 bit install ;) | 19:57 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!