search for: qemu64

...cpus with NMI Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) My host kernel config is http://cdw.me.uk/tmp/host-config.txt and the guest config is http://cdw.me.uk/tmp/guest-config.txt with qemu command line: qemu-system-x86 -enable-kvm -cpu qemu64 -machine q35 -m 2048 -name $1 \ -smp sockets=1,cores=4 -pidfile /run/$1.pid -runas nobody \ -serial stdio -vga none -vnc none -kernel /boot/vmlinuz-guest \ -append "console=ttyS0 root=/dev/vda" \ -drive file=/dev/guest/$1,cache=none,format=raw,if=virtio \ -device virti...

...cpus with NMI Kernel Offset: 0x0 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) My host kernel config is http://cdw.me.uk/tmp/host-config.txt and the guest config is http://cdw.me.uk/tmp/guest-config.txt with qemu command line: qemu-system-x86 -enable-kvm -cpu qemu64 -machine q35 -m 2048 -name $1 \ -smp sockets=1,cores=4 -pidfile /run/$1.pid -runas nobody \ -serial stdio -vga none -vnc none -kernel /boot/vmlinuz-guest \ -append "console=ttyS0 root=/dev/vda" \ -drive file=/dev/guest/$1,cache=none,format=raw,if=virtio \ -device virti...

Version 1 was here: https://listman.redhat.com/archives/libguestfs/2023-February/thread.html#30694 I made a few changes in v2 but overall decided to keep the now unused gcaps_arch_min_version capability. This doesn't preclude removing it in future if we think it's never going to be useful. I changed patch 1 so that to remove the long comment about how the field is used, anticipating the

...t; --- a/lib/types.mli > +++ b/lib/types.mli > @@ -268,7 +268,11 @@ type guestcaps = { > minimum version. Notably RHEL >= 9 requires at least x86_64-v2. > > If the guest is capable of running on QEMU's default VCPU model > - for the architecture ([-cpu qemu64]) then this is set to [0]. *) > + for the architecture ([-cpu qemu64]) then this is set to [0]. > + > + Note this capability is not actually used by any current output > + mode. It is retained in case we might use it in future, but we > + might remove it if it is...

...dpe1gb lm rep_good nopl > extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave > avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse > 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 > > whereas in a (working) -cpu qemu64 guest, they look like this: > > fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx > fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm > cmp_legacy svm abm sse4a I thought I'd try to bisect on processor flags to see which wa...

...dpe1gb lm rep_good nopl > extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave > avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse > 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 > > whereas in a (working) -cpu qemu64 guest, they look like this: > > fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx > fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm > cmp_legacy svm abm sse4a I thought I'd try to bisect on processor flags to see which wa...

...ug vcpus, but when i want to unplug them i get the following: virsh # setvcpus pathway 3 --live virsh # setvcpus pathway 4 --live virsh # setvcpus pathway 2 --live error: internal error: unable to execute QEMU command 'device_del': acpi: device unplug request for not supported device type: qemu64-x86_64-cpu Does anyone know why it can't be unplugged ? Thanks. Brtnf -- Bernd Lentes Systemadministration Institute for Metabolism and Cell Death (MCD) Building 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lentes@helmholtz-muenchen.de phone: +49 89 3187 1241 phone: +49 89 3187...

...confused by the behaviour of the CPU description in my VM. I have a host with an AMD CPU with SVM feature and I want to try nested virtualization on a Fedora22 guest. The host is Fedora22 as well. libvirtd (libvirt) 1.2.13.1 kernel 4.1.6-200.fc22.x86_64 1. I tried 'custom' mode with model qemu64 with required feature 'SVM' but '/proc/cpuinfo' in the guest doesn't show SVM. 2. However, if I forbid the SVM feature, the guest can't be created and libvirt complains that the host CPU has SVM. 3. The only way to have SVM reported in '/proc/cpuinfo' inside the gu...

...d_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave >>> avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse >>> 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 >>> >>> whereas in a (working) -cpu qemu64 guest, they look like this: >>> >>> fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx >>> fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm >>> cmp_legacy svm abm sse4a >> >> I thought I'...

...d_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave >>> avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse >>> 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 >>> >>> whereas in a (working) -cpu qemu64 guest, they look like this: >>> >>> fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx >>> fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm >>> cmp_legacy svm abm sse4a >> >> I thought I'...

...sed the virsh capabilites command to detect how is detected my CPU host which is an Intel Xeon E5410 and my problem is that this CPU is detected only with the cpumodel "pentium3". But if use the kvm -cpu ? command, it returns me the following capabilities : $ kvm -cpu ? x86 qemu64 x86 phenom x86 core2duo x86 kvm64 x86 qemu32 x86 coreduo x86 486 x86 pentium x86 pentium2 x86 pentium3 x86 athlon x86 n270 Moreover, if i decide to use the pentium3 cpumodel for my KVM VM, t...

...eryone's email on this but I tried something new and found a different problem. I uninstalled all the debian package (libvirt, kvm, qemu, virt-manager, etc.) and then remade all the packages and installed them. Haswell again shows up in virt-manager, but now any CPU I choose including kvm64 and qemu64 give the same error: root@mal:~# virsh create /etc/libvirt/qemu/debian7-nonsmp.xml 2013-06-19 03:09:42.836+0000: 24248: info : libvirt version: 1.0.6 2013-06-19 03:09:42.836+0000: 24248: warning : virLogParseDefaultPriority:1581 : Ignoring invalid log level setting error: Failed to create domain f...

...to unplug them i get the following: > > virsh # setvcpus pathway 3 --live > virsh # setvcpus pathway 4 --live > virsh # setvcpus pathway 2 --live > error: internal error: unable to execute QEMU command 'device_del': acpi: device unplug request for not supported device type: qemu64-x86_64-cpu > > Does anyone know why it can't be unplugged ? Sounds like qemu doesn't support unplug of vcpus. Which version of qemu do you use?

...nopl >> extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave >> avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse >> 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 >> >> whereas in a (working) -cpu qemu64 guest, they look like this: >> >> fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx >> fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm >> cmp_legacy svm abm sse4a > > I thought I'd try to bisect on process...

...were 1) The ability to specify cpu type and even exact capabilities 2) The ability to set the topology. It's good because before this ability appears WinXP guests won't use more than two cores. I got problem with both of these features. First, I can't manually specify cpu type 'qemu64' - virtmanager says my physical CPU doesn't have some abilities. But if no CPU is specified, it is reported as 64bit Second, a killer app on one of WinXP servers stopped working since upgrade. It's a russian proprietary accounting app named 1C ver. 8.1 (1cv8.exe). It would just han...

