hi everybody
from brief few looks I took at some notes it seems advisable
to use"virtio" for both storage & network
my question would be, having it usual way:
-drive file="${imgFile}",index=0,media=disk
is it possible to simply switch over to "virtio"?
if yesthen how to do it, I'd presume one
also
how do
Red... SCSI controller
and
Red... pass-through controller
drivers differfrom one another?
how would this difference be reflected on guemu-host side?
On 01/29/13 15:15, lejeczek wrote:
hi everybody
from brief few looks I took at some notes it seems
advisable to use"virtio
hi everybody
a newbie here, hoping some experienced users/expert can
honestly answer this one question,
and I think I realize all other advantages libvirt offer but
simply performance,
does libvirt make a user pay penalty, even if only a small
amount, for using it when compared to raw qemu-k
hi everybody
I'm wondering if a following setup is supported in quemu:
having a vnc with a full control to the quest and spice-web
sharing this same desktop/connection,
so one could control the quest (via vnc) and others would be
spectators (view only) via spice-web
possible?
or any other wa
hi everybody
I'd like to ask around if Xeon Phis are any good for
passthrough?
Are there any plans for near future or maybe there are
already some success stories using this product?
many thanks,
P.
hi everybody, I tried to get a help on libvirt mailing list
but not luck, I hope maybe here?
I'm trying Qemu's watchdog.
My understanding was that hardware (here qemu's watchdog)
would take
action, eg. cold reboot) the system if there is no ping from
the OS watchdog, so I
thought stopping wat
hi all,
guys/gals, how do you do it?
team interfaces (physical) in the host and pass it to guest?
or host pass-through two NICs and team them in the guest?
and why?
many thanks
hi all
I wonder is your virtfs passthrough working?
I'm trying first time a pretty regular setup, and guests
mount that mount tag, I can list in a guest mountpoint's
content, I see files & dirs but when I try to list content
below, eg a subfolder in the mountpoint then it get denied.
Would you
Hi everybody.
I wonder if somebody would know bit more what to do or think
about this:
...
[Fri May 29 08:00:02 2020] tun: unexpected GSO type: 0x0,
gso_size 1368, hdr_len 66
[Fri May 29 08:00:02 2020] tun: 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
[Fri May 29 08:00:02 2020
Hi guys.
I have libvirtd to manage my VMs and it all works well
including backend to the storage being glusterfs, but when I
try something simple, for the first time, this:
-> $ qemu-img create -f qcow2
gluster://swir.direct:24007/VMs/fcos-node1.qcow2 20G
Formatting
'gluster://swir.direct:2
Hi guys.
I have libvirtd to manage my VMs and it all works well
including backend to the storage being glusterfs, but when I
try something simple, for the first time, this:
-> $ qemu-img create -f qcow2
gluster://swir.direct:24007/VMs/fcos-node1.qcow2 20G
Formatting
'gluster://swir.direct:2
Hi guys.
I am trying to backup qcow2s which are luks encrypted but I
fail and I wonder if it's my syntax being crooked or
something is not working in qemu(-img).
Non-encrypted qcow2 works fine and I only add encryption
bits to cmd line, here:
-> $ qemu-img create -f qcow2 -b -o
encrypt.key-
On 14/08/2021 11:19, Peter Maydell wrote:
On Sat, 14 Aug 2021 at 08:24, lejeczek wrote:
-> $ qemu-img create -f qcow2 -b -o
encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d
/00.GLUSTER-mnt/VMs3/enc.locallan.qcow2 -F qcow2
./enc.locallan.qcow2.bkp
qemu-img: Invalid image s
On 15/08/2021 13:17, Peter Maydell wrote:
On Sun, 15 Aug 2021 at 13:07, lejeczek wrote:
On 14/08/2021 11:19, Peter Maydell wrote:
On Sat, 14 Aug 2021 at 08:24, lejeczek wrote:
-> $ qemu-img create -f qcow2 -b -o
encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d
/00.GLUSTER-
On 16/08/2021 10:02, Peter Maydell wrote:
On Sun, 15 Aug 2021 at 17:26, lejeczek wrote:
On 15/08/2021 13:17, Peter Maydell wrote:
How about you say what command line(s) you tried that gave that
error message ?
Almost identical to the original, only take out 'options'
out and pu
Hi guys.
I am experiencing a peculiar situation where LIVE migration
between boxes:
A&B have Ryzen 5 3600
C has Ryzen 5 5600G
I highlight CPU bits as rest of the hardware & OS are virtually identical.
with 'virsh' I can:
1) LIVE migrate a OK:
between A & B
from C to A &| B
2) LIVE migrate sa
Hi guys.
Should 'info' fail as per the subject?
I mean - does it make sense to claim 'write' with 'info' - if that's
really what happens?
many thanks, L.
Hi guys.
In my centOSes, ver. 9 host and ver. 8 guests, I use
'i6300esb' which renders '/dev/watchdog1' to which I point
in /etc/watchdog.conf on VMs.
Now... my VMs(for whatever reasons) sometimes(to often in my
mind) get:
...
watchdog: BUG: soft lockup - CPU#0 stuck for xyzs! ...
...
When th
Hi guys
I'm trying to connect to an encrypted image but my fiddling
- as I never known this one - fails.
Very bare cmd fails:
-> $ qemu-nbd --connect=/dev/nbd0 /00-VMs/enc.ommie.qcow2
qemu-nbd: Failed to blk_new_open '/00-VMs/enc.ommie.qcow2':
Parameter 'encrypt.key-secret' is required for ci
On 31/03/2023 15:22, lejeczek wrote:
Hi guys
I'm trying to connect to an encrypted image but my
fiddling - as I never known this one - fails.
Very bare cmd fails:
-> $ qemu-nbd --connect=/dev/nbd0 /00-VMs/enc.ommie.qcow2
qemu-nbd: Failed to blk_new_open
'/00-VMs/en
Hi guys.
If by any chance Centos users, even better if
devel/packagers, traverse here - would you know why there is
no arm/64 emulation with default packages/repo?
I wonder if this something only Centos do/did - if indeed
that part is missing - or perhaps Qemu alone drifted /
floated that way
Hi Guys.
I see something like here:
-> $ gpg --verbose --keyserver hkp://keyserver.ubuntu.com
--recv-keys 7568D9BB55FF9E5287D586017AE645C0CF8E292A
gpg: Note: RFC4880bis features are enabled.
gpg: keyserver receive failed: Server indicated a failure
only in my VMs where underlying hardware hav
On 20/12/2023 16:09, lejeczek wrote:
Hi Guys.
I see something like here:
-> $ gpg --verbose --keyserver hkp://keyserver.ubuntu.com
--recv-keys 7568D9BB55FF9E5287D586017AE645C0CF8E292A
gpg: Note: RFC4880bis features are enabled.
gpg: keyserver receive failed: Server indicated a fail
hi guys.
Latest version 8.x ov ESXi fails - for me that is - to use
emulated disk/drive, fails with:
disk device does not support OSDATA
would anybody know if it's possible to "fix" this - without
passing-through?
many thanks, L.
Hi guys.
There is something in sroogle results, in general, about
this here:
Task failed on server: This host supports AMD-V, but the
AMD-V implementation is incompatible with VMware ESX.
Installer log files are located at /tmp/vcsaUiInstaller
This errors out when I try to deploy vCenter (w
25 matches
Mail list logo
