Le mar. 28 mars 2023 à 09:36, Thomas Huth a écrit :
>
> On 27/03/2023 21.52, Eric Nichols (DirWiz) via wrote:
> > Long time user, first time poster...
> >
> > My setup is simple. Debian host running qemu 7.2.0 and 2 guest (Windows
> > 2010 workstation & 2022 server). My goal is to setup a privat
and handle all this socket/mcast complexity
> internally and away from the OS. Bonus points if you could merge this
> new idea for hubport with SLIRP!
>
> Many thanks again!
> Eric
>
>
> On 3/28/23 6:05 AM, lacsaP Patatetom wrote:
> > Le mar. 28 mars 2023 à 09:36, Thomas
hi Qemu command line users,
`qemu-img` does not allow to have a light and tree-like view of a derived
image.
as I didn't find another solution on the Internet, I wrote this little bash
script which may be useful to some of you and which allows to obtain this :
$ qemu-img-tree /opt/virtual/test11
Le ven. 26 mai 2023 à 03:01, skylarmylar via a
écrit :
> Hi! I am looking for instruction about using command line QEMU-KVM to
> create VMs for testing Yubikey authentication of system initialization
> stages, logins, and processes. If anyone can tell me where to find the
> information I need to
`-nic none` (see here
https://qemu.readthedocs.io/system/invocation.html#hxtool-5)
Le mar. 5 déc. 2023 à 13:33, Talha Khan a écrit :
> Hello all,
> I want to build an instance of qemu(x86-64) without any network devices in
> the emulator (no nic,no netdev or anything). Im new to all these, any h
Le mar. 5 déc. 2023 à 13:50, lacsaP Patatetom a
écrit :
> `-nic none` (see here
> https://qemu.readthedocs.io/system/invocation.html#hxtool-5)
>
> Le mar. 5 déc. 2023 à 13:33, Talha Khan a écrit :
>
>> Hello all,
>> I want to build an instance of qemu(x86-64) withou
hi,
to quickly test my efi application `./esp/EFI/BOOT/BOOTX64.EFI`, I use the
following command `qemu-system-x86_64 -accel kvm -machine q35 -m 1024 -bios
/usr/share/edk2/x64/OVMF.fd -hda fat:./esp/ -snapshot` but it has recently
failed with the error message given in subject.
for various reasons
Le mer. 13 déc. 2023 à 12:24, Alberto Garcia a écrit :
> On Wed, Dec 13, 2023 at 11:46:51AM +0100, lacsaP Patatetom wrote:
> > to quickly test my efi application `./esp/EFI/BOOT/BOOTX64.EFI`, I use
> the
> > following command `qemu-system-x86_64 -accel kvm -machine q35 -m 102
Le mer. 13 déc. 2023 à 13:29, Narcis Garcia a
écrit :
> A FAT16 partition (0x06) can be as large as 2 GiB
>
>
> El 13/12/23 a les 12:23, Alberto Garcia ha escrit:
> > On Wed, Dec 13, 2023 at 11:46:51AM +0100, lacsaP Patatetom wrote:
> >> to quickly test my efi applicat
Le mer. 13 déc. 2023 à 14:57, Thomas Huth a écrit :
> On 13/12/2023 13.51, Alberto Garcia wrote:
> > On Wed, Dec 13, 2023 at 01:27:49PM +0100, Narcis Garcia wrote:
> >> A FAT16 partition (0x06) can be as large as 2 GiB
> >
> > That's why I say that there's probably a limitation in the QEMU vvfat
Le mer. 13 déc. 2023 à 17:32, Alberto Garcia a écrit :
> On Wed, Dec 13, 2023 at 04:33:00PM +0100, lacsaP Patatetom wrote:
> > having said that, and if you respect the constraints ("what you
> > should never do..."), vvfat is a really nice way of performing and
> >
Le ven. 15 déc. 2023 à 11:39, Alberto Garcia a écrit :
> On Fri, Dec 15, 2023 at 09:15:22AM +0100, lacsaP Patatetom wrote:
> > here's a little script following the exchanges above.
> > perhaps it will be useful to others...
>
> If you want a full disk image with its pa
hi,
when I want to offer a smartphone to my virtual machine, I have to attach
it as "device_add usb-host,hostbus=X,hostport=Y,id=Z" otherwise, I lose the
attachment on the virtual machine side when I switch the smartphone mode (MTP,
USB connection sharing, etc...).
to avoid having to manually bui
hi,
when using `qemu-img create`, why do I have to specify the format of the
base image ?
can't `qemu-img` detect it itself ?
I understand that I have to specify the format of the created image, but I
don't understand for the base image.
`qemu-img create -b base.img -f qcow2 new.img`
rather than
Le jeu. 25 avr. 2024 à 11:30, Peter Maydell a
écrit :
> On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom
> wrote:
> >
> > hi,
> >
> > when using `qemu-img create`, why do I have to specify the format of the
> base image ?
> > can't `qemu-img` detect
Le jeu. 25 avr. 2024 à 15:13, Jakob Bohm via a
écrit :
> On 2024-04-25 14:51, lacsaP Patatetom wrote:
> > Le jeu. 25 avr. 2024 à 11:30, Peter Maydell > <mailto:peter.mayd...@linaro.org>> a écrit :
> >
> > On Thu, 25 Apr 2024 at 09:55, lacsaP Patatetom
&
Le mar. 29 oct. 2024 à 16:09, lacsaP Patatetom a
écrit :
> Le mar. 29 oct. 2024 à 15:52, lacsaP Patatetom a
> écrit :
>
>> hi,
>>
>> in order to have “portable” VMs, I used to install them with Qemu's `-cpu
>> qemu64` option, but it turns out that the
Le mar. 29 oct. 2024 à 15:52, lacsaP Patatetom a
écrit :
> hi,
>
> in order to have “portable” VMs, I used to install them with Qemu's `-cpu
> qemu64` option, but it turns out that the Windows 11 24H2 installation CD
> no longer boots with this option : do you know whic
hi,
in order to have “portable” VMs, I used to install them with Qemu's `-cpu
qemu64` option, but it turns out that the Windows 11 24H2 installation CD
no longer boots with this option : do you know which CPU flag to use to
maintain the desired "portability"* ?
note that Windows 11 24H2 boots wit
hi,
here's some bash helpers around/for qemu, that I hope you'll find useful.
https://github.com/patatetom/qemu-helpers
regards, lacsaP.
Le mer. 20 nov. 2024 à 10:37, lacsaP Patatetom a
écrit :
> hi,
>
> I'd like to use an executable file as a configuration file for `qemu`
> using a shebang : let me explain.
>
> I currently store my configuration like this in `configuration.qemu` :
> ```
> -ar
hi,
I'd like to use an executable file as a configuration file for `qemu` using
a shebang : let me explain.
I currently store my configuration like this in `configuration.qemu` :
```
-argument
- argument -option
-etc...
```
and I call `qemu` like this and it works as expected :
`$ qemu $(
Le ven. 15 nov. 2024 à 15:21, Frantisek Rysanek
a écrit :
> > And, I have an idea: rather than refer to driver=qcow2 and
> > file.filename, how about referring to the loopback device (NBD) that
> > you already have, courtesy of qemu-nbd ? Would that perhaps circumvent
> > the file lock? ;-)
> >
>
Le ven. 15 nov. 2024 à 16:11, lacsaP Patatetom a
écrit :
> Le ven. 15 nov. 2024 à 15:21, Frantisek Rysanek
> a écrit :
>
>> > And, I have an idea: rather than refer to driver=qcow2 and
>> > file.filename, how about referring to the loopback device (NBD) that
>>
Le ven. 15 nov. 2024 à 13:35, Frantisek Rysanek
a écrit :
> > # qemu-nbd -c /dev/nbd0 file.qcow2
> > # mount /dev/nbd0p1 /mnt -o uid=me
> > $ # do some changes in /mnt/...
> >
> Are you sure the changes have made it to the underlying file?
> If you do an umount here, a sync() is guaranteed.
> If
Le jeu. 14 nov. 2024 à 17:00, Frantisek Rysanek
a écrit :
> > my image `fie.qcow2` is mounted elsewhere (nbd) and running
> > `qemu-system-x86_64 -snapshot -hda file.qcow2` fails with the error
> > "qemu-system-x86_64: -hda usb1.disk: Failed to get shared “write”
> > lock / Is another process usi
Le ven. 15 nov. 2024 à 14:00, lacsaP Patatetom a
écrit :
> Le ven. 15 nov. 2024 à 13:35, Frantisek Rysanek
> a écrit :
>
>> > # qemu-nbd -c /dev/nbd0 file.qcow2
>> > # mount /dev/nbd0p1 /mnt -o uid=me
>> > $ # do some changes in /mnt/...
>> >
&g
Le jeu. 14 nov. 2024 à 15:11, lacsaP Patatetom a
écrit :
> hi,
> what is the "relaxed" equivalent of the `-hda file.qcow2` command line
> argument to control file locking (`locking=off`) ?
> the documentation says that `-hda a` can be replaced by `-drive file=a`
>
Le jeu. 14 nov. 2024 à 16:15, lacsaP Patatetom a
écrit :
> Le jeu. 14 nov. 2024 à 15:11, lacsaP Patatetom a
> écrit :
>
>> hi,
>> what is the "relaxed" equivalent of the `-hda file.qcow2` command line
>> argument to control file locking (`locking=off`) ?
&
Le jeu. 14 nov. 2024 à 15:11, lacsaP Patatetom a
écrit :
> hi,
> what is the "relaxed" equivalent of the `-hda file.qcow2` command line
> argument to control file locking (`locking=off`) ?
> the documentation says that `-hda a` can be replaced by `-drive file=a`
>
hi,
what is the "relaxed" equivalent of the `-hda file.qcow2` command line
argument to control file locking (`locking=off`) ?
the documentation says that `-hda a` can be replaced by `-drive file=a` and
that locking can be controlled with the `locking` option of the `blockdev`
argument : how to link
hi,
what network configuration (HM/VM side) would you set up to capture/follow
a virtual machine's network traffic, forcing it to pass through tools such
as tshark/wireshark, dnsmasq or mitmproxy ?
the host machine (HM) is an ArchLinux.
regards.
32 matches
Mail list logo
