Displaying 5 results from an estimated 5 matches for "virtdriv".
Did you mean:
virtdev
2017 Jun 03
2
Re: libvirtd not accepting connections
On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote:
>I also tried stopping libvirtd, renaming both qemu-system-i386 and
>qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq
>log messages show up.
>
>$ sudo systemctl status libvirtd.service
>● libvirtd.service - Virtualization daemon
> Loaded: loaded
2017 Jun 04
0
Re: libvirtd not accepting connections
...virStateInitialize:769 :
Running global init for QEMU state driver
2017-06-04 00:04:14.303+0000: 3379: info : virObjectNew:202 :
OBJECT_NEW: obj=0x7fa3d0122250 classname=virQEMUDriverConfig
2017-06-04 00:04:14.305+0000: 3379: debug :
virSecurityManagerNewDriver:86 : drv=0x7fa44d580f40 (selinux)
virtDriver=QEMU flags=a
2017-06-04 00:04:14.305+0000: 3379: debug :
virSecuritySELinuxInitialize:561 : SELinuxInitialize QEMU
2017-06-04 00:04:14.307+0000: 3379: debug :
virSecuritySELinuxQEMUInitialize:516 : Loaded domain context
'system_u:system_r:svirt_t:s0', alt domain context
'system_u:...
2017 Jun 04
2
Re: libvirtd not accepting connections
...69 :
>Running global init for QEMU state driver
>2017-06-04 00:04:14.303+0000: 3379: info : virObjectNew:202 :
>OBJECT_NEW: obj=0x7fa3d0122250 classname=virQEMUDriverConfig
>2017-06-04 00:04:14.305+0000: 3379: debug :
>virSecurityManagerNewDriver:86 : drv=0x7fa44d580f40 (selinux)
>virtDriver=QEMU flags=a
>2017-06-04 00:04:14.305+0000: 3379: debug :
>virSecuritySELinuxInitialize:561 : SELinuxInitialize QEMU
>2017-06-04 00:04:14.307+0000: 3379: debug :
>virSecuritySELinuxQEMUInitialize:516 : Loaded domain context
>'system_u:system_r:svirt_t:s0', alt domain contex...
2017 Jun 04
0
Re: libvirtd not accepting connections
...nit for QEMU state driver
>> 2017-06-04 00:04:14.303+0000: 3379: info : virObjectNew:202 :
>> OBJECT_NEW: obj=0x7fa3d0122250 classname=virQEMUDriverConfig
>> 2017-06-04 00:04:14.305+0000: 3379: debug :
>> virSecurityManagerNewDriver:86 : drv=0x7fa44d580f40 (selinux)
>> virtDriver=QEMU flags=a
>> 2017-06-04 00:04:14.305+0000: 3379: debug :
>> virSecuritySELinuxInitialize:561 : SELinuxInitialize QEMU
>> 2017-06-04 00:04:14.307+0000: 3379: debug :
>> virSecuritySELinuxQEMUInitialize:516 : Loaded domain context
>> 'system_u:system_r:svirt_t:s...
2011 Apr 23
4
A question about memory ballooning
Hi all,
How can I manage automatically memory ballooning under a kvm host
(C5.6 and future C6)?? For example if I define a kvm guest to boot up
with 512MB of RAM and I have configured 1GB as a maximum memory for this
guest, how can I allocate this memory when guest will need it??
And the opposite question, can memory balloon be deallocated?? And is
it possible to do this automatically or