[libvirt-users] All VMs permanently 'paused'
by Mark Coolen
I set up Alpine Linux as a libvirt-based KVM hypervisor last week.
Everything was working beautifully on Friday. I left two Windows VMs up and
running and two 'Saved' on Friday afternoon. When I go in this morning the
two running ones were 'Paused' and I can't unpause them with virt-manager
or with virsh. The other two saved ones I can start, but they are
immediately paused too. When I click to unpause in virt- manager nothing
happens. When I 'resume' in virsh I get 'Domain ... resumed' but it's
immediately paused again. I looked in /var/log/libvirt/libvirtd.log and
qemu/<DOMAIN>.log and there doesn't seem to be anything happening. No
errors or anything.
As I say. Everything was working fine on Friday afternoon.
Does anyone know what I should try next? I'll attach my logs and the XML of
one of my machines.
_ _ _ ___ _
)\/,) ___ __ )L, )) __ __ )) __ _ _
((`(( ((_( (| ((\ ((__((_)((_)(( (('((\(
6 years, 6 months
[libvirt-users] virsh and bash scripts
by Hetz Ben Hamo
Hi,
I'm looking for a way to use virsh to connect to vCenter/VCSA and do some
simple management of the VM's in case of power loss (I'm planning to run
the script upon UPS/apcd event of power failure).
Looking through the virsh documentation, I didn't find 2 things:
1. Login through a script (I don't see any user/password, specially since
VCSA for example requires to use username(a)vsphere.local [or your AD domain
insteadd of vsphere.local if you connected it to your AD domain])
2. Get all the VMs running on the vCenter, not just specific hosts.
Any suggestion?
Thanks
6 years, 6 months
[libvirt-users] Libvirt not terminating SSH processes
by Priyanka Gupta
Hi LibVirt team,
I am facing an issue with libvert. I am closing a "qemu+ssh" connection but
the initiated ssh process are going into sleep mode and not getting killed
upon closing the connection. Can you please help me figure out the issue ?
--
With Kind Regards
Priyanka Gupta
6 years, 6 months
[libvirt-users] Cannot Write xvga=yes in xml file
by Rogue S.T
Hello,my system info:
virsh verison
Compiled against library: libvirt 3.9.0
Using library: libvirt 3.9.0
Using API: QEMU 3.9.0
Running hypervisor: QEMU 2.10.90
And i want to pass through my gpu to my window 7 guest with <hostdev>, next line is comand i use:
<hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
<rom bar='on' file='/root/gpu.dump'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</hostdev>
But i get this error:
XML document failed to validate against schema: Unable to validate doc against /ocl/share/libvirt/schemas/domain.rng
Extra element devices in interleave
Element domain failed to validate content
If i delete xvga='yes',it's ok, but i get a other question, my display is not light.
6 years, 6 months
[libvirt-users] libvirt net xml format
by Bhasker C V
Hi all,
I went through the docs but could not find a way to pass the
-h OR --no-hosts
option to dnsmasq via libvirt xml
Is there a way to do this via xml ? please can someone help.
Thanks
6 years, 6 months
[libvirt-users] Using Intel Quick-Sync with GPU capable Intel CPUs
by Benjammin2068
Rogue S.T asked about checking out graphics cards which brought the question to me...
Is it possible to make Intel on-CPU GPU resources to Windows 10?
(the box I'm working with has Xeon E5-2640v4 CPUs which should be QuickSync capable)
What else do I have to do to take advantage of this?
Just load the drivers?
Thanks,
-Ben
6 years, 6 months
[libvirt-users] questions about disk auth element for Backing Chain
by Meina Li
Hi,
I am a libvirt qe, I am testing the function about the new location of disk
auth element (as sub-element of the source element) in Backing Chain
Management. And I have a questions:
When all the backing chain are iscsi network disk type(no matter if the
authentication is exist), start the guest , it will only has the top
level disk in xml and there are no other backingStore in it. The test step
is below.
So can this function support all backing chain with network disk type
actually, or only use network authentication as the base image for backing
chain of file disk type?
Can you help reviewing it? Thanks very much in advance!
Test step:
1. iSCSI server:
o- iscsi
............................................................................................................
[Targets: 2]
| o- iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6
....................................................... [TPGs: 1]
| | o- tpg1
.....................................................................................
[gen-acls, tpg-auth, 1-way auth]
| | o- acls
..........................................................................................................
[ACLs: 0]
| | o- luns
..........................................................................................................
[LUNs: 4]
| | | o- lun0
................................................................
[fileio/file1 (/tmp/lun1.img) (default_tg_pt_gp)]
| | o- portals
....................................................................................................
[Portals: 1]
| | o- 0.0.0.0:3260
.....................................................................................................
[OK]
| o- iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece
....................................................... [TPGs: 1]
| o- tpg1
..................................................................................................
[gen-acls, no-auth]
| o- acls
..........................................................................................................
[ACLs: 0]
| o- luns
..........................................................................................................
[LUNs: 3]
| | o- lun0
................................................................
[fileio/file3 (/tmp/lun3.img) (default_tg_pt_gp)]
| o- portals
....................................................................................................
[Portals: 1]
| o- 0.0.0.0:3260
.....................................................................................................
[OK]
2. Set iscsi secret.
# cat iscsi-secret.xml
<secret ephemeral='no' private='yes'>
<description>iSCSI secret</description>
<usage type='iscsi'>
<target>libvirtiscsi</target>
</usage>
</secret>
# virsh secret-define iscsi-secret.xml
Secret 47bd2f3e-023f-44ba-85a3-e8fa7f16ff23 created
# MYSECRET=`printf %s "redhat" | base64`
# virsh secret-set-value 47bd2f3e-023f-44ba-85a3-e8fa7f16ff23 $MYSECRET
Secret value set
3. Create backing chain.
# qemu-img create -f qcow2 -b iscsi://
redhat:redhat@10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6/0
iscsi://
10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0
-o backing_fmt=qcow2
4. Start guest.
# qemu-img info iscsi://
10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0
--backing-chainimage: json:{"driver": "qcow2", "file": {"lun": "0",
"portal": "10.66.7.27:3260", "driver": "iscsi", "transport": "tcp",
"target": "iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece"}}
file format: qcow2
virtual size: 5.0G (5368709120 bytes)
disk size: unavailable
cluster_size: 65536
backing file: iscsi://
redhat:redhat@10.66.7.27:3260/iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6/0
backing file format: qcow2
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
image: json:{"driver": "qcow2", "file": {"lun": "0", "portal": "
10.66.7.27:3260", "driver": "iscsi", "transport": "tcp", "user": "redhat",
"password": "redhat", "target":
"iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.9cba196611e6"}}
file format: qcow2
virtual size: 5.0G (5368709120 bytes)
disk size: unavailable
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: false
refcount bits: 16
corrupt: false
# virsh dumpxml rhel7 | grep disk -A 9
...
<disk type='network' device='disk'>
<driver name='qemu' type='qcow2'/>
<source protocol='iscsi'
name='iqn.2003-01.org.linux-iscsi.localhost.x8664:sn.a8d92ebb4ece/0'>
<host name='10.66.7.27' port='3260'/>
</source>
<target dev='vdb' bus='virtio'/>
<alias name='virtio-disk1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x09'
function='0x0'/>
</disk>
...
Best Regards
Meina Li
6 years, 6 months
