Re: SNP: qemu upstream vs AMD fork on kernel 6.11

2024-08-05 Thread Paolo Bonzini
AMD fork (https://github.com/AMDESE/qemu snp-latest) is not in line with the upstream kernel, for example: 66e7fbadfc8 i386/sev: Add KVM_EXIT_VMGEXIT handling for Page State Changes e9898385037 i386/sev: Add KVM_EXIT_VMGEXIT handling for Page State Changes (MSR-based) What problems are you seeing

Re: target/i386: fix pushed value of EFLAGS.RF

2024-06-10 Thread Paolo Bonzini
On Tue, Jun 11, 2024 at 12:39 AM Robert Henry wrote: > > > Paolo: > > Regarding your commit to QEMU > https://github.com/qemu/qemu/commit/69cb498c56263a5ae484fd4fef920d3d3eea04c8 > > Four years ago I reported a bug > https://gitlab.com/qemu-project/qemu/-/issues/249

Re: Why does the vmovdqu works for passthrough device but crashes for emulated device with "illegal operand" error (in x86_64 QEMU, -accel = kvm) ?

2024-03-04 Thread Paolo Bonzini
emulate (as opposed to, for example, GPU VRAM that is passed through). Thanks, Paolo Is your "program" just doing a memcpy() with an mmap() of the PCI BAR acquired through pci-sysfs or a userspace vfio-pci driver within the guest? In QEMU 4a2e242bbb30 ("memory: Don't use

Re: Segfault in hw/scsi/scsi-disk.c caused by null pointer

2022-08-12 Thread Paolo Bonzini
r old version of QEMU. Paolo

Re: romfile resize

2021-02-23 Thread Paolo Bonzini
u can create a dummy file with the right size, or copy it from the source. Paolo

Re: [QEMU TCG] Qeustion about the PCID Feature in TCG

2021-02-22 Thread Paolo Bonzini
field get set in cr3 but I am not sure it's the right one. I think it's the right one, yes. It works mostly by chance, but it should work for your use case. Paolo

Re: [QEMU TCG] Qeustion about the PCID Feature in TCG

2021-02-18 Thread Paolo Bonzini
a). In this case, everything seemingly works because QEMU is not checking reserved bits in CR3 and CR4 (see cpu_x86_update_cr3 and cpu_x86_update_cr4 in target/i386/helper.c). A smaller issue is that PCID without the INVPCID instruction makes little sense, so you would have to implement that as w

Re: Optimized clocksource with AMD AVIC enabled for Windows guest

2021-02-04 Thread Paolo Bonzini
are-accelerated EOI or interrupt injection. Paolo

Re: Optimized clocksource with AMD AVIC enabled for Windows guest

2021-02-02 Thread Paolo Bonzini
On 03/02/21 07:40, Kechen Lu wrote: From the above observations, trying to see if there's a way for enabling AVIC while also having the most optimized clock source for windows guest. You would have to change KVM, so that AVIC is only disabled if Auto-EOI interrupts are used. Paolo

Re: QEMU 5.1: Can we require each new device/machine to provided a test?

2020-05-15 Thread Paolo Bonzini
lpark of what you'd need. You can then stimulate keyboard or mouse devices via chardev (-serial msmouse), or run SCSI tests for MSD and UAS. Paolo

Re: QEMU participation to Google Season of Docs

2020-04-06 Thread Paolo Bonzini
he TOC to fit all the material in both categories would be the best outcome of our participation in GSoD. Paolo

Re: QEMU participation to Google Season of Docs

2020-04-01 Thread Paolo Bonzini
perhaps you could help by providing the text for our Summer of Code submission? Thanks, Paolo

Re: qemu-system-x86_64: -accel kvm:tcg: Don't use ':' with -accel, use -M accel=... for now instead

2019-11-25 Thread Paolo Bonzini
-M accel=kvm:tcg", it will continue to work and will be transparently converted to "-accel kvm -accel tcg". Thanks, Paolo Il lun 25 nov 2019, 21:20 Nir Soffer ha scritto: > On Mon, Nov 25, 2019 at 9:54 PM Nir Soffer wrote: > > > > We have automated tests ru

Re: How to initiate power-off in quest with new microvm machine type

2019-11-12 Thread Paolo Bonzini
the microvm machine type. I'm not entirely convinced that this is really > necessary, but if it makes people's life easier, it may be worth it. I think we should rather add a minimal i8042 device that can only do reset (but wouldn't be detected as i8042 by the guest). But if reboot=t works, we could also add it to the automatically-generated command line. Paolo

Re: [Qemu-discuss] [Qemu-devel] Handling signal of Qemu thread

2018-08-20 Thread Paolo Bonzini
rsions, QEMU can process the SIG_IPI synchronously in the CPU thread and set a flag that KVM_RUN reads (cpu->kvm_run->immediate_exit). On those new versions, the signal is never blocked and kvm_eat_signal() does not do sigtimedwait anymore, it just resets cpu->kvm_run->immediate_exit back to zero. Thanks, Paolo

Re: [Qemu-discuss] [Qemu-devel] Apple hypervisor.framework (hvf) availability

2018-02-08 Thread Paolo Bonzini
U developers use > Linux -- the BSDs and Windows hosts are also not very well > represented in the QEMU dev community. Indeed. However, Windows at least has Wine and it can also be virtualized if you have a legal license. If Apple wants to donate even oldish hardware to developers, I'm s

Re: [Qemu-discuss] [Qemu-devel] Apple hyphervisor.framework availability

2018-02-07 Thread Paolo Bonzini
ing/profiling the hvf accelerator to > improve it's performance and robustness? > > What can users do to provide information for developers to make such > improvements? No one is working on QEMU/HVF right now, I don't even own a computer that can run it. However I hope that the Android emulator developers take it up. Paolo

Re: [Qemu-discuss] Apple hyphervisor.framework availability

2017-11-27 Thread Paolo Bonzini
On 25/11/2017 11:48, Brendan Simon (eTRIX) wrote: > On 25/11/17 10:10 am, Brendan Simon (eTRIX) wrote: > >> On 24/11/17 11:39 pm, Paolo Bonzini wrote: >>> On 24/11/2017 12:58, Brendan Simon (eTRIX) wrote: >>>> Checked out the `hvf` branch, but it failed the b

Re: [Qemu-discuss] Apple hyphervisor.framework availability

2017-11-24 Thread Paolo Bonzini
On 24/11/2017 12:58, Brendan Simon (eTRIX) wrote: > > Checked out the `hvf` branch, but it failed the build.  Ran `mkdir build > ; cd build ; ../configure ; make` > > Am I missing some definitions or command line switches? No, I've pushed an updated version. Paolo

Re: [Qemu-discuss] Apple hyphervisor.framework availability

2017-11-23 Thread Paolo Bonzini
repository. hvf apparently hasn't been > merged into the upstream QEMU git repository yet. Right, more testing is welcome. Paolo

Re: [Qemu-discuss] [Qemu-devel] QEMU without X11 support

2017-10-15 Thread Paolo Bonzini
nographic is a shortcut for "-display none -machine graphics=off" 2) it changes the default character device backend from "vc:80Cx24C" (80x24 graphical console) to either "mon:stdio" or "stdio", except for the parallel port whose default becomes simply "null". Paolo

Re: [Qemu-discuss] changing from net to netdev with vde switches and double nics

2017-08-30 Thread Paolo
> On Wed, 30 Aug 2017 08:03:31 +0200 > Thomas Huth wrote: > > NET0="-net vde,vlan=0,sock=/var/run/vde.ctl00 -net > > nic,vlan=0,model=rtl8139,macaddr=$NIC0MAC" > > NET1="-net vde,vlan=1,sock=/var/run/vde.ctl01 -net > > nic,vlan=1,model=rtl8139,macaddr=$NIC1MAC" > > > > Now I guess this is im

Re: [Qemu-discuss] changing from net to netdev with vde switches and double nics

2017-08-29 Thread Paolo
s left orphan, because no other devices seems to be made aware that hubport_n exists, nor looks to me that they could be wired to it. Is there a feasible way to have the same network layout with netdev in place of net? Any hint on alternative ways to do it? Paolo

[Qemu-discuss] changing from net to netdev with vde switches and double nics

2017-08-28 Thread Paolo
Hello everyone, I'm at loss as to how to translate from net to netdev syntax the following lines: NET0="-net vde,vlan=0,sock=/var/run/vde.ctl00 -net nic,vlan=0,model=rtl8139,macaddr=$NIC0MAC -net tap,vlan=0,ifname=pub2,script=no,downscript=no" NET1="-net vde,vlan=1,sock=/var/run/vde.ctl01 -ne

Re: [Qemu-discuss] Windows-10 virtualization and nested virtualization

2016-04-06 Thread Paolo Bonzini
manpower. If somebody wants the feature enough that they will spend time looking at why it doesn't work, then that will help. Paolo

Re: [Qemu-discuss] Windows-10 virtualization and nested virtualization

2016-04-06 Thread Paolo Bonzini
pervisor flag is > needed. That is not what the error means. The error means that Hyper-V has failed to start. Paolo > > On Mon, 2016-04-04 at 17:35 -0400, Bandan Das wrote: >> Jeff Forbes mailto:jeff.for...@mail.nacon.com>> >> writes: >> >>> We have a Win

Re: [Qemu-discuss] TCP options ipv4 and ipv6 have no effect

2015-10-12 Thread Paolo Bonzini
On 12/10/2015 15:06, Sair, Umair wrote: > Paolo, thanks for the explanation :) > >> > Did you test the patch, and did it work for you? If so, it is customary >> > to reply with a line like "Tested by: Sair, Umair ". > Yes, it worked for me. Should I re