...6 kvm64 Common KVM processor x86 n270 Intel(R) Atom(TM) CPU N270 @ 1.60GHz x86 pentium x86 pentium2 x86 pentium3 x86 phenom AMD Phenom(tm) 9550 Quad-Core Processor x86 qemu32 QEMU Virtual CPU version 2.5+ x86 qemu64 QEMU Virtual CPU version 2.5+ x86 host KVM processor with all supported host features (only available in KVM mode) Recognized CPUID flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 pn clflush ds acpi mmx fxsr sse sse2 ss ht tm ia64 pbe pni pclmul...

On 06/17/2013 05:41 PM, Michael Giardino wrote: > Kashyap: I have not tried integrating your guest xml but I will look > over it today when I get a chance. Thank you. > > Martin: Below is the output from /proc/cpuinfo. Let me know if there is > anything else that would be helpful in debugging this. Thank you, > Unfotunately, my guess was wrong. If you could run 'cpuid

...='amd-ssbd'/> > >> > <feature policy='require' name='skip-l1dfl-vmentry'/> > >> > </mode> > >> > <mode name='custom' supported='yes'> > >> > <model usable='yes'>qemu64</model> > >> > <model usable='yes'>qemu32</model> > >> > <model usable='no'>phenom</model> > >> > <model usable='yes'>pentium3</model> > >> > <model usable='y...

Hi all, this is the long awaited patch series to add xen device model support in qemu; the main author is Anthony Perard. Developing this series we tried to come up with the cleanest possible solution from the qemu point of view, limiting the amount of changes to common code as much as possible. The end result still requires a couple of hooks in piix_pci but overall the impact should be very