Preparing to run multiple qcow images from a new T7 SSD

mx flag

I just got a new 1 TB Samsung T7 SSD and I want to be able to run multiple VM's from this drive using QEMU/KVM and virt-manager.

First question: Do I need to do anything to format or prepare the SSD drive? I have done nothing so far except mount it and look at directories. Haven't setup password protection or anything like that.

Second question: I am sure I will need to change my default storage pool and edit XML files when I create new VM's can anyone explain that to me?

Finally, I imagine I will have to edit XML files to make each instance somehow unique with different IP so I can distinguish it for SSH purposes?

waltinator avatar
it flag
A multiple member, overly broad, bunch of UTBLT Using Thing Before Learning Thing) question-like meanderings doesn't fit with AskUbuntu's Q&A format. Please read and
ar flag
You can change the storage pool using the Virtual Machine Manager, the GUI for KVM. No manual editing of XML should be needed. Other than the `ext4` format, there is no special thing you need to do to the external drive.
dino avatar
mx flag
Thanks for your help. I'll take your advise. I found a youtube vid explaining everything I need to know.
sa flag

For best results you should reformat the SSD to get rid of the password protection which turns the Samsung T7 into an SSD that mounts automatically like a normal external SSD when its USB cable is plugged in. Format the Samsung T7 to whatever format you prefer based on its expected use case just like an ordinary external SSD.

mx flag

Yes, Thank you, I did format my SSD to ext4 first thing before I attempted to create virtual machine.

I worked my problem out and did not want to leave this thread orphaned, in hope of maybe helping someone else.

First of all, I was able to get a VM working using default settings from my local drive but installing on the SSD was giving me fits. I did get a working VM on the T7 which was great but I then tried editing my /etc/fstab to mount the device by UUID# instead of /dev/sdbx and that broke the VM. I was able to intermittently get a couple of VM's working by setting them up as root and a couple of other setups that I was uncomfortable with because it required me to run them with system wide sudo privileges. I was trying to do things that are a little more advanced than my skill level by setting up custom mount points and mounting the device by UUID so it wouldn't mater what port I plugged the device into and trying automount and nofail options in my /etc/fstab That kept crashing my system. I kept running into permission problems as well as other issues, so many in fact that I can't remember everything I tried. I decided to leave my mount points default and just plug the device in to the same port every time. I was finally able to get another VM working then it was broken by a system update. I spent 4 or 5 days trying to figure that out going as far as reinstalling my system and reformatting my SSD. Nothing I tried would fix the permission issues and I kept getting an error that I was trying to use storage that was not compatible with the dir file system. I new something was not right about that because every working VM that I had created was using the dir file system and the error i was getting was telling me my storage needed to be in the fat format. Finally, yesterday an update came down the pike for qemu and that fixed all of the issues and errors that I was experiencing.

I will tell you that I used chatgpt to work through a lot of these issues and it was very helpful. However it is limited in what it can do. You have to constantly direct it back to the history of the chat and it will tend to take you in loops to try and fix a problem (especially if the problem is unfixable do to a broken package caused by a system update). You also have to be knowledgeable enough to ask it the right questions. There is no doubt I learned a lot through this experience (as was my goal) about permissions and how to set them using chmod and chown, using virsh, as well as all kinds of commands that I would not have learned had I not had to do them repeatedly through the direction of chatgpt. I am pretty impressed with it as a learning tool.

Anyway. I learned that it is best (if you are at my skill level) to leave things default if possible. I'm talking about mount points and settings in the virt-manager when trying to setup a VM and run it from your SSD. If you can follow directions and have patience to learn it is very doable and really not all that difficult as long as you don't get too far off base with customization. I've got a pretty firm grip on how to work with qemu/kvm, libvirt, virt-manager system now although it took a little bit of learning and repeatedly using commends.

I sit in a Tesla and translated this thread with Ai:


Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.