Re: [Qemu-discuss] TCP options ipv4 and ipv6 have no effect

2015-10-05 Thread Paolo Bonzini
believe that the fix for the issue under discussion will be > committed to qemu repo very soon, Did you test the patch, and did it work for you? If so, it is customary to reply with a line like "Tested by: Sair, Umair ". > so I'll like to add one more thing > which requires to be fixed along with it. In 'tcp_chr_accept' > function of qemu-char.c, the data type of saddr should be > sockaddr_in6 so that it works with both IPv6 and IPv4 on Windows > (works for linux without it because of accept4 and works with this > solution as well!). Can you send a patch for it? Thanks! Paolo

Re: [Qemu-discuss] TCP options ipv4 and ipv6 have no effect

2015-10-05 Thread Paolo Bonzini
believe that the fix for the issue under discussion will be > committed to qemu repo very soon, Did you test the patch, and did it work for you? If so, it is customary to reply with a line like "Tested by: Sair, Umair ". > so I'll like to add one more thing > which requires to be fixed along with it. In 'tcp_chr_accept' > function of qemu-char.c, the data type of saddr should be > sockaddr_in6 so that it works with both IPv6 and IPv4 on Windows > (works for linux without it because of accept4 and works with this > solution as well!). Can you send a patch for it? Thanks! Paolo

