Re: Accelerator in ARM-based macOS

[Simon Becherer]

Am 26.02.24 um 11:33 schrieb Serdar Bahar:

Hello,

I'm a newbie in QEMU and I'm using it on an Apple Silicon macOS (ARM-based). I use the default accelerator tcg to run a virtual machine with Ubuntu but it is quite slow. I tried commands like "-enable-kvm" or "-accel 
xyz"  but every one of them (except tcg) returned the message "invalid accelerator" (I guess none of them are compatible with an ARM-based macOS). Do you have any suggestions for me to have a faster experience in my 
virtual machine? Again, I'm very new to QEMU and I'm trying it because other options are either not compatible with my computer or are paid and I apologize if my question barely makes sense.


Thank you,
Serdar Bahar


if i understand you correct,
your host is arm based and your guest is
i86-64 based?
as far as i know, accelerating is only working
if host and guest has the same processor-family.
maybe i am wrong, i am only an user.
i do not know if ubuntu is available in a arm based
version, if yes, then i would use this version and try
to use the acceleration.


--
www.becherer.de




OpenPGP_signature
Description: OpenPGP digital signature

Re: difference between command line and virtual machine manager

[Simon Becherer]

Am 08.09.23 um 12:41 schrieb w...@gmx.com:

I am a newbie when it comes to QEMU/KVM. So bear with my questions.
To explain what I am doing, I am a ham radio operator, and need to run Winlink radio email and VARA in Windows. That is all I use windows for. Wine is not sufficient to run it for some reason that I am unable to 
fathom. Therefore, I have had to resort to the Virtual Machine.

Now on to the reason for this post:
My host is a fairly recent Linux Mint 21.1. My Guest is a Windows 10. My usual method is to bring up Virtual Machine Manager, and run Windows from there. It works great UNTIL I try to use the radios' USB port for 
data communications.
The radio has either a C-Media chipset or a cp210 type chipset (depending upon the radio). It has the quality of being BOTH a USB audio, AND 1 or 2 serial ports (for CAT control and PTT). What I need to do, is to 
pass through both the audio part and the serial port(s) part as well.
But they might not be present, if the particular radio is not on. Which brings me to my 2nd question, how do I start up the VM without them, if I am not plugged in to the radio's USB port. And then be able to run the 
VM when they ARE plugged in. Which leads me to, can I run this whole thing via the command line with or without the particular USB port, and how do I create the command line version from the Virtual Machine Manager?

So in summary I have 3 questions:
1. How to pass through the USB device in question (both audio and serial) ?
2. How to make it all variable (sometimes one radio vs the other will be 
plugged in, and sometimes none at all) ?
3. If different CLI versions have to be made depending upon #2 above, how do I 
create that from what I have in the Virtual Machine Manager?
I hope this ramble makes some sense to someone at 5:00 in the morning!
Thank you for taking the time to read this, and look forward to your answers.
Jerry


Maybe i do not completely understand, but what i do:

1+2)
i use virtmanager and there is a option to bypass usb-ports
inside the "pull down menues". i do this for some usb-dongels
the host-port(s) can be used, or not, and so its seen inside the
vm or not. in my case, 2 usb dongels are always plugged in
and i switch between this 2, because otherwise my old windows
software will only see one of them (lsusb did not see any difference
between the dongels).
but if i remember correct its also possible to plug it in,
and after that connect via the virt manager the usb-port.
its a little tricky to set the host system to do it, at least
in opensuse. - i have it somewhere written down how to configure
it (for opensuse) but i have to search if you are interested in.

3) the commandline virt manager is using you will find by
ps fax |grep qemu

simoN






Extra Ham Operator: WF5W
Registered Linux User: 275424
3D designer

The most exciting phrase to hear in science - the one that heralds new discoveries - is not 
"Eureka!" but "That's funny...". - Isaac. Asimov




OpenPGP_signature
Description: OpenPGP digital signature

Re: Windows VM's getting hung up on boot

[Simon Becherer]

