Ok, I've added and got rid of the pc-1.1
rubbish, now the qemu looks like:
qemu-system-x86_64 -enable-kvm -name cedric.CalvaEDI.COM -S -machine
pc-i440fx-2.1,accel=kvm,usb=off -m 8192 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid 99cfca83-cf28-ce9b-86a4-947debc202b5
-nographi
On 19/12/14 15:53, Michael Tokarev wrote:
acpi is not the only possible way. More recent qemu (not pc-1.1 which
you used) also has pcie bus, which does support hotplugging without acpi.
But you used both pc-1.1 (old non-pcie machine) and no-acpi.
Ok, thanks. Still waiting for people to stop
On 19/12/14 15:10, Michael Tokarev wrote:
Also, libvirt isn't right (IMHO) to stick with particular
machine version (in your case, -M pc-1.1). It is needed
for certain guest OS types, for example windows, to keep
its activation changes (so that hw should not change).
Linux is much more tolerant
19.12.2014 17:42, John Hughes wrote:
[]
> If it works then I contend the bug is the error message -- it would be really
> helpful if it said "You can't hotplug because you haven't got ACPI".
acpi is not the only possible way. More recent qemu (not pc-1.1 which
you used) also has pcie bus, which
On 19/12/14 14:59, Michael Tokarev wrote:
19.12.2014 16:50, John Hughes wrote:
Note:
... -no-acpi ...
No ACPI, no hotplug?
The linux guest-side module to handle hotplug is acpiphp.
I think the name speaks for itself.
When I can get my users to stop doing real work to let me play with my
toy
19.12.2014 16:59, Michael Tokarev wrote:
> 19.12.2014 16:50, John Hughes wrote:
>
>> Note:
>>
>> ... -no-acpi ...
>>
>> No ACPI, no hotplug?
>
> The linux guest-side module to handle hotplug is acpiphp.
> I think the name speaks for itself.
Also, libvirt isn't right (IMHO) to stick with particul
19.12.2014 16:50, John Hughes wrote:
> Note:
>
> ... -no-acpi ...
>
> No ACPI, no hotplug?
The linux guest-side module to handle hotplug is acpiphp.
I think the name speaks for itself.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "uns
Well, I've upgraded to:
# dpkg -l libvirt* qemu* | grep '^ii'
ii libvirt-bin 1.2.9-6~bpo70+1amd64
programs for the libvirt library
ii libvirt-clients 1.2.9-6~bpo70+1amd64
programs for the libvirt library
ii libvirt-daemon 1.2.9-6~
Hello John.
It looks like you're making too much conspiracy theories
out of this simple problem.
I don't remember how this worked in 1.1 times of qemu.
Apparently libvirt chooses -nodefaults and the result
is that the pci bus created does not support hotplug,
since libvirt didn't specify if qemu
I've restarted my VM and tried again.
This is what I see:
adriatic:~# lsof /dev/md124
adriatic:~# virsh attach-device cedric.CalvaEDI.COM zz.xml
error: Failed to attach device from zz.xml
error: internal error unable to execute QEMU command 'device_add': Bus
'pci.0' does not support hotplugging
Well, it looks like the command has half worked -- lsof shows me that
kvm has opened the block device I tried to add.
Now how to make it give it up?
# lsof /dev/md/cedric\:new
COMMAND PID USER FD TYPE DEVICE SIZE/OFFNODE NAME
kvm 28159 libvirt-qemu 28u BLK 9,124
Package: qemu-kvm
Version: 1.1.2+dfsg-6+deb7u6
Severity: normal
Dear Maintainer,
* What led up to the situation?
Tried to add a new disk to a running kvm guest
* What exactly did you do (or not do) that was effective (or
ineffective)?
Using the virsh attach-device command I tried to
12 matches
Mail list logo
