hi everybody,
how could I (easily) follow file modifications made by guest os (Windows)
with qemu ?
could I directly exploit the overlay image based on an original Windows
image ?
regards, lacsaP.
hi everybody,
I've a qcow2 image disk (win.img) and I run a VM (qemu -hda linux.img) :
how can I hotplug my second disk (win.img) in my running VM ?
thanks for help, lacsaP.
hello,
while doing some tests on the ntfs file system, I met some strange things
with my qcow2 disk images.
the images are on a partition mounted in tmpfs, but the result is the same
when they are recorded on a partition in ext4 format.
I don't know where the problem comes from : qemu-nbd or forma
I just finished the same test on raw images (with losetup instead of
qemu-nbd) and the problem does not occur in this case.
(ntfsfix is - must be - used with the -n option to not alter the checked
partitions)
2017-12-01 18:56 GMT+01:00 Pascal :
> hello,
>
> while doing some tests on
880305172e6f54c8c201 /dev/nbd1p1
qemu-nbd -d /dev/nbd0
/dev/nbd0 disconnected
qemu-nbd -d /dev/nbd1
/dev/nbd1 disconnected
rm -f /tmp/a.img
rm -f /tmp/b.img
2017-12-05 19:29 GMT+01:00 Programmingkid :
> >
> > Message: 1
> > Date: Mon, 4 Dec 2017 19:04:36 +0100
> > Fro
m -m 2048 -bios OVMF-pure-efi.fd -hda
/dev/sdx
(assuming your USB flash drive is /dev/sdx and is readable)
are your really sure your USB flash drive is UEFI ready ?
I hope it will help.
2018-05-09 1:20 GMT+02:00 ToddAndMargo :
> On 05/06/2018 11:26 PM, Pascal wrote:
>
>> hi, install
hi,
when I run qemu with machine pc, my virtual network card "runs", but not
when I run it with machine q35.
in the first case (pc), module e1000 is loaded and dhcpcd on ens3 is ok (
10.0.2.15/24).
in the second case (q35), module e1000e is loaded and dhcpcd on enp0s2 is
ko (waiting for carrier/
np0s2).
I think the problem would rather come from the virtualized 4.14.40-1-lts
kernel side because I do not meet it on my physical host which also uses
the e1000e module...
does anyone have an idea or a lead ?
regards, lacsaP.
2018-05-11 15:39 GMT+02:00 Pascal :
> hi,
>
> when I run q
the guests are started as follows :
/usr/bin/qemu-system-x86_64 -enable-kvm -m 2048 -machine {q35|pc} -usb -hda
{arch1|arch2}.img
regards.
2018-05-28 15:32 GMT+02:00 Pascal :
> hello,
>
> I come back to you with this subject that I opened to bring some
> clarifications, becaus
Mon, May 28, 2018 at 9:53 PM, Pascal wrote:
>
>> the guests are started as follows :
>>
>> /usr/bin/qemu-system-x86_64 -enable-kvm -m 2048 -machine {q35|pc} -usb
>> -hda
>> {arch1|arch2}.img
>>
>> regards.
>>
>> 2018-05-28 15:32 GMT+02:00 Pas
restart from zero if possible...
# qemu-nbd -d /dev/nbd0
# modprobe -rv nbd
# modprobe nbd
# qemu-nbd -c /dev/nbd0 /the/file
# blockdev --rereadpt /dev/nbd0
# fdisk -l /dev/nbd0
# mount /dev/nbd0p1 /mount/point
Le jeu. 29 nov. 2018 à 17:32, Jakob Bohm a écrit :
> Check
>
> cat /proc/partit
the fdisk command ended without error :
# sync
# qemu-nbd -d /dev/nbd0
# qemu-nbd -c /dev/nbd0 /the/target
Le ven. 30 nov. 2018 à 14:04, ramakanth varala
a écrit :
> Hi Pascal & Jakob,
>
> I started from first .
>
> I created manully the partitions as below
>
>27
1 4 32098+ 83 Linux
> /dev/nbd0p2 5261020932695 83 Linux
>
> Command (m for help): q
>
> [root@localhost ~]# blockdev --rereadpt /dev/nbd0
> BLKRRPART: Invalid argument
> [root@localhost ~]# ls /dev/nbd0
> /dev/nbd0
&g
try to disconnect and then re-connect the exported (network) device (eg.
the over side)...
Le mar. 4 déc. 2018 à 11:53, Jan Schermer a écrit :
> Partigion is missing :-)
> try:
> kpartx -a /dev/ndb0
>
>
> > On 4 Dec 2018, at 11:35, ramakanth varala
> wrote:
> >
&
er wrote:
>
>> Partigion is missing :-)
>> try:
>> kpartx -a /dev/ndb0
>>
>>
>> > On 4 Dec 2018, at 11:35, ramakanth varala
>> wrote:
>> >
>> > Hi Pascal..
>> >
>> > yes its RW ...
>> >
>> > [root@localho
efcount_bits=16
# ll /tmp/test.*
-rw-r--r-- 1 root root 196616 4 déc. 14:20 /tmp/test.qcow
-rw-r--r-- 1 pascal pascal 536870912 4 déc. 14:20 /tmp/test.raw
# modprobe nbd
# qemu-nbd -c /dev/nbd0 /tmp/test.raw
WARNING: Image format was not specified for '/tmp/test.raw
home/test/test.3.5.1b.debug/test.3.5.1b.debug.raw: x86 boot sector;
> partition 1: ID=0x83, starthead 1, startsector 63, 208782 sectors;
> partition 2: ID=0x83, starthead 254, startsector 41913585, 16065 sectors,
> code offset 0x48
>
>
> On Tue, Dec 4, 2018 at 6:48 PM Pascal wro
gt;> Report bugs to
>> [root@localhost ~]# qemu-nbd --version
>> qemu-nbd version 0.0.1
>> Written by Anthony Liguori.
>>
>> Copyright (C) 2006 Anthony Liguori .
>> This is free software; see the source for copying conditions. There is NO
>> warranty; not
hi,
did you try to start Win10 by leaving the -machine pc-q35-2.4 option ?
otherwise, if you still have your Linux available, you can try to start
Win10 without the -cpu host option and with the -cpu kvm64 option.
why do you finally start Win10 with the -no-kvm option?
regards.
Le lun. 18
hello,
if I understand correctly, you want to study the possibility of recovering
deleted files from an SSD disk: is that right ?
regards, lacsaP.
Le jeu. 4 avr. 2019 à 08:24, Narcis Garcia a écrit :
> Is there a way to specify a disk to be detected as an SSD drive?
>
> Once reached this, I wa
backing. Anything that can handle
> > discards will do, including sparse files.
> >
> >
> > My advice, however, would be to use qcow2, since sparse files don't work
> > particularly well. Executing the example above would leave you with
> > about 300MB a
he discard operation was working strings(1) would still show
> > the hello-world string in the journal.
> >
> > You could try something like this:
> >
> > $ echo hello, world > /dev/sda
> > $ strings /dev/sda
> > $ blkdiscard /dev/sda
> > $ strings
th lsblk and fstrim)
>
> How can I make guest OS to detect device as no rotational or true SSD?
>
>
> El 10/4/19 a les 12:47, Narcis Garcia ha escrit:
> > Pascal, I don't understand syntax you use for lsblk.
> > I see this with:
> > $ cat /sys/block/sda/queue/rot
I would tend to say that "discard" is not related to "ssd" while "rotational"
is...
Le mer. 10 avr. 2019 à 14:06, Pascal a écrit :
> lsblk -ndo ROTA /dev/sda
>
> sorry for the bad copy.
>
> Le mer. 10 avr. 2019 à 12:52, Narcis Garcia a
>
/nbd0 $temo_raw
>
> 2)qemu-nbd --partition=1 --connect /dev/nbd0 $temp_raw
>
>
>
> Thanks
>
>
> On Thu, Jan 17, 2019 at 6:50 PM Pascal wrote:
>
>> hi,
>>
>> your /home/pnsc/nsc.3.5.1b.debug/nsc.3.5.1b.debug.raw is a raw disk
>> image, is that
probably give
you a lot of explanations...
regards, lacsaP.
Le lun. 13 mai 2019 à 13:05, ramakanth varala
a écrit :
> Hi Pascal,
>
> thanks for the information. I had to do some changes to make that work.
>
> I was using RHEL 5.7 , no partitions visible in /proc/partitions
hi,
how to redirect a local port in guest to a local port on host (adb) ?
I've tried :
qemu ... -nic user,guestfwd=tcp:127.0.0.1:5037-tcp:127.0.0.1:5037
but I've got this error :
qemu-system-x86_64: Conflicting/invalid host:port in guest forwarding rule
'tcp:127.0.0.1:5037-tcp:127.0.0.1:5037'
crit :
> On Tue, 28 May 2019 at 15:01, Pascal wrote:
> > how to redirect a local port in guest to a local port on host (adb) ?
> >
> > I've tried :
> >
> > qemu ... -nic user,guestfwd=tcp:127.0.0.1:5037-tcp:127.0.0.1:5037
> >
> > but I've go
hello,
when a smartphone (android) is connected to the host PM, its USB
interface(s) changes state depending on the selected function (power, mtp,
etc...) and theses changes are not reflected on the guest VM : how handle
this ?
a USB hub can be transferred from the host PM to the guest VM but it
hi,
I have two Linux VM that communicate without any problem when I use VDE but
their communication stops when I try to connect them with a multicast bus :
does anyone have an idea ?
vde_switch
qemu -nic vde,mac=52:54:00:11:11:11 vm1.disk
qemu -nic vde,mac=52:54:00:22:22:22 vm2.disk
and all is o
hi,
for information : the disabling of my firewall fixed the problem :-)
regards, lacsaP.
Le mer. 18 sept. 2019 à 11:57, Pascal a écrit :
> hi,
>
> I have two Linux VM that communicate without any problem when I use VDE
> but their communication stops when I try to connect
anation, a beginning of a solution or a path to
follow ?
is VDE still maintained ? I like using it because it does not require any
privileges.
regards, lacsaP.
-- Forwarded message -
De : Pascal
Date: lun. 23 sept. 2019 à 10:33
Subject: Re: connect virtual machines to each othe
when I start qemu as below : *qemu: Parameter
'type' expects a net backend type (maybe it is not compiled into this
binary)*
regards, lacsaP.
-- Forwarded message -
De : Pascal
Date: ven. 27 sept. 2019 à 09:23
Subject: [Qemu-discuss] connect virtual machines to each othe
hi,
try : qemu jsec2.bin -snapshot
Le mar. 29 oct. 2019 à 07:45, bilsch01 a écrit :
> I have a simple 16-bit real mode OS called JINX that I have been
> running/testing on a flash drive. I write the 8192 byte file, jsec2.bin,
> to a flash drive using the linux dd copy utility, and then boot th
hi,
if you do tar tvf on your .img file, then this file is not a disk image,
but a tar file ?
Le mar. 29 oct. 2019 à 04:15, Supratim Sanyal a
écrit :
> Hi all,
>
> I have a basic XENIX 2.3.4 installation running great under
> qemu-system-i386 version 3.1.1/FreeBSD 12-RELEASE.
>
> I recently obta
try to install nec usb xhci drivers on 7
Le lun. 18 nov. 2019 à 06:03, ToddAndMargo a écrit :
> On 11/17/19 8:16 PM, Christopher Snowhill (kode54) wrote:
> > Windows 7 has always required vendor drivers for USB 3.x. You can try
> setting the interface to mimic a real XHCI device that has Windows
hello,
can we say that if the tests are conclusive under Qemu then, they will
necessarily be conclusive on real hardware that will be at least as
powerful as the Qemu host ?
regards, lacsaP.
Le lun. 20 janv. 2020 à 16:14, caner yilmaz a
écrit :
> Hello Peter,
>
> That was also my understanding,
hi everybody,
I use (the excellent) qemu with -serial mon:stdio instead of -monitor stdio
because I'm a killer Ctrl-C :-)
is there a way to activate/open automatically the monitor without using
Ctrl-A+C with the keyboard ?
regards, lacsaP.
sh groups of commands there via a script .
regards, lacsaP.
Le mar. 31 mars 2020 à 09:48, Pascal a écrit :
> hi everybody,
>
> I use (the excellent) qemu with -serial mon:stdio instead of -monitor
> stdio because I'm a killer Ctrl-C :-)
>
> is there a way to activate/open au
hi Peter,
thank you for these explanations which answer perfectly to my need (which
is only occasional).
regards, lacsaP.
Le mar. 31 mars 2020 à 17:22, Peter Maydell a
écrit :
> On Tue, 31 Mar 2020 at 15:45, Pascal wrote:
> > my goal is to be able to easily pass commands to qem
may be adding media=disk to the drive definition : -drive
if=none,format=raw,file=disk.img,media=disk
otherwise, are you sure you packed the right stuff to detect the disc?
Le ven. 3 avr. 2020 à 07:28, a écrit :
> Hi
>
> I have a working QEMU image emulating an ARM vexpress-a9 and I run it like
hello,
I had a similar problem with VDE.
I didn't get an answer, but don't despair.
Unfortunately I haven't tried again since.
https://wiki.archlinux.org/index.php/Talk:QEMU#VDE
regards, lacsaP.
Le jeu. 11 juin 2020 à 02:53, Filipe Manana a écrit :
> Hello,
>
> Using any qemu version from 3.x to
use -b and not -o :
qemu-img create -f qcow2 -b base_img.qcow2 overlay1_img.qcow2
qemu-img create -f qcow2 -b base_img.qcow2 overlay2_img.qcow2
and then :
qemu overlay1_img.qcow2
qemu overlay2_img.qcow2
Le jeu. 24 sept. 2020 à 08:48, Bernd Nachtigall a écrit :
> Hi,
>
> qemu: 3.1.1.1
> qemu-kvm:
hi,
under Qemu 5.1.0, with a Windows virtual machine, if in the console I use
drive_add 0 if=none,file=usb.disk,id=usbdrv
device_add usb-storage,drive=usbdrv,id=usbkey
the disk is presented next to the hard disk C: and is not considered
removable although it is possible to eject it from the tool
hi,
when you are asked to change the floppy disk,
- go to the Qemu console (Ctrl-Alt-2 I think),
- "eject" the floppy disk in place with eject floppy0
- "insert" the desired floppy disk with change floppy0 diskX.img
- go back to Qemu (Ctrl-Alt-1 I think),
- resume installation
regards, lacsaP.
L
hi,
my 21H1 is running with UEFI activated in the VM (-bios ...) : try on this
side...
regards.
Le lun. 12 juil. 2021 à 10:27, Stefano Cappa
a écrit :
> I'm trying to install Windows 10 64 bit (latest available official iso)
>
> my environment:
> - macbook pro 13 2020 (intel)
> - macos BigSur (w
hi,
if it is installed on your system, `lsof` may tell you which process blocks
(uses) your file...
regards.
Le sam. 10 juil. 2021 à 16:02, gustavklopp a écrit :
> Hi!
> I've launched a virtual image through the software virtual-manager (it's a
> GUI allowing to launch your virtual images).
>
>
under Linux, it is generally the `ovmf` package which contains the
necessary (ovmf.fd) :
-bios /usr/share/ovmf/OVMF.fd
Le lun. 12 juil. 2021 à 10:44, Stefano Cappa
a écrit :
> Thank you, but where can I find the bios file to pass to that command?
>
> Il lun 12 lug 2021, 10:35 Pascal h
params?
>
> Il lun 12 lug 2021, 10:52 Pascal ha scritto:
>
>> under Linux, it is generally the `ovmf` package which contains the
>> necessary (ovmf.fd) :
>> -bios /usr/share/ovmf/OVMF.fd
>>
>> Le lun. 12 juil. 2021 à 10:44, Stefano Cappa <
>> stefan
hello everybody,
virtual FAT disk image - *which is a convenient way to transfer files to
the guest without having to activate its network* - seems to work very
poorly with Windows : do you have the same difficulties?
context : up to date archlinux, qemu 6.0.0, fresh installed windows 10 21H1.
/
up :-)
nobody uses this feature of qemu?
Le ven. 27 août 2021 à 11:11, Pascal a écrit :
> hello everybody,
>
> virtual FAT disk image - *which is a convenient way to transfer files to
> the guest without having to activate its network* - seems to work very
> poorly with Window
up² :-)
can someone just ping me to make me sure I'm posting on the qemu list ?
Le mar. 31 août 2021 à 09:24, Pascal a écrit :
> up :-)
> nobody uses this feature of qemu?
>
> Le ven. 27 août 2021 à 11:11, Pascal a écrit :
>
>> hello everybody,
>>
>>
e a écrit :
> On Thu, Sep 09, 2021 at 09:32:48AM +0200, Pascal wrote:
> > up² :-)
> > can someone just ping me to make me sure I'm posting on the qemu list ?
>
> Your question is reaching the list, but this mail ought to be informative:
>
> https://lists.gnu.org/arc
mea-culpa, I forgot to add this to my morning answer : *a big thank you to
all those who contribute to this great open source tool that is Qemu !*
Le ven. 10 sept. 2021 à 11:08, Peter Maydell a
écrit :
> On Thu, 9 Sept 2021 at 20:24, Eric Blake wrote:
> > There may be other less-risky ways for
hi everyone,
I'm trying in vain to install windows 11 in a virtual machine with qemu
without tpm support with the various registry keys found on the internet
(BypassTPMCheck for example) but I keep getting the message that my
(virtual) machine does not have the necessary prerequisites and cetera :
ig\BypassCPUCheck = 1
new dword32
Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig\BypassStorageCheck = 1
new dword32
Computer\HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig\BypassSecureBootCheck = 1
regards, lacsaP.
Le lun. 11 oct. 2021 à 10:48, Pascal a écrit :
> hi everyone,
> I'm tryi
just "> version='2.0'/>", with plain Qemu you need to manage everything
>> yourself, including control socket and state directory.
>>
>> Regards
>> Friedrich
>>
>> On 10/15/21 1:42 PM, Pascal wrote:
>> > hi everyone,
>> > here is the "environment" used (but it still doesn't work :-() :
>>
>>
hi,
could you provide all the commands that allowed you to run W$11 in a
virtual machine?
I have been trying in vain for a few days (
https://lists.nongnu.org/archive/html/qemu-discuss/2021-10/msg00016.html).
regards, lacsaP.
Le mar. 19 oct. 2021 à 16:05, Gabriel Dante Lima Chaves <
gabriellimac
briellimacha...@gmail.com> a écrit :
> Hi,
>
> I've used the exact commands that they recommend doing on quickemu git
> page https://github.com/wimpysworld/quickemu. It's as follows:
>
> $ quickget windows 11
> $ quickemu --vm windows-11.conf
>
> Hope it helps.
./11.disk \
-cdrom ./11.iso
regards, lacsaP.
Le lun. 18 oct. 2021 à 10:50, Pascal a écrit :
> hi,
>
> I simply prefer the manipulation of a few keys in the Windows registry at
> the time of installation to the "complex" Qemu boot (SecureBoot and TPM).
>
> however, I tri
hi,
may be with
-drive if=none,file=/dev/sdb,id=usb -device usb-storage,drive=usb,id=usb
and possibly add -snapshot
regards.
Le lun. 8 nov. 2021 à 17:23, Thomas Huth a écrit :
> On 07/11/2021 16.30, Marcin Zajączkowski wrote:
> > Hi. Having some (dracut-related) issues with a Fedora LiveCD ins
hi,
for some time, the `info usbhost` command returns an error if no USB host
device is shared beforehand.
this was not the case before.
(qemu) info usbhost
Command "info usbhost " is not available.
(qemu) device_add usb-host,hostbus=1,hostport=8,id=camera
(qemu) info usbhost
Bus 2, Addr 2, Port
hi,
I like VDE (https://github.com/virtualsquare/vde-2) to make my machines
communicate with each other.
regards, lacsaP.
Le mar. 21 déc. 2021 à 18:42, Daniel Dawson a
écrit :
> I have a couple of VNs that need to communicate through their own
> network. This network needs to not interact with t
hi,
may be with VNC on Windows...
regards, lacsaP.
Le mar. 4 janv. 2022 à 06:16, marco restelli a écrit :
> Dear all,
>I have an Ubuntu virtual machine which works fine in a linux host
> but gives a black screen in a Windows host. In Windows, I can switch
> to a different TTY and log in to t
hi,
may be with -device VGA,edid=on,xres=1280,yres=720
regards.
Le mer. 26 janv. 2022 à 13:53, chuck a écrit :
> Hi all
>
> I installed ubuntu qemu and leopard on the virt disk
>
> starting the powermac always displays 800x600.
>
> startup command:
>
> qemu-system-ppc -L pc-bios -boot c -M mac99
hi,
I discover this way (URI nvme://...) with your question.
according to the documentation (
https://qemu.readthedocs.io/en/latest/system/images.html?highlight=nvme#nvme-disk-images),
the access is exclusive : wouldn't there be another process that would
monopolize the device ?
regards, lacsaP.
L
hi,
could you provide the full command line used for this please ?
regards, lacsaP.
Le mer. 16 mars 2022 à 08:45, Johannes Zirngibl a écrit :
>
>
>
> *Gesendet:* Dienstag, 15. März 2022 um 11:09 Uhr
> *Von:* "Peter Maydell"
> *An:* "Johannes Zirngibl"
> *Cc:* qemu-discuss@nongnu.org
> *Betreff
hi,
`-t` switch for persistence (for me - `-p` is for port number).
`qemu-nbd -c` operate as a "local" server.
`qemu-nbd` still running : use `ps ax | grep nbd` and/or `ss -p | grep nbd`
to see it.
regards, lacsaP.
Le ven. 29 avr. 2022 à 02:40, Connor Kuehl a écrit :
> re-adding the list
>
> O
`qemu-nbd -c` operate as a "local" server/client.
Le ven. 29 avr. 2022 à 09:58, Pascal a écrit :
> hi,
>
> `-t` switch for persistence (for me - `-p` is for port number).
> `qemu-nbd -c` operate as a "local" server.
> `qemu-nbd` still running : use `ps ax | g
upposed to.
>
> Reading the man page I just expected to see it available (via an nbd
> client) on port 10809as well as /dev/nbd0 via the usual filesystem
> interfaces.
>
> ( So I tried with -re 2 (read-only , 2 users ) out of curiosity and stuff
> broke ... )
>
> Unless
hi,
my system is a Linux (5.10.83) with SystemD (249.7) and Qemu (6.1.0) and
I've a poor small Bash script:
#!/usr/bin/bash
systemd-cat -p warning <<< "script running..."
qemu-nbd -r -s -f raw -c /dev/nbd0 /dev/sdb |& systemd-cat -p warning
after loading nbd module, if I plug a blank disk (/dev/
hi,
after several checks, everything seems to be correctly configured...
could it be systemd (udev) that kills qemu-nbd after the script is finished
?
regards, lacsaP.
Le jeu. 19 mai 2022 à 17:09, Eric Blake a écrit :
> On Thu, May 19, 2022 at 04:40:27PM +0200, Pascal wrote:
>
hi,
*as for my other thread posted yesterday (kernel: block nbd0: shutting down
sockets), I don't know if the problem is directly related to qemu-nbd but I
post on this one because it occurs during its use : thank you for
redirecting me if needed.*
my system is a Linux (5.10.83) with SystemD (249
gets killed.
nothing else appears about nbd after the kernel message.
regards, lascaP.
Le jeu. 19 mai 2022 à 17:09, Eric Blake a écrit :
> On Thu, May 19, 2022 at 04:40:27PM +0200, Pascal wrote:
> > hi,
> >
> > my system is a Linux (5.10.83) with SystemD (249.7) and Qemu (
and here is the journalctl extract (one hair shorter) of the system started
again with the debug kernel parameter and the script called manually :
00:00:09 kernel: usb 2-3: new SuperSpeed Gen 1 USB device number 4 using
xhci_hcd
00:00:09 systemd-udevd[216]: 2-3: Device is queued (SEQNUM=2255, ACTI
hi,
I play to emulate the Raspberry Pi and, to avoid having to wait for the
(re)start of my slow VM, I recorded a snapshot at the end of the first boot.
but when I reload this snapshot, I have a lot of error messages (EXT4-fs
error (device mmcblk0p2) ... reading directory lblock 0) and I cannot us
hi,
I'm on a corporate network that is filtered (proxy) and I need to run some
tests on a W11 virtual machine that needs to have direct access to the
Internet.
I set up this configuration and route everything that comes out of tap0 to
wlan0 and then to Internet :
-
hi,
may be your USB SSD is attached to your host and can't be added to your W11
guest ?
*(ps: I don't know virt-manager, I'm using qemu from command line)*
*regards, lacsaP.*
Le lun. 26 déc. 2022 à 21:37, Ernesto Pozzoni a
écrit :
> Hello,
>
> I would be grateful if you could help me.
> My virt
hi,
I don't know if your VMs are dead but sr0 is related to the (virtual)
optical disk.
regards.
Le ven. 6 janv. 2023 à 15:58, Jean-Philippe Combe a
écrit :
> Hello everyone,
>
> I'm new here, I'm from France and I use QEMU/KVM for about 1 month
>
> I did install QEMU/KVM on a laptop with Debian
79 matches
Mail list logo
