search for: i440fx

On Sat, Mar 24, 2018 at 03:08:16PM +0000, Tanmoy Sinha wrote: > Even though force_tcg works, I intend not to run it on emulation. Is there > way I can run it over kvm? The other observation is, without force_tcg if I > use the machine type as *pc-i440fx-2.**1*,accel=kvm it works fine. The > default machine type for my host *pc-i440fx-2.8, *which seems to crib. I don't know, but this is basically a bug in VMware, so you need to ask them to fix their nested KVM-on-ESXi use case. Rich. -- Richard Jones, Virtualization Group, Red Hat http:/...

Thanks will write to VMWare forums. Btw, is there a way I can change the qemu default machine type? I mean when I specify *-machine pc *it picks up pc-i440fx-2.8 by default. Or is it tied to the underlying host hardware? *$> *qemu-system-x86_64* -machine help* Supported machines are: *pc* Standard PC (i440FX + PIIX, 1996) (alias of pc-i440fx-2.8) *pc-i440fx-2.8* Standard PC (i440FX + PIIX, 1996) (default) pc-i440fx-2.7...

...arget-i386/kvm.c:1805: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed." Instead when I use a wrapper script and hook it with the env variable LIBGUESTFS_HV=/tmp/qemu.wrapper, things work fine, as in the script I just spawn the guest with the specific machine type pc-i440fx-2.1 over KVM. exec qemu-system-x86_64 -enable-kvm -machine *pc-i440fx-2.**1*,accel =kvm,dump-guest-core=off "${args[@]}" The script is attached as well as the libguestfs-test-tool logs. Can anybody help me on this. Why is the latest machine type, i.e. pc-i440fx-2.8 on my debian 9 gu...

