[virt-tools-list] virt-manager: does not pick up all config changes

[Cole Robinson]

On 10/01/2009 11:06 AM, James Brackinshaw wrote:
>>> I ran:
>>>  virsh edit NAME
>>> then changed <source network="default" /> under <interface type="network">
>>>
>>
>> Ahh, okay, I misunderstood. You essentially want to hotplug a network
>> card on your VM. Libvirt does support hotplugging, but not via 'virsh
>> edit' which is essentially 'virsh define'. You want to use
>> attach/detach-device for hotplugging.
> 
> I don't think I want hotplugging. I want to change the vlan for a
> particular device. I suppose in kvm speak this would mean changing the
> host network device that a virtual network device is mapped to. All
> while the guest is running. I guess this is not possible.
> 
> (Kind of like on a real switch, I change the native vlan for a port)
> 

I see, sorry for the confusion. AFAIK, the only way to accomplish this
via libvirt is through hotplugging. If you know of some way to do this
in qemu/kvm without outright removing the nic from the guest, feel free
to file a feature request against libvirt to support it (with example
qemu monitor commands).

>>> 2. virt-manager appears unresponsive/dead if you forget you're in a
>>> vnc window somewhere. would be good to have some feedback (a beep or
>>> whatever) if that happens
>>
>> Not sure I follow? How does it appear unresponsive?
> 
> I am using Windows with Xming as my X server. If I start virt-manager
> then interact with a guest using the VNC console, I can move my mouse
> to the virt-manager window and try to do stuff. It doesn't let me do
> anything.
> 
> Perhaps this is a bug with Xming? Should my mouse pointer not be stuck
> inside the guest VNC console?

Depending on what type of grab mode the guest and vnc client negotiate,
there are two possible modes:

- The mouse is 'stuck' in the VNC window. Pressing ctrl-alt releases it.
- The mouse is not stuck, but only sends input to the guest when the
    mouse is over the VNC area. virt-manager should act normal when the
    mouse is outside the VNC area.

If one of those isn't happening, then there is a bug somewhere, likely
your X server, or the VNC client gtk-vnc.

The mode that is negotiated depends on the guest distro and what input
device (tablet vs. regular mouse) is emulated in the VM.

- Cole