Re: [qubes-users] Re: CentOS Virtualization From Multiple .vmdk
awokd, what a relief to get some additional help here! The issue is that this CentOS VM was distributed as a learning environment for a specific course I'm taking with software/services/configurations/etc directly tied to the lessons. I need everything to be intact. I've reached the limit of my experience in this process and can find no other material online to help me. Your dd loopback advice exactly fits this step I'm stuck at. I don't know how to make this bootable. Sigh... I wrote an email to linuxrespin.org yesterday pleading for help which has some information for you I dread to paraphrase/reformat so I'll repost here, because I list commands run and output of file/directory structures... This bends my brain. Apologies and thanks for helping with this mess: --- Hi linuxrespin team! I'm desperate and need your expertise. For one week now I've been bashing my brain trying to get this to work and I've reached the end of my capabilities. Can you please help me? 1. I have a CentOS virtual machine which runs perfectly in VirtualBox. The VM is in .vmdk format. *. I run Qubes OS and need to run CentOS as a guest. I need to convert the .vmdk virtual hard drives into a format which Qubes will accept. 2. I've used qemu-img to convert the .vmdk files into a raw image. 3. I've mounted the raw image (LVM) onto a loop device and am able to access the file system. 4. I have zero understanding of how to make an iso / live iso from this. Can you please help me? I've used the guide below to aide me, but the final tool from the author's repository does not work for me. Do you know how I can take the CentOS filesystem I have access to and turning it into a bootable iso? https://www.turnkeylinux.org/blog/convert-vm-iso --- ls -l /media/sf_Linux/CentOS\ 7.x\ 64-bit/ total 54015160 -rwxrwx--- 1 root vboxsf8684 Jun 7 2017 CentOS 7.x 64-bit.nvram -rwxrwx--- 1 root vboxsf 3413508096 Jun 7 2017 CentOS 7.x 64-bit-s001.vmdk -rwxrwx--- 1 root vboxsf 2366242816 Jun 7 2017 CentOS 7.x 64-bit-s002.vmdk -rwxrwx--- 1 root vboxsf 4088070144 Jun 7 2017 CentOS 7.x 64-bit-s003.vmdk -rwxrwx--- 1 root vboxsf 2242772992 Jun 7 2017 CentOS 7.x 64-bit-s004.vmdk -rwxrwx--- 1 root vboxsf 226492416 Jun 7 2017 CentOS 7.x 64-bit-s005.vmdk -rwxrwx--- 1 root vboxsf 786432 Apr 26 2017 CentOS 7.x 64-bit-s006.vmdk -rwxrwx--- 1 root vboxsf 720896 Apr 26 2017 CentOS 7.x 64-bit-s007.vmdk -rwxrwx--- 1 root vboxsf 3080192 Jun 7 2017 CentOS 7.x 64-bit-s008.vmdk -rwxrwx--- 1 root vboxsf 720896 Apr 26 2017 CentOS 7.x 64-bit-s009.vmdk -rwxrwx--- 1 root vboxsf19136512 Jun 7 2017 CentOS 7.x 64-bit-s010.vmdk -rwxrwx--- 1 root vboxsf 131072 Apr 26 2017 CentOS 7.x 64-bit-s011.vmdk -rwxrwx--- 1 root vboxsf1029 Jun 7 2017 CentOS 7.x 64-bit.vmdk -rwxrwx--- 1 root vboxsf 69 Apr 26 2017 CentOS 7.x 64-bit.vmsd -rwxrwx--- 1 root vboxsf2888 Jun 7 2017 CentOS 7.x 64-bit.vmx -rwxrwx--- 1 root vboxsf 272 Apr 26 2017 CentOS 7.x 64-bit.vmxf --- qemu-img convert -f vmdk turnkey-core.vmdk -O raw turnkey-core.raw mkdir turnkey-core.mount loopdev=$(losetup -s -f turnkey-core.raw) kpartx -a $loopdev --- ls -l /dev/mapper/ total 0 lrwxrwxrwx 1 root root 7 Apr 16 21:06 centos-home -> ../dm-5 lrwxrwxrwx 1 root root 7 Apr 16 21:06 centos-root -> ../dm-2 lrwxrwxrwx 1 root root 7 Apr 16 21:06 centos-swap -> ../dm-4 lrwxrwxrwx 1 root root 7 Apr 16 21:06 centos-var -> ../dm-3 crw--- 1 root root 10, 236 Apr 14 23:39 control lrwxrwxrwx 1 root root 7 Apr 16 19:03 loop0p2 -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 16 19:34 loop1p1 -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 16 19:34 loop1p2 -> ../dm-6 lrwxrwxrwx 1 root root 7 Apr 16 21:06 loop3p1 -> ../dm-7 lrwxrwxrwx 1 root root 7 Apr 16 21:06 loop3p2 -> ../dm-8 --- mkdir turnkey-core.mount mount /dev/mapper/$(basename $loopdev)p1 turnkey-core.mount ^ the above command gives me access to: --- config-3.10.0-514.16.1.el7.x86_64 config-3.10.0-514.2.2.el7.x86_64 extlinux grub grub2 initramfs-0-rescue-0a268e711a9e49e6958dee98a83bcef2.img initramfs-3.10.0-514.16.1.el7.x86_64.img initramfs-3.10.0-514.16.1.el7.x86_64kdump.img initramfs-3.10.0-514.2.2.el7.x86_64.img initramfs-3.10.0-5
[qubes-users] Re: CentOS Virtualization From Multiple .vmdk
Using the following guide I've been able to mount the raw, qemu-img converted .vmdk files onto a loop device, thus I'm able to access every partition of the virtual machine. https://www.turnkeylinux.org/blog/convert-vm-iso Unfortunately the end of the guide is broken for my case and I'm unable to generate the iso. I've successfully extracted the root filesystem. Now that I have all the data, how to I turn this into an iso file which will load the vm? Please help, I've been banging my head on this thing for a week and am lost. :( -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1e0ebd07-bcf9-4c1a-9b68-b6eaeb96968b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: CentOS Virtualization From Multiple .vmdk
I've also just tried: qvm-create centos --class StandaloneVM --property virt_mode=hvm --property kernel="" --property memory=4096 --property maxmem=4096 --property debug=True --label red qvm-start centos --cdrom=TEST-VMDK:/home/user/root.img and qvm-start centos --hddisk=TEST-VMDK:/home/user/root.img -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1e9f41ce-04a1-405a-8f65-6ca316a2d641%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: CentOS Virtualization From Multiple .vmdk
I forgot to mention: SeaBIOS (version rel-1.10.2-0-...) Machine UUID ... Booting from Hard Disk... Boot failed: not a bootable disk Booting from Floppy... Boot failed: could not read the boot disk No bootable device. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e5268680-dbfa-44ee-b3af-6809b742168b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: CentOS Virtualization From Multiple .vmdk
Drew, Would you mind walking me through this more step-by-step? I've tried many variations of this and I keep failing. I'm using Qubes 4.0. To create the centos qube I do: Qube Manager-> Qube-> Create new qube-> Name and label: centos red Type: Standalone qube not based on a template In a qube named TEST-VMDK, I have the CentOS root image here: /home/user/root.img Which I've created using your advice: qemu-img convert {path/to/vmdk}CentOS\ 7.x\ 64-bit.vmdk root.img Is this the correct way to create the StandaloneVM I need? Should it be/not be based on a template? Should it be the default (PVH) mode, or HVM? Should the kernel be the default (4.14.18-1) (current)? I don't know how to do this from the terminal using Qubes 4.0. >From dom0 I've: qvm-run --pass-io TEST-VMDK 'cat /var/lib/qubes/appvm' > /home/user/root.img I think this is wrong? Why does my PVH/HVM show up in /var/lib/qubes/appvms? Why do none of the qubes in that directory contain root.img? Where should my root.img reside? Is there a command to create the correct VM type and load a root image from a specified qube such as TEST-VMDK? When I do: qvm-prefs-centos There's no line about a root.img so I must be doing something very wrong? As you can see... a lot of step-by-step hand-holding would be amazing. I really need to understand how to do this. I have a lot of VMs I need to load this way... Thank you so much for your help. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/55300f8f-e0a0-4a4f-be23-668a2019aaac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] CentOS Virtualization From Multiple .vmdk
Hello everyone, thank you for your help :) I'm not having success creating a CentOS 7.6 (x86_64) VM from multiple .vmdk files. I've attempted to follow the official Qubes HVM guide and other guides on the Internet. The files: CentOS 7.x 64-bit-s001.vmdk CentOS 7.x 64-bit-s002.vmdk CentOS 7.x 64-bit-s003.vmdk CentOS 7.x 64-bit-s004.vmdk CentOS 7.x 64-bit-s005.vmdk CentOS 7.x 64-bit-s006.vmdk CentOS 7.x 64-bit-s007.vmdk CentOS 7.x 64-bit-s008.vmdk CentOS 7.x 64-bit-s009.vmdk CentOS 7.x 64-bit-s010.vmdk CentOS 7.x 64-bit-s011.vmdk CentOS 7.x 64-bit.nvram CentOS 7.x 64-bit.vmdk CentOS 7.x 64-bit.vmsd CentOS 7.x 64-bit.vmx CentOS 7.x 64-bit.vmxf This runs CentOS with a GUI successfully under VirtualBox on Linux. I have tried these sections of following guide: https://www.qubes-os.org/doc/hvm/#converting-virtualbox-vm-to-hvm https://www.qubes-os.org/doc/hvm/#creating-an-hvm-domain Here are steps I'm taking now to provide more information: # Convert vmdk to raw: qemu-img convert *.vmdk -O raw image.img # Qube Manager - Create new Qube # Name and label: centos # Type: Standalone qube not based on a template # Advanced: install system from device # Start CentOS qvm-start centos --cdrom=TEMP:/home/user/image.img # centos window opens with the following output: SeaBIOS (version ...) Machine UUID ... Booting from DVD/CD... Boot failed: Could not read from CDROM (code 0004) Booting from Hard Disk... Boot failed: not a bootable disk Booting from Floppy... Bootfailed: could not read the boot disk No bootable device. # Trying with hddisk as per: https://groups.google.com/d/msg/qubes-users/84IjinPx_ng/eWFv81S4tnsJ qvm-start centos --hddisk=TEMP:/home/user/image.img # F5 and Copying to Dom0 Suggestions also fail: https://groups.google.com/d/msg/qubes-users/84IjinPx_ng/mYYfbj6mSeIJ Could something here be the problem? qemu-img convert *.vmdk -O raw image.img I don't know what else to try... Thanks for your help. :) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/81683354-d012-46b2-981f-678604039bbb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.