Am 28.08.23 um 17:13 schrieb Jay Lepore:
I have had an ongoing though occassional problems with Windows failing to reboot and getting stuck right here.  I am guessing it comes after some kind of forced reboot during an unattended Windows update but that 
still doesn't explain the hang.


Has anyone else grappled with this and found the cause of it?

What sayeth the group?

--
Sincerely,

Jay

Jay Lepore
CompuMatter
*Office*: 360 299 2428 | *Cell*: 360 202 0434
*Email*: j...@compumatter.com
/If you are satisfied with your service, please consider providing us a social 
media review at https://compumatter.com/reviews
...If you are not, please let me know so I can make it better/




If its tumbleweed,
and you have an amd processor

then look here:

https://bugzilla.opensuse.org/show_bug.cgi?id=1214628

with different posibilitys to fix.

simoN




--
www.becherer.de




OpenPGP_signature
Description: OpenPGP digital signature

Re: qemu 8.0.4 windows xp not working

[Simon Becherer]

BUG CREATED:

https://bugzilla.opensuse.org/show_bug.cgi?id=1214628

simoN


Am 25.08.23 um 12:28 schrieb Simon Becherer:

Am 25.08.23 um 11:22 schrieb Simon Becherer:

Hi,

is there a known bug for:

my windows xp qemu boxes (host is opensuse tumbleweed amd processor)
will not start any more after updating to qemu 8.0.4

old linux (suse 10) starts, and windows 10 starts.

and if, is there a work around?


thanks,

simoN



i tried also a new installation of "windows xp professionel service pack3 cd"
stops before setup, similar as my old windows after loading some drivers

