Why choosing QEMU directly instead of the virtualisation stack

Why I chose QEMU directly instead of the virtualisation stack Today I finally settled the question: QEMU directly vs libvirt/virt-manager , especially for a Windows work VM stored on a USB stick. Short answer: for this use case, QEMU + one good script beats the whole virtualisation stack. My context The VM disk ( LCS.raw ) lives on a USB partition (label: LCS_RAW ). I want a “VM on a stick”: plug USB anywhere → mount → run → done. It’s one VM, always the same, for client work (Windows + browser). I don’t need snapshots, multi-VM orchestration, XML configs, etc. Why I didn’t want libvirt / virt-manager here 1. libvirt assumes “local, permanent storage” Libvirt stores VM definitions in XML pointing to fixed paths like: /var/lib/libvirt/images/windows.qcow2 My VM is on a removable USB , which might be: /dev/sda2 today /dev/sdb2 tomorrow /media/ernest/Whatever if Plasma mounts it /mnt/LCS when I mount it manually Libvirt and virt-manager don’...
0

Changing or setting up the Prompt Statement - PS (bash prompt)

PS1="<special_characters>"


Guides:


Bash prompt special characters


\a

An ASCII bell character (07)

\d
The date in “Weekday Month Date” format (e.g., “Tue May 26”)

\D{format}
The format is passed to strftime(3) and the result is inserted into the prompt string; an empty format results in a locale-specific time representation. The braces are required

\e
An ASCII escape character (033)

\h
The hostname up to the first ‘.’

\H
The hostname

\j
The number of jobs currently managed by the shell

\l
he basename of the shell’s terminal device name

\n
Newline

\r
Carriage return

\s
The name of the shell, the basename of $0 (the portion following the final slash)

\t
The current time in 24-hour HH:MM:SS format

\T
The current time in 12-hour HH:MM:SS format

\@
The current time in 12-hour am/pm format

\A
The current time in 24-hour HH:MM format

\u
The username of the current user

\v
The version of bash (e.g., 2.00)

\V
The release of bash, version + patch level (e.g., 2.00.0)

\w
The current working directory, with $HOME abbreviated with a tilde

\W
The basename of the current working directory, with $HOME abbreviated with a tilde

\!
The history number of this command

\#
The command number of this command

\$
If the effective UID is 0, a #, otherwise a $

\nnn
The character corresponding to the octal number nnn

\\
A backslash

\[
Begin a sequence of non-printing characters, which could be used to embed a terminal control sequence into the prompt

\]
End a sequence of non-printing characters 

Comments

Post a Comment