[libvirt-users] virt-manager wont connect to remote libvirt instance
by bherman
I am using virt-manager on debian 8 and I am remotely connecting to a
libvirt instance on a server.
It was all working fine until today when I discovered that I cannot
remotely connect to the libvirt server anymore.
● libvirtd.service - Virtualization daemon
Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Tue 2016-11-22 10:27:09 CST; 46min ago
Docs: man:libvirtd(8)
http://libvirt.org
Process: 27630 ExecReload=/bin/kill -HUP $MAINPID (code=exited,
status=0/SUCCESS)
Main PID: 27823 (libvirtd)
CGroup: /system.slice/libvirtd.service
├─ 4787 /usr/sbin/libvirtd
├─ 8187 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf
--dhcp-script=/usr/lib/libvi...
├─ 8188 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf
--dhcp-script=/usr/lib/libvi...
└─27823 /usr/sbin/libvirtd
It says it is running however I cant connect to it either remotely or on
the server using virt-manager.
When I do a virsh --list It just hangs and doesn't output anything.
Any ideas?
--
Thanks,
Brian Herman
IT
O: (773)299-7557
F: (773)299-7505
7 years, 8 months
[libvirt-users] Routed mode problem with SSH
by Marcelo Palma
Hi guys, I describe the context of the problem below:
I installed a Tor relay on a virtual machine on my server with IP
9.1.1.101. This
virtual machine needs to use a static IP (9.1.1.102) to work as a Tor
relay. After
that I create a virtual network in *Routed mode* to connect to the physical
network (used as a bridge between the virtual machine and the external
network (Internet)).
Since I change the NAT to Routed mode, I can't access my server via ssh
user(a)9.1.1.101.
Will it be a Routed mode problem?
How can I solve this problem?
Thank you
Marcelo
7 years, 8 months
[libvirt-users] blockcommit and gluster network disk path
by Sahina Bose
Hi,
I'm running into problems with blockcommit and gluster network disks -
wanted to check how to pass path for network disks. How's the protocol and
host parameters specified?
For a backing volume chain as below, executing
virsh blockcommit fioo5
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c
--base
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a
--top
vmstore/912d9062-3881-479b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c
--verbose --wait
gives "error: invalid argument: No device found for specified path".
<disk type='network' device='disk' snapshot='no'>
<driver name='qemu' type='qcow2' cache='none' error_policy='stop'
io='threads'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/027a3b37-77d4-4fa9-8173-b1fedba1176c'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore type='network' index='1'>
<format type='qcow2'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/d4c23ec6-20ce-4a2f-9b32-ca91e65a114a'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore type='network' index='2'>
<format type='raw'/>
<source protocol='gluster' name='vmstore/912d9062-3881-47
9b-a6e5-7b074a252cb6/images/27b0cbcb-4dfd-4eeb-8ab0-8fda54a6
d8a4/f5098809-e719-404b-8d80-3f824f4333a2'>
<host name='10.70.37.28' port='0'/>
</source>
<backingStore/>
</backingStore>
</backingStore>
<target dev='vda' bus='virtio'/>
<serial>27b0cbcb-4dfd-4eeb-8ab0-8fda54a6d8a4</serial>
<boot order='2'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
thanks
sahina
7 years, 8 months
[libvirt-users] Attach libvirt guest to an existing openvswitch port
by Ivan Borodin
Good day gentlemen.
I am building a study project and trying to configure openvswitch vlans
outside libvirt by means of openvswitch itself.
Somehow with interface types 'bridge' and 'network', libvirt does attach
domain to the existing port specified in <target dev=''/>, wiping the
exixting settings and always deletes this port upon domain shutdown,
thus making me loose ovs configuration.
Could you, please, tell me how should I configure an interface or
libvirt itself to avoid this libvirt's greedines.
libvirt 2.4.0
Thak you.
Ivan.
7 years, 8 months
[libvirt-users] export a cert
by lejeczek
hi everybody
I'm browsing around but probably missing that obvious little
thing - exporting certs to pem format with ipa command
toolkit - that must be there somewhere, right?
thanks,
L.
7 years, 8 months
[libvirt-users] ergodox keyboard not working on USB hostdev passthrough
by Paul Handy
I'm using a bit of a different keyboard, the infinity ergodox [
https://input.club/devices/infinity-ergodox/]. It functions just fine as a
keyboard on my host computer, but when I try to bind it to the guest,
nothing seems to happen.
lsusb gives its ID:
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
*Bus 005 Device 003: ID 1c11:b04d*
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 258a:0001
Bus 001 Device 002: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So, I made a file, hostdev-1c11:b04d.xml, which contains the following:
<hostdev mode='subsystem' type='usb' >
<source>
<vendor id='0x1c11'/>
<product id='0xb04d'/>
</source>
</hostdev>
Note, I have had this same xml inside the domain's xml, but have pulled it
out separately so that I could run:
virsh attach-device linux-x86_64 hostdev-1c11:b04d.xml
It appears to attach the device, as it becomes visible in the domain's
lsusb:
Bus 001 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0001
*Bus 003 Device 003: ID 1c11:b04d *
Bus 003 Device 001: ID 1d6b:0001
Bus 002 Device 003: ID 093a:2521
Bus 002 Device 002: ID 258a:0001
Bus 002 Device 001: ID 1d6b:0001
The mouse works just fine. I bought a cheap keyboard to test out, and it
works just fine. My pet keyboard, however, doesn't work on the guest.
Nothing seems to register. Any ideas here what I could do? Drivers? ROM's?
I've tried both SeaBIOS and OVMF with no difference in outcome, and while
this appears to be a hardware problem, I don't know where to begin.
Thanks,
Paul
7 years, 8 months
[libvirt-users] BroadCom NIC not adding as PassThrough device
by Tahir Masood
Hi Guys,
I am trying to add a Broadcom Physical NIC to a virtual Machine as
Passthrough device. However I am getting following error.
Error starting domain: unsupported configuration: host doesn't support
passthrough of host PCI devices
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 88, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 124, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 83, in
newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1404, in
startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: unsupported configuration: host doesn't support passthrough of
host PCI devices
libvirt allows to appply the changes to the VM xml configurations, but gives
error the moment I try to start the VM.
I have tried following approaches.
1- Open Virt-Manager, Shutdown VM, edit VM , add PCI hardware device ,
locate BroadCom NIC, apply changes. Then I restart the VM.
2- Also tried to add following XML tags one by one using 'virsh edit', but
got same error.
Tag -1
<hostdev mode='subsystem' type='pci' managed='yes'>
<source>
<address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/>
</source>
</hostdev>
Tag -2
<interface type='hostdev' managed='yes'>
<source>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00'
function='0x1'/>
</source>
</interface>
The detail of the BroadCOm NIC are as follows.
02:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM5709 Gigabit
Ethernet (rev 20)
What would it take to add this NIC to VM as Passthrough Device?
Regards,
Tahir Masood
Senior Engineer,
xFlow Research Inc.
+92-300-9779473
<mailto:tahir.masood@xflowresearch.com> tahir.masood(a)xflowresearch.com
<http://www.xflowresearch.com/> www.xflowresearch.com
7 years, 8 months
[libvirt-users] how to use command 'guest-file-open' for Windows server 2012R2 vm
by 刘梦可
hello,
I am using libvirt 1.2.17 on CentOS 7.2 - kernel
3.10.0-327.13.1.el7.x86_64. The command guest-file-open failed to open
with error "this feature or command is not currently supported", the
detail is as below:
virsh qemu-agent-command instance-00000015
"{\"execute\":\"guest-file-open\",
\"arguments\":{\"path\":\"\tmp.txt\",\"mode\":\"r\"}}"
error: internal error: unable to execute QEMU agent command
'guest-file-open': this feature or command is not currently supported.
The guest instance-00000015 is a Windows server 2012R2, and I
installed the qemu-guest-agent by the file qemu-ga-x64.msi from
virtio-win-0.1.126. It can be running in guest.
Doesn't the qemu-guest-agent in Windows VM support guest-file-*
commands? How or when can I use the command guest-file-* command?
Thanks very much!!
-mkliu28
7 years, 8 months
[libvirt-users] Guest startup process blocks if a hook's child process is still running (i.e : after forking)
by Nicolas Roy-Renaud
I've been having issues with KVM lately where I sometimes put my host
into sleep while a guest is still running, which prevents it from waking
up properly. This is somewhat expected due to my setup, but I have
mistakenly done this more than once and could use a workaround to stop
this from happening.
So I've been trying to setup a libvirt hook to fork an instance of
systemd-inhibit when the start hook is called and keep it running until
the shutdown hook is called. This seems to work well when I run the hook
script in a normal bash shell, but running it through libvirt simply
blocks the starting process until systemd-inhibit quits.
Here's the script :
LOCK_FILE="/tmp/vfio-lock-$OBJECT"
if [ "$OPERATION" == "start" ]; then
(
touch "$LOCK_FILE";
systemd-inhibit --what="sleep" \
--who="libvirt" \
--mode="block" \
inotifywait -qq -e delete "$LOCK_FILE"
) & disown $!
exit
fi
if [ "$OPERATION" == "shutdown" ]; then
rm "$LOCK_FILE"
fi
Is there some way to make it so libvirt sees the hook script exiting and
carries on with the rest of its guest startup process even after a
process fork or would that require changes in the internal hook handling
functions?
- Nicolas
7 years, 8 months
