remove win 10 from a dual boot

I’ve been evaluating a new laptop model for possible use by others in the building (lots of travel). My original game plan for this HP Envy 360 13.3 was to preserve Windows temporarily, shrink the Window partition, install Leap 42.3 as a dual boot long enough to eval openSUSE on the somewhat cutting edge hardware. If all went well I would wipe the drive, reinstall Leap using the whole drive and put Win 10 in a VM for infrequent use with one program. If not I would restore OEM Windows and return the PC.

I found that the post-install configuring of Leap on this Kabylake hardware, etc. was extremely complex & difficult, and I have no desire to go through it again, however now that the system is set up I am thrilled with it, therefore I have a new plan.

# fdisk -l
Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E1D7AECD-133E-4DD9-989A-5DD30EAF6715

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     534527    532480   260M EFI System
/dev/nvme0n1p2    534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3    567296  368198755 367631460 175.3G Microsoft basic data
/dev/nvme0n1p4 976068608  978075647   2007040   980M Windows recovery environment
/dev/nvme0n1p5 978075648 1000202239  22126592  10.6G Microsoft basic data
/dev/nvme0n1p6 368199680  372402175   4202496     2G Microsoft basic data
/dev/nvme0n1p7 372402176  435329023  62926848    30G Microsoft basic data
/dev/nvme0n1p8 435329024  976068607 540739584 257.9G Microsoft basic data

Using Gparted I would delete the Windows partitions, move swap, / and home into that space, then expand home as much as possible before setting up the VM. (home and / are ext4)

I know it won’t be that simple. (id’s etc. will be off at the very least)

What are the landmines in my way? What workarounds will I need?

I would leave things as they are, I’m guessing partitions 2,3,4 and 5? With a gpt disk, use gdisk -l and lsblk gives better views…

Then just use the space as a new partition and mount it as say /data all via YaST partitioner, else your going to have to boot from a rescue system and run gparted, move stuff around, check the UUID’s and modify /etc/fstab with the new ID’s etc…

Thank you. As so often happens you’ve given me a much simpler approach than my own. Positively elegant in its simplicity. Furthermore it will give me the chance to give the new Virtual install of Win 10 a good shakedown before removing the factory install.

Just remember to grab your WinX product ID’s (eg ProduKey) so can use in your virtual environment. You might also check on the system manufacturer’s website for free recovery media…

Also conside KVM as the virtualization technology to use.