the line (autogenerated from libvirt) of my installation try is attached here:

  1470 ?    Ssl    0:03 /usr/sbin/virtqemud --timeout 120
  3472 pts/7    S+ 0:00  |   \_ grep --color=auto qemu
  3376 ?    Sl 0:21 /usr/bin/qemu-system-x86_64 -name guest=winxp,debug-threads=on -S -object 
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-winxp/master-key.aes"} -machine pc-i440fx-8.0,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram,hpet=off,acpi=on 
-accel kvm -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff -m size=786432k -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":805306368} -overcommit mem-lock=off -smp 
2,sockets=2,cores=1,threads=1 -uuid c94ea441-c095-4263-9af0-f28a931dea70 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=28,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device 
{"driver":"ich9-usb-ehci1","id":"usb","bus":"pci.0","addr":"0x5.0x7"} -device {"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pci.0","multifunction":true,"addr":"0x5"} -device 
{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pci.0","addr":"0x5.0x1"} -device {"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pci.0","addr":"0x5.0x2"} -device 
{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x6"} -blockdev 
{"driver":"file","filename":"/var/lib/libvirt/images/winxp.qcow2","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":true},"auto-read-only":true,"discard":"unmap"} -blockdev 
{"node-name":"libvirt-2-format","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":true},"driver":"qcow2","file":"libvirt-2-storage","backing":null} -device 
{"driver":"ide-hd","bus":"ide.0","unit":0,"drive":"libvirt-2-format","id":"ide0-0-0","bootindex":2,"write-cache":"on"} -blockdev 
{"driver":"file","filename":"/home/simon/kvm/images-backup/winxp-wincam1/win_xp_prof_sp3.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev 
{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"} -device {"driver":"ide-cd","bus":"ide.0","unit":1,"drive":"libvirt-1-format","id":"ide0-0-1","bootindex":1} -netdev 
{"type":"tap","fd":"29","id":"hostnet0"} -device {"driver":"e1000","netdev":"hostnet0","id":"net0","mac":"52:54:00:30:0a:2e","bus":"pci.0","addr":"0x3"} -chardev pty,id=charserial0 -device 
{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0} -chardev spicevmc,id=charchannel0,name=vdagent -device 
{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"com.redhat.spice.0"} -device {"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"} -audiodev 
{"id":"audio1","driver":"spice"} -spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on -device 
{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x2"} -device 
{"driver":"intel-hda","id":"sound0","bus":"pci.0","addr":"0x4"} -device {"driver":"hda-duplex","id":"sound0-codec0","bus":"sound0.0","cad":0,"audiodev":"audio1"} -chardev spicevmc,id=charredir0,name=usbredir -device 
{"driver":"usb-redir","chardev":"charredir0","id":"redir0","bus":"usb.0","port":"2"} -chardev spicevmc,id=charredir1,name=usbredir -device 
{"driver":"usb-redir","chardev":"charredir1","id":"redir1","bus":"usb.0","port":"3"} -device {"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x7"} -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on



simoN



OpenPGP_signature
Description: OpenPGP digital signature

Re: qemu 8.0.4 windows xp not working

[Simon Becherer]

Am 25.08.23 um 11:22 schrieb Simon Becherer:

Hi,

is there a known bug for:

my windows xp qemu boxes (host is opensuse tumbleweed amd processor)
will not start any more after updating to qemu 8.0.4

old linux (suse 10) starts, and windows 10 starts.

and if, is there a work around?


thanks,

simoN



i tried also a new installation of "windows xp professionel service pack3 cd"
stops before setup, similar as my old windows after loading some drivers

the line (autogenerated from libvirt) of my installation try is attached here:

 1470 ?Ssl0:03 /usr/sbin/virtqemud --timeout 120
 3472 pts/7S+ 0:00  |   \_ grep --color=auto qemu
 3376 ?Sl 0:21 /usr/bin/qemu-system-x86_64 -name guest=winxp,debug-threads=on -S -object 
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-winxp/master-key.aes"} -machine pc-i440fx-8.0,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram,hpet=off,acpi=on 
-accel kvm -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff -m size=786432k -object {"qom-type":"memory-backend-ram","id":"pc.ram","size":805306368} -overcommit mem-lock=off -smp 
2,sockets=2,cores=1,threads=1 -uuid c94ea441-c095-4263-9af0-f28a931dea70 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=28,server=on,wait=off -mon chardev=charmonitor,id=monitor,mode=control -rtc 
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device 
{"driver":"ich9-usb-ehci1","id":"usb","bus":"pci.0","addr":"0x5.0x7"} -device {"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pci.0","multifunction":true,"addr":"0x5"} -device 
{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pci.0","addr":"0x5.0x1"} -device {"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pci.0","addr":"0x5.0x2"} -device 
{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.0","addr":"0x6"} -blockdev 
{"driver":"file","filename":"/var/lib/libvirt/images/winxp.qcow2","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":true},"auto-read-only":true,"discard":"unmap"} -blockdev 
{"node-name":"libvirt-2-format","read-only":false,"discard":"unmap","cache":{"direct":false,"no-flush":true},"driver":"qcow2","file":"libvirt-2-storage","backing":null} -device 
{"driver":"ide-hd","bus":"ide.0","unit":0,"drive":"libvirt-2-format","id":"ide0-0-0","bootindex":2,"write-cache":"on"} -blockdev 
{"driver":"file","filename":"/home/simon/kvm/images-backup/winxp-wincam1/win_xp_prof_sp3.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev 
{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"} -device {"driver":"ide-cd","bus":"ide.0","unit":1,"drive":"libvirt-1-format","id":"ide0-0-1","bootindex":1} -netdev 
{"type":"tap","fd":"29","id":"hostnet0"} -device {"driver":"e1000","netdev":"hostnet0","id":"net0","mac":"52:54:00:30:0a:2e","bus":"pci.0","addr":"0x3"} -chardev pty,id=charserial0 -device 
{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0} -chardev spicevmc,id=charchannel0,name=vdagent -device 
{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"com.redhat.spice.0"} -device {"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"} -audiodev 
{"id":"audio1","driver":"spice"} -spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on -device 
{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pci.0","addr":"0x2"} -device 
{"driver":"intel-hda","id":"sound0","bus":"pci.0","addr":"0x4"} -device {"driver":"hda-duplex","id":"sound0-codec0","bus":"sound0.0","cad":0,"audiodev":"audio1"} -chardev spicevmc,id=charredir0,name=usbredir -device 
{"driver":"usb-redir","chardev":"charredir0","id":"redir0","bus":"usb.0","port":"2"} -chardev spicevmc,id=charredir1,name=usbredir -device 
{"driver":"usb-redir","chardev":"charredir1","id":"redir1","bus":"usb.0","port":"3"} -device {"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.0","addr":"0x7"} -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on



simoN

--
www.becherer.de



OpenPGP_signature
Description: OpenPGP digital signature

qemu 8.0.4

[Simon Becherer]

Hi,

is there a known bug for:

my windows xp qemu boxes (host is opensuse tumbleweed amd processor)
will not start any more after updating to qemu 8.0.4

old linux (suse 10) starts, and windows 10 starts.

and if, is there a work around?


thanks,

simoN



--
HINWEIS:
Wenn Sie diese "reintext" Mail mit Outlook
oeffnen kann es sein, dass Outlook
diese mail nicht korrekt anzeigt.
Das ist ein fehler oder eine Misskonfiguration
in Outlook. Informieren Sie ihren
Systemadministrator.

==

B e c h e r e r GmbH
Sondermaschinenbau
Mauermattenstrasse 22
79183 Waldkirch
Germany

Tel.: (+49) (0)7681 3134
Fax:  (+49) (0)7681 4378
Mail: i...@becherer.de
Web:  www.becherer.de

USt-ID-Nr.: DE 814912198
Registergericht: Freiburg HRB 701860
Geschaeftsfuehrer:
Dipl.-Ing. (FH), EWE   Simon H. Becherer
Gerichtsstand / Sitz: Waldkirch

Es gelten ausschliesslich unsere allgemeinen Liefer-
und Zahlungsbedingungen / Einkaufsbedingungen:
www.becherer.de/AGB


OpenPGP_signature
Description: OpenPGP digital signature

Re: How to enlarge qemu display ?

[Simon Becherer]

Am 07.11.22 um 16:42 schrieb Pierre Couderc via:

> 
> I have never gone in virt-manager, but I suppose that there sould be 
> corresponding  native instruction...
> 
i changed about 3 years in past from my shellscripts to virt-manager
and i have never repented it.

simoN

-- 
www.becherer.de




signature.asc
Description: OpenPGP digital signature

Re: How to enlarge qemu display ?

[Simon Becherer]

Am 07.11.22 um 13:52 schrieb Pierre Couderc via:
> 
> On 11/7/22 12:10, Simon Becherer wrote:
>>
>> Am 07.11.22 um 10:49 schrieb Pierre Couderc via:
>>> I use a XP guest  in qemu on  linux.
>>>
>>> I use a 4K monitor and my 800x600 XP windows is very very small, lost in 
>>> the 4K monitor.
>>>
>>> I do not want  to change my 800x600 size nor my monitor.
>>>
>>> But I would like to enlarge the XP window so that a XP pixel be mapped on 4 
>>> monitor pixels, or even if possible on 2 or 2.5 or 3 pixels.
>>>
>>> Is it possible...?
>>>
>>> Thanks for any help !
>>>
>>> PC
>>
>> If you use "virt-manager" (and spice for display) on kde
>> simply klick on the window and zoom/stretch it.
>> for this you have to set inside the menu
>> "view" -> "scale display" -> "always".
>>
>> i think i remember, this has to set at the host
>> machine to work, only over ssh it will not work.
>> could be the problem that i have opened it always
>> at serveral machines at once
>> (if i remember correct)
>> once set, you will be able
>> to zoom like every other kde/plasma also if you
>> start like:
>> ssh -X thehostmachine LANGUAGE=en_US /usr/bin/virt-manager
>>
>> and by the way, spice display is much faster than vnc,
>> (nearly) no delay.
>>
>> simoN
> Thank you very much, I am not under kde...
> 
The main thing is "virt-manager" (where you have to make
the "view" setting, i think it should also work with any
other desktop who is able to size windows.

simoN


-- 
www.becherer.de




signature.asc
Description: OpenPGP digital signature

Re: How to enlarge qemu display ?

[Simon Becherer]

Am 07.11.22 um 10:49 schrieb Pierre Couderc via:
> I use a XP guest  in qemu on  linux.
> 
> I use a 4K monitor and my 800x600 XP windows is very very small, lost in the 
> 4K monitor.
> 
> I do not want  to change my 800x600 size nor my monitor.
> 
> But I would like to enlarge the XP window so that a XP pixel be mapped on 4 
> monitor pixels, or even if possible on 2 or 2.5 or 3 pixels.
> 
> Is it possible...?
> 
> Thanks for any help !
> 
> PC


If you use "virt-manager" (and spice for display) on kde
simply klick on the window and zoom/stretch it.
for this you have to set inside the menu
"view" -> "scale display" -> "always".

i think i remember, this has to set at the host
machine to work, only over ssh it will not work.
could be the problem that i have opened it always
at serveral machines at once
(if i remember correct)
once set, you will be able
to zoom like every other kde/plasma also if you
start like:
ssh -X thehostmachine LANGUAGE=en_US /usr/bin/virt-manager

and by the way, spice display is much faster than vnc,
(nearly) no delay.

simoN

-- 
www.becherer.de



signature.asc
Description: OpenPGP digital signature

Re: External snapshots and using qemu without libvirt

[Simon Becherer]

Am 13.09.21 um 16:34 schrieb Leek, Jim:
> I'm still messing about with qemu snapshots.  I have internal snapshots 
> working OK.  But I read this in the RHEL documentation: "Important: Red Hat 
> recommends the use of external snapshots." Then on a later page I found this: 
> "However, external snapshots are currently not fully implemented on Red Hat 
> Enterprise Linux 7, and are not available when using virt-manager."Ha!
> 
> Maybe external snapshots will work if I run qemu without libvirt? But I'm 
> having trouble getting that to work as well.  I found this page and followed 
> the instructions: 
> https://developers.redhat.com/blog/2020/03/06/configure-and-run-a-qemu-based-vm-outside-of-libvirt
>  (although he talks about qemu-system-x86_64 and I'm using qemu-kvm, but I 
> hope that doesn't make any difference.)
> 
> But I can't get it to work.  I've tried a number of modifications, and the 
> command line below launches the VM, but I can't access it.  No screen pops 
> up, and I can't get there via ssh.  If I take off the last lines about the 
> display it will say I can use VNC ::1:5900, but when I connect there it with 
> a VNC client it just says "guest has not initialized display yet."
> 
> Anybody have any ideas on any of this?
> Thanks
> 
> Here's the command line I've tried.  The removing the last 2 arguments does 
> change the display behavior, but not to any particular benefit:
> #! /bin/sh 
> export LC_ALL=C 
> export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin 
> export HOME=/var/lib/libvirt/qemu/domain-6-centos8_3 
> export XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-6-centos8_3/.local/share 
> export XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-6-centos8_3/.cache 
> export XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-6-centos8_3/.config 
> export QEMU_AUDIO_DRV=spice 
> /usr/libexec/qemu-kvm \
> -name guest=centos8_3,debug-threads=on \
> -S \
> -enable-fips \
> -machine pc-q35-rhel8.2.0,accel=kvm,usb=off,vmport=off,dump-guest-core=off \
> -cpu 
> Skylake-Server-IBRS,ss=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,clflushopt=on,umip=on,pku=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,skip-l1dfl-vmentry=on,pschange-mc-no=on
>  \
> -m 24000 \
> -overcommit mem-lock=off \
> -smp 2,sockets=2,cores=1,threads=1 \
> -uuid 8dd20f24-3e31-464c-956e-67d3d9f2a83c \
> -no-user-config \
> -rtc base=utc,driftfix=slew \
> -global kvm-pit.lost_tick_policy=delay \
> -no-hpet \
> -no-shutdown \
> -global ICH9-LPC.disable_s3=1 \
> -global ICH9-LPC.disable_s4=1 \
> -boot strict=on \
> -device 
> pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
>  \
> -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 \
> -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 \
> -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
> -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
> -device pcie-root-port,port=0x15,chassis=6,id=pci.6,bus=pcie.0,addr=0x2.0x5 \
> -device pcie-root-port,port=0x16,chassis=7,id=pci.7,bus=pcie.0,addr=0x2.0x6 \
> -device pcie-root-port,port=0x17,chassis=8,id=pci.8,bus=pcie.0,addr=0x2.0x7 \
> -device pcie-pci-bridge,id=pci.9,bus=pci.1,addr=0x0 \
> -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 \
> -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 \
> -blockdev 
> '{"driver":"file","filename":"/home/leek2/qemu/rhel8_1-clone-1.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}'
>  \
> -blockdev 
> '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}'
>  \
> -device 
> virtio-blk-pci,scsi=off,bus=pci.4,addr=0x0,drive=libvirt-1-format,id=virtio-disk0,bootindex=1
>  \
> -device 
> virtio-net-pci,netdev=hostnet0,id=net0,mac=6c:2b:59:e9:44:49,bus=pci.7,addr=0x0
>  \
> -netdev bridge,id=hostnet0,br=virbr0 \
> -chardev spicevmc,id=charchannel0,name=vdagent \
> -device 
> virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
>  \
> -device virtio-balloon-pci,id=balloon0,bus=pci.5,addr=0x0 \
> -object rng-random,id=objrng0,filename=/dev/urandom \
> -device virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.6,addr=0x0 \
> -msg timestamp=on \
> -device 
> qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1
>  \
> -spice 
> port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
> 


Without checking all of your config:
> -spice 
> port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
should be: disable-ticketing=on

i would suggest you fire up your quemu with libvirt and then check the 
generated startline
with
ps fax |grep qemu

regards,

simoN

-- 
www.becherer.de





signature.asc
Description: OpenPGP digital signature

Re: Virtual FAT disk images

[Simon Becherer]

Yes,
as i know this ist the qemu list,
but as i see from the response (i am on this
list since 5 month), its more or less
developement and only if you get "luck"
a answer for "simple" user questions here.

by the way, what ist your cc quemu-bl...@nonmguru.org

simoN

Am 09.09.21 um 09:32 schrieb Pascal:
> 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,
> 
> 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.
> 
> /usr/bin/qemu-system-x86_64 -accel kvm -machine q35 -m 1024 -device 
> nec-usb-xhci -device usb-tablet -cpu qemu64,kvm=off -parallel null -serial 
> mon:stdio -hda windows.disk -hdb fat:rw:/tmp/test/
> 
> access to the E: drive is extremely slow and the system events report 
> many storahci (129: reinit \device\RaidPort0 sent) and disk (153: I/O @0x3f 
> on disk 1 \device\0001f replayed) warnings.
> 
> regards.
> 

-- 
www.becherer.de





signature.asc
Description: OpenPGP digital signature

Re: Backing up Windows Guest

[Simon Becherer]

Am 27.07.21 um 18:08 schrieb Chris Moody:
> Hi all,
> 
> Thinking of doing a distrohop, one issue I've had in the past when doing this 
> is the Windows seems to know that its environment has changed causing issues 
> with its registration.
> 
> Is there a way to backup this file in such a way that Windows won't know its 
> running under a different Host OS?
> 
> Thanks in advance for your help,
> 
> Chris
> 
> 

Hi chris,

i asked 2 times at this list how to stuck the virtual hardware / environement 
to do not change
when qemu is updated. i get only one "+" but no other response for a solution.
if you find a solution or anybody who could answer, please tell me/us.


simoN




-- 
www.becherer.de



signature.asc
Description: OpenPGP digital signature

Again, qemu changed virtual hardware

[Simon Becherer]

Hi, i like to ask again here:

how did i fix the virtual hardware that quemu will after updates
still send the guests the same hardware as before??

i updated today to 6.0.0-26.1 (opensusetumbleweed)

windows xp: lost the network controller, but has a identical new (e1000) 
network controller
   found, so i have to set up it new.

windows 10: a propetary software lost the licence because of the update of the 
linux qemu host.
i have to order new key.


how could i prevent qemu from doing that AND hold my system up to date
-> not updating qemu is not a solution.

start line from win10 (libvirt)

/usr/bin/qemu-system-x86_64 -name guest=win_10_profirst,debug-threads=on -S 
-object 
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-1-win_10_profirst/master-key.aes"}
-machine 
pc-q35-4.2,accel=kvm,usb=off,vmport=off,dump-guest-core=off,memory-backend=pc.ram
 -cpu
EPYC-IBPB,x2apic=on,tsc-deadline=on,hypervisor=on,tsc-adjust=on,arch-capabilities=on,xsaves=on,cmp-legacy=on,perfctr-core=on,clzero=on,xsaveerptr=on,virt-ssbd=on,npt=on,nrip-save=on,svme-addr-chk=on,rdctl-no=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,monitor=off,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff
-m 4096 -object 
{"qom-type":"memory-backend-ram","id":"pc.ram","size":4294967296} -overcommit 
mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 
539ae174-da2a-4e80-8ee6-d2e86b843304 -no-user-config -nodefaults
-chardev socket,id=charmonitor,fd=33,server=on,wait=off -mon 
chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew 
-global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global
ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device 
pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2
 -device
pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device 
pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device
pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device 
pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device 
qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device
virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -blockdev 
{"driver":"file","filename":"/home/simon/kvm/images/win_10_profirst.qcow2","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}
-blockdev 
{"node-name":"libvirt-2-format","read-only":false,"driver":"qcow2","file":"libvirt-2-storage","backing":null}
 -device ide-hd,bus=ide.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=1 
-device
ide-cd,bus=ide.1,id=sata0-0-1 -netdev tap,fd=35,id=hostnet0 -device 
e1000e,netdev=hostnet0,id=net0,mac=52:54:00:8c:08:86,bus=pci.1,addr=0x0 
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev 
spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -device
usb-tablet,id=input0,bus=usb.0,port=1 -audiodev id=audio1,driver=spice -spice 
port=5900,addr=127.0.0.1,disable-ticketing=on,image-compression=off,seamless-migration=on
 -device
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1
 -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b -device
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0,audiodev=audio1 -chardev 
spicevmc,id=charredir0,name=usbredir -device 
usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev
spicevmc,id=charredir1,name=usbredir -device 
usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device 
virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on


simoN

-- 
www.becherer.de




signature.asc
Description: OpenPGP digital signature

Re: Windows 9x - which graphic?

[Simon Becherer]

Am 06.06.21 um 14:19 schrieb Kamil Jońca:
> 
> I try to install my windows 9x instances under qemu. Although
> installation finished successuflly, and I can log in into newly
> installed guest I cannot achieve an graphic mode better than 640x480 (in
> particular I would use 1024x768)
> I tried minport vbe driver
> (https://web.archive.org/web/20191129030225/https://bearwindows.zcm.com.au/vbe9x.htm#2)
> with cirrus/vga/vmga card 
> and cirrus driver with cirrus card - but without sucess.
> Both 95 and 98 hangs during shutting down :(
> 
> Any hints?
> KJ
> 
> 

I have not used win98 boxes since 4? years, but before,
i have used win98 with cirrus, and if i remember correct also
vesa. 1024x768.
as i know i have not had problems. but i do not remember exactly
if i have installed a fix for win98 shutdown problem. there must
be somewhere a small microsoft fix for this. (not related to emulations,
and i do not remember what was the cause for the shutdown problem)

simoN


-- 
www.becherer.de





signature.asc
Description: OpenPGP digital signature

Re: shared disk (DOS)

[Simon Becherer]

Am 13.04.21 um 12:02 schrieb Tomas By:

> All I need is 2-4 DOS instances sharing a directory somewhere.
> /Tomas
> 
why not use "dosbox" (or a other dos emulation)
and forget qemu for this purpose.

simoN


-- 
www.becherer.de





signature.asc
Description: OpenPGP digital signature

Re: How to make a VM guest look like just another metal machine on my LAN?

[Simon Becherer]

Hi,



Am 21.02.21 um 09:46 schrieb Steve Litt:
> Hi all,
> 
.
.
.

> 
> Steve Litt 
> Autumn 2020 featured book: Thriving in Tough Times
> http://www.troubleshooters.com/thrive
> 

i have only partly read your mail.
but i think it sounds like a problem similar to one i have had
with the "firewalld" and ssh from outside to a virtual machine.
(a year or so in past)

(i am here at host opensuse tumbleweed and different virtual machines startet 
by virtmanager.
so i have set inside yast (host) the bridge device "br0" and have permanent set
the hardware-network-card (host) as a slave to this bridge. the connection to 
the guest will
be done automaticaly by virt-manager. no need to write a script.)
BUT i run into a routing problem, solved here:

i was following this:
https://superuser.com/questions/990855/configure-firewalld-to-allow-bridged-virtual-machine-network-access
in detail:
firewall-cmd --permanent --direct --passthrough ipv4 -I FORWARD -i br0 -j ACCEPT
firewall-cmd --permanent --direct --passthrough ipv4 -O FORWARD -i br0 -j ACCEPT
firewall-cmd --reload
this will create a file: /etc/firewalld/direct.xml
with the above entries.
i tested also then:
iptables-save  -f dateiname
iptables-restore -f dateiname
iptables -L
now there is a line more inside: -A FORWARD -i br0 -j ACCEPT
but i do not recall why i have done this. my working configuration did not have 
the last "-A" line inside.

hope this  will help you.
for test purpose i would (if possible inside your enviorement) stop the 
firewall (host) completely and check
if its then running. if its running, you know for sure its a firewall problem.

simoN

-- 
www.becherer.de




signature.asc
Description: OpenPGP digital signature

qemu change virtual hardware after update

[Simon Becherer]

Hi,

i am new here on this list, so if this problem was discussed/solved
somewhere else, please point me to it.

i use qemu (at the moment 5.2) with virt-manager on opensuse tumbleweed.

is there a way to prevent qemu from updating virtualized hardware inside
the virtualization?

as example: sometimes when qemu is updated, the virtual machines OS
(windows 10 or windows xp) find new "hardware"
and at least in windows xp i have now a huge amount of broken
(most is invisible inside system-control) hardware. (this machine
runs since 2011)
and of course the "fingerprint" of the system will change.

there is the parameter -machine pc-q35-4.2
inside my command line. i was thinking this will stay always at same
hardware. but this parameter is since 15.juni2020 (generation of the
libvirt xml file) inside.
but after an update of my system and of course with the system also
qemu, in jan. 2021, some components
(not only but also the networkadapter), inside qemu has changed.
the networkadapter is also inside the config line: e1000e.
but windows10 has found a new one (a new e1000e) and i have
had to set for the new adapter my fixed ipv4 adres.

this results in my main problem:

i see this virtual-hardware-updates at least two times in the last 2 years.

and it brakes for me my installation of a proprietary software in win10 who has
a copy protection. i have then always to make a phone call to the
software company and ask for new key-number.
that's annoying. (i own a permanent license for one computer but the computer
should not change the hardware) - the host did not change, but qemu (or libvirt)
(but libvirt has always the same xml file, so i think its qemu itself) changed
the virtual hardware.
and maybe sometimes in future the company will tell me to buy support for the 
software.
because the license did not include support or phone calls for new
license numbers.

stay on same hardware do not update software "or anything", that is one of the 
reasons i like to use a
virtualized environment. and of course to be portable with the emulation to 
move on at host side
the hard and software.

so what must i do to tell qemu "stay ALWAYS on hardware qemu version X.y never 
change it."

simoN

-- 
www.becherer.de




signature.asc
Description: OpenPGP digital signature