Hi all, What are the differences between pc and q35?? By default, virt-manager+libvirt setups kvm guest machine as a pc-i440fx-rhel7.1.0. [hicheck at ckvm015 ~]$ /usr/libexec/qemu-kvm -machine ? Supported machines are: pc RHEL 7.1.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.1.0) pc-i440fx-rhel7.1.0 RHEL 7.1.0 PC (i440FX + PIIX, 1996) (default) pc-i440fx-rhel7.0.0 RHEL 7.0.0 PC (i440FX + PIIX,...

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. Newer versions of libvirt and QEMU will probably switch over to d...

...now it is at 2.10: $ rpm -q qemu-system-x86 qemu-system-x86-2.10.2-1.fc27.x86_64 The guest is offline. Let's see (in a couple of ways) what machine type it has while it is dormant: # virsh dumpxml cirros | grep -i machine= <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> # grep machine= /etc/libvirt/qemu/cirros.xml <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> Okay, now edit the guest XML and carefully remove the "machine='pc-i440fx-2.10'" bit---to see what machine t...

On Tue, Jun 19, 2018 at 11:37:46AM +0100, Richard W.M. Jones wrote: > QEMU for x86 supports two machine types, "pc" (emulating the ancient > Intel i440FX chipset originally used by the Pentium Pro), and "q35" > (https://wiki.qemu.org/Features/Q35). > > Currently virt-v2v does not set any machine type, so libvirt or the > target hypervisor will choose some default, probably i440fx. Newer > versions of libvirt and QEMU will...

..., I can >> reproduce even by hotplugging a DIMM instead as well - that's good, so >> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >> with older machine types. >> >> Can you switch to a newer qemu machine version, especially >> pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem works for me with >> that QEMU machine just fine. > > I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? > Below I don't even see virtio_mem. I had to repair the image (filesystem fsck) because it was...

..., I can >> reproduce even by hotplugging a DIMM instead as well - that's good, so >> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >> with older machine types. >> >> Can you switch to a newer qemu machine version, especially >> pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem works for me with >> that QEMU machine just fine. > > I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? > Below I don't even see virtio_mem. I had to repair the image (filesystem fsck) because it was...

...One issue is we don't always have access to the target hypervisor. For example in the Glance case we have to write something which will be picked up by Nova much later: > > + "hw_machine_type", > > + (match guestcaps.gcaps_machine with > > + | I440FX -> "pc" > > + | Q35 -> "q35" > > + | Virt -> "virt"); I read the Nova code and it seems very ad-hoc. As far as I can tell these strings are eventually passed down to libvirt. However libvirt capabilities doesn't advertise the...

...<doi>0</doi> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-i386</emulator> <machine canonical='pc-i440fx-1.6' maxCpus='255'>pc</machine> <machine maxCpus='255'>pc-q35-1.4</machine> <machine maxCpus='255'>pc-q35-1.5</machine> <machine canonical='pc-q35-1.6' maxCpus='255'>q35</machine> <ma...

Hi, Could anybody give me some advice, how to define virtual machine type "pc-i440fx-2.1" on latest centos 7.1? I need to live migrate vms from debian based hypervisor and I get an error about unsupported machine types, because on centos there are different naming "pc-i440fx-rhel7.1.0". -- Marius Vaitiek?nas

...ugging a DIMM instead as well - that's good, so >>>> it's not related to virtio-mem, lol. Seems to be some QEMU setup issue >>>> with older machine types. >>>> >>>> Can you switch to a newer qemu machine version, especially >>>> pc-i440fx-5.0? Both, hotplugging DIMMs and virtio-mem works for me with >>>> that QEMU machine just fine. >>> >>> I still could reproduce this issue with pc-i440fx-5.0 or pc. Did I miss anything? >>> >> >> Below I don't even see virtio_mem. I had to rep...

QEMU for x86 supports two machine types, "pc" (emulating the ancient Intel i440FX chipset originally used by the Pentium Pro), and "q35" (https://wiki.qemu.org/Features/Q35). Currently virt-v2v does not set any machine type, so libvirt or the target hypervisor will choose some default, probably i440fx. The latest advice from the QEMU and libvirt communities is not to...

Hello. I'd like to determine if it's possible to change the 'machine type' attribute while a vm is running. For example, I have: <os> <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type> <boot dev='hd'/> </os> I'd like to change that to "machine='pc-i440fx-1.7'" due to an error[1] I'm seeing while migrated similar images to another host. The only way I've been able to change the machine is...

...ve access to the target hypervisor. > > For example in the Glance case we have to write something which will > be picked up by Nova much later: > > > > + "hw_machine_type", > > > + (match guestcaps.gcaps_machine with > > > + | I440FX -> "pc" > > > + | Q35 -> "q35" > > > + | Virt -> "virt"); > > I read the Nova code and it seems very ad-hoc. As far as I can tell > these strings are eventually passed down to libvirt. However libvirt > capabili...

...+rev1/hw/i386/smbios.c:825: smbios_get_tables: > Assertion `smbios_smp_sockets >= 1' failed > > Not sure if bisect will help much, but the commit which introduced > this platform works well (3458b2b0). > > arg set follows: > > /usr/bin/kvm -name vm28456 -S -machine pc-i440fx-2.1,accel=kvm,usb=off > -cpu qemu32 -m 256 -realtime mlock=off -smp > 1,sockets=1,cores=12,threads=12 -numa node,nodeid=0,cpus=0,mem=256 > -uuid 46623576-d00b-42b4-b1cc-c5c780a8b5b3 -nographic -no-user-config > -nodefaults -chardev > socket,id=charmonitor,path=/var/lib/libvirt/qemu/v...

...s is not my first install, I have configured libvirt on many machines in the past, it just worked, it has not required any manual configuration. [root at sj aadmin]# /usr/libexec/qemu-kvm -machine help Supported machines are: none empty machine pc RHEL 7.0.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.0.0) pc-i440fx-rhel7.0.0 RHEL 7.0.0 PC (i440FX + PIIX, 1996) (default) rhel6.6.0 RHEL 6.6.0 PC rhel6.5.0 RHEL 6.5.0 PC rhel6.4.0 RHEL 6.4.0 PC rhel6.3.0 RHEL 6.3.0 PC rhel6.2.0 RHEL 6.2.0 PC rhel6.1.0...

Yes it works if I use force_tcg env variable On Sat, 24 Mar 2018 at 4:37 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Mar 23, 2018 at 05:35:38PM +0000, Tanmoy Sinha wrote: > > Thanks. Reading the defect and the associated thread in > > https://bugs.launchpad.net/qemu/+bug/1661386, I enabled performance > > counters in VMWare guest settings. Now the

...emu-system-x86 > qemu-system-x86-2.10.2-1.fc27.x86_64 > > The guest is offline. Let's see (in a couple of ways) what machine type > it has while it is dormant: > > # virsh dumpxml cirros | grep -i machine= > <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> > > # grep machine= /etc/libvirt/qemu/cirros.xml > <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> > > Okay, now edit the guest XML and carefully remove the > "machine='pc-i440fx-2.10'&quo...