search for: hotpluggable

Hi, i'm playing a bit around with vcpus. My guest is Windows 10 1903. This is the excerpt from the config: ... <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2' enabled='no' hotpluggable='yes'/> <vcpu id='3' enabled='no' hotpluggable='yes'/> </vcpus> ... I'm able t...

...otlb DMA bounce buffers to >> map such PFNs (total 0 (slots), used 0 (slots)). >> >> Can you try with "swiotlb=force" on the kernel cmdline? > Alternative, looks like you can specify "-m 2G,maxmem=16G,slots=1", to > create proper ACPI tables that indicate hotpluggable memory. (I'll have > to look into QEMU to figure out to always indicate hotpluggable memory > that way). > That works too. Yes, better resolved in qemu, maybe. :) Thanks!

...otlb DMA bounce buffers to >> map such PFNs (total 0 (slots), used 0 (slots)). >> >> Can you try with "swiotlb=force" on the kernel cmdline? > Alternative, looks like you can specify "-m 2G,maxmem=16G,slots=1", to > create proper ACPI tables that indicate hotpluggable memory. (I'll have > to look into QEMU to figure out to always indicate hotpluggable memory > that way). > That works too. Yes, better resolved in qemu, maybe. :) Thanks!

...t;currentMemory unit='KiB'>4147456</currentMemory> <!-- maxMemory unit='KiB' slots='8'>16146944</maxMemory --> <vcpu placement='static' current='2'>4</vcpu> <vcpus> <vcpu id='0' enabled='yes' hotpluggable='no'/> <vcpu id='1' enabled='yes' hotpluggable='yes'/> <vcpu id='2' enabled='no' hotpluggable='yes'/> <vcpu id='3' enabled='no' hotpluggable='yes'/> </vcpus> <os> &lt...

...; Hi, > > i'm playing a bit around with vcpus. > My guest is Windows 10 1903. > This is the excerpt from the config: > ... > <vcpu placement='static' current='2'>4</vcpu> > <vcpus> > <vcpu id='0' enabled='yes' hotpluggable='no'/> > <vcpu id='1' enabled='yes' hotpluggable='yes'/> > <vcpu id='2' enabled='no' hotpluggable='yes'/> > <vcpu id='3' enabled='no' hotpluggable='yes'/> > </vcpus>...

On 05.06.20 11:08, David Hildenbrand wrote: > On 05.06.20 10:55, Alex Shi wrote: >> >> >> ? 2020/1/9 ??9:48, David Hildenbrand ??: >>> Ping, >>> >>> I'd love to get some feedback on >>> >>> a) The remaining MM bits from MM folks (especially, patch #6 and #8). >>> b) The general virtio infrastructure (esp. uapi in patch

On 05.06.20 11:08, David Hildenbrand wrote: > On 05.06.20 10:55, Alex Shi wrote: >> >> >> ? 2020/1/9 ??9:48, David Hildenbrand ??: >>> Ping, >>> >>> I'd love to get some feedback on >>> >>> a) The remaining MM bits from MM folks (especially, patch #6 and #8). >>> b) The general virtio infrastructure (esp. uapi in patch

...hot unplugs of various devices, I've found out that hot unplugging <lease> device doesn't generate VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an alias, so it wouldn't be identifiable in the corresponding callback. Is this difference from other hotpluggable devices intentional? If yes, is there any better way of checking that <lease> removal is completed than querying and examining the domain XML? From user's point of view, it would be best if I could simply handle the device removal event the same way as with other devices. Thanks, Milan

...nd out that >> hot unplugging <lease> device doesn't generate >> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an >> alias, so it wouldn't be identifiable in the corresponding callback. >> >> Is this difference from other hotpluggable devices intentional? If yes, > > Well a "lease" is not a device per-se. It's just libvirt putting it with > devices. Currently the "lease" is always successfully removed/unplugged > if the API returns success as there is no cooperation with qemu > necessary s...

...n't have any swiotlb DMA bounce buffers to > map such PFNs (total 0 (slots), used 0 (slots)). > > Can you try with "swiotlb=force" on the kernel cmdline? Alternative, looks like you can specify "-m 2G,maxmem=16G,slots=1", to create proper ACPI tables that indicate hotpluggable memory. (I'll have to look into QEMU to figure out to always indicate hotpluggable memory that way). -- Thanks, David / dhildenb

...ers to >>> map such PFNs (total 0 (slots), used 0 (slots)). >>> >>> Can you try with "swiotlb=force" on the kernel cmdline? >> Alternative, looks like you can specify "-m 2G,maxmem=16G,slots=1", to >> create proper ACPI tables that indicate hotpluggable memory. (I'll have >> to look into QEMU to figure out to always indicate hotpluggable memory >> that way). >> > > > That works too. Yes, better resolved in qemu, maybe. :) > You can checkout git at github.com:davidhildenbrand/qemu.git virtio-mem-v4 (prone to...

...however is the same, whichever I use Now, the command above produces this error. I find no google results with this error text. Can someone tell, what causes the error? > > error: Failed to attach disk error: operation failed: adding scsi > > disk controller failed: type scsi not a hotpluggable PCI device. > > failed to add if=scsi I found a post (2009, on fedora-virt list), which is relevant: http://www.redhat.com/archives/fedora-virt/2009-December/msg00032.html Otherwise, I have found almost nothing! BTW, I can attach a disk to the KVM guest, using a virtio driver: > &gt...

...turn to ONLINE after it''s replugged. This goal may be hard to achieve because it''s a tough decision as to whether or not to panic when the storage failed. And seems there''s no mechanism for zfs to tell if it''s a usb harddisk or a fixed disk. Anyway, because the hotpluggable nature of usb harddisk, unplug it unintentionally should not panic. my 1c Thank you

...o access) outw 1737 (memory access) movw 4341 for comparison: (hypercall access): vmcall 1566 (pv memory access) movw_fast 1817 (*explanation what this is below) This creates a problem if we want to make virtio devices proper PCI express devices with native hotplug support. This is because each hotpluggable PCI express device always has a PCI express port (port per device), where each port is represented by a PCI to PCI bridge. In turn, a PCI to PCI bridge claims a 4Kbyte aligned range of IO addresses. This means that we can have at most 15 such devices, this is a nasty limitation. Another problem wi...

...o access) outw 1737 (memory access) movw 4341 for comparison: (hypercall access): vmcall 1566 (pv memory access) movw_fast 1817 (*explanation what this is below) This creates a problem if we want to make virtio devices proper PCI express devices with native hotplug support. This is because each hotpluggable PCI express device always has a PCI express port (port per device), where each port is represented by a PCI to PCI bridge. In turn, a PCI to PCI bridge claims a 4Kbyte aligned range of IO addresses. This means that we can have at most 15 such devices, this is a nasty limitation. Another problem wi...