Re: [Qemu-discuss] TCP options ipv4 and ipv6 have no effect

2015-10-04 Thread Paolo Bonzini
} if (addr->has_to) { qemu_opt_set_number(opts, "to", addr->to, &error_abort); The first if handles the "default to N" case, the second handles "default to Y", the (absent) else case handles "default to PF_UNSPEC". Paolo

[Qemu-discuss] How to Use QEMU

2015-09-29 Thread Paolo G. Santiago
4.0.1.tar.bz2 but I don't know what to do with it. I can't find an .exe file to install. Sorry but I'm a total noob at this. Hope someone can give me a walkthrough on how to use it     Looking forward to your urgent reply. Paolo Santiago

Re: [Qemu-discuss] Why do additional cores reduce performance?

2014-12-16 Thread Paolo Bonzini
not support multithreading. KVM does, and you are using it. > I guess I need to try different hypervisor. 50% performance is too > high price especially when VT-x and VT-d are meant to make it 0% It is surprising to me too. Paolo

Re: [Qemu-discuss] Why do additional cores reduce performance?

2014-12-16 Thread Paolo Bonzini
HT in the host _and_ you are pinning the two threads of each guest core to the two threads of a host core. Paolo

Re: [Qemu-discuss] Hang on reboot in FreeBSD guest on Linux KVM host

2014-06-17 Thread Paolo Bonzini
Il 16/06/2014 18:47, John Nielsen ha scritto: On Jun 16, 2014, at 10:39 AM, Paolo Bonzini wrote: Il 16/06/2014 18:09, John Nielsen ha scritto: The only substantial difference on the hardware side is the CPU. The hosts where the problem occurs use "Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.

Re: [Qemu-discuss] Hang on reboot in FreeBSD guest on Linux KVM host

2014-06-16 Thread Paolo Bonzini
eon(R) CPU E5-2650 0 @ 2.00GHz". Can you do "grep . /sys/module/kvm_intel/parameters/*" on both hosts please? Paolo

Re: [Qemu-discuss] e1000 patch for osx

2013-10-30 Thread Paolo Bonzini
@@ -446,7 +456,15 @@ > if (addr < NPHYWRITEOPS && phyreg_writeops[addr]) { > phyreg_writeops[addr](s, index, data); > } > -s->phy_reg[addr] = data; > +switch (addr) { > + case PHY_CTRL: > + s->phy_reg[addr] = data & 0x7eff; Does it work if you put 0x7fff here? Paolo

Re: [Qemu-discuss] e1000 patch for osx

2013-10-30 Thread Paolo Bonzini
e second patch I posted and see if it works for you? Paolo

Re: [Qemu-discuss] [Qemu-devel] e1000 patch for osx

2013-10-30 Thread Paolo Bonzini
dr < NPHYWRITEOPS && phyreg_writeops[addr]) { phyreg_writeops[addr](s, index, data); +} else { +s->phy_reg[addr] = data; } -s->phy_reg[addr] = data; } } s->mac_reg[MDIC] = val | E1000_MDIC_READY; Paolo

Re: [Qemu-discuss] e1000 patch for osx

2013-10-30 Thread Paolo Bonzini
} else { if (addr < NPHYWRITEOPS && phyreg_writeops[addr]) { phyreg_writeops[addr](s, index, data); +} else { +s->phy_reg[addr] = data; } -s->phy_reg[addr] = data; } } s->mac_reg[MDIC] = val | E1000_MDIC_READY; Paolo

Re: [Qemu-discuss] e1000 patch for osx

2013-10-25 Thread Paolo Bonzini
ply fully as code was changed. Which patch was that? Paolo