On 04/27/2017 04:31 PM, Stefano Ricci wrote: > Here is the backtrace of the libvirt process just started [Just a side note, you shouldn't top post on technical lists. Gmail sucks at this.] > > https://pastebin.com/R66myzFp Looks like libvirtd is trying to spawn /usr/bin/qemu-system-x86_64 but it takes ages to init. In the debug logs you might see the actual command line that

...-mice"}, {"name": > "query-memory-devices"}, {"name": "query-memdev"}, {"name": > "query-machines"}, {"name": "query-kvm"}, {"name": "query-iothreads"}, > {"name": "query-hotpluggable-cpus"}, {"name": "query-fdsets"}, > {"name": "query-events"}, {"name": > "query-dump-guest-memory-capability"}, {"name": "query-dump"}, > {"name": "query-cpus"}, {"name": &quo...

...evices, I've found out that > hot unplugging <lease> device doesn't generate > VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an > alias, so it wouldn't be identifiable in the corresponding callback. > > Is this difference from other hotpluggable devices intentional? If yes, Well a "lease" is not a device per-se. It's just libvirt putting it with devices. Currently the "lease" is always successfully removed/unplugged if the API returns success as there is no cooperation with qemu necessary so the semantics of askin...

...hot unplugging <lease> device doesn't generate > >> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. <lease> also doesn't have an > >> alias, so it wouldn't be identifiable in the corresponding callback. > >> > >> Is this difference from other hotpluggable devices intentional? If yes, > > > > Well a "lease" is not a device per-se. It's just libvirt putting it with > > devices. Currently the "lease" is always successfully removed/unplugged > > if the API returns success as there is no cooperation with q...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to get add a new Wiki entry regarding Automounting with HAL for CentOS 5, since the behaviour is very different than CentOS 4. Main points: - - Making automounting hotpluggable devices work with other WMs - - Overriding the default mount point - - Overriding the default mount options (noexec etc) Small nightmare here to find out how to do those things, for a simple fact: NONE of the documentation I've found work. The reason ? HAL adding "user" do the line...