- 15 8月, 2014 32 次提交
-
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
-
由 Taowei 提交于
All vbox objects are child objects from the nsISupports in vbox's C++ API version. Since the CAPI is generated from the C++ API, I kept their relationship here, by the definitations below: typedef struct nsISupports nsISupports; typedef nsISupports IVirtualBox; typedef nsISupports ISession; and so on... So, when calling the API from nsISupports, we don't need to do typecasting, and things work still work well.
-
由 Taowei 提交于
-
由 Taowei 提交于
Introduce vbox_uniformed_api to deal with version conflicts. Use vbox_install_api to register the currect vboxUniformedAPI with vbox version. vboxConnectOpen has been rewritten.
-
由 Laine Stump 提交于
Martin Kletzander pointed out in email that my commit 2a193f64 introduced a crash in networkCreateInterfacePool() during startup of any network that doesn't have a <pf> subelement of its <forward> element. He also supplied a patch. http://www.redhat.com/archives/libvir-list/2014-August/msg00655.html I expanded on that patch by cleaning up now-extraneous checks in the callers of networkCreateInterfacePool(). Fortunately the offending patch hasn't been in any release, and hasn't been (to my knowledge) backported to any other branch.
-
由 Jim Fehlig 提交于
Handle formating of VIF config in a new function xenFormatXMVif(). Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com>
-
由 Kiarie Kahurani 提交于
introduce functions xenFormatXMSound xenFormatXMInputDevs(virConfPtr conf,....); which formats peripheral device config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMVfb(virConfPtr conf,.........); which formats Vfb config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com>
-
由 Kiarie Kahurani 提交于
introduce functions xenFormatXMEmulator(virConfPtr conf,........); xenFormatXMCDROM(virConfPtr conf, .......); xenFormatXMOS(virConfPtr conf,........); which formats OS and associated config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Kiarie Kahurani 提交于
introduce functions xenFormatXMCPUAllocation(virConfPtr conf, ......); xenFormatXMCPUFeatures(virConfPtr conf, ......); which formats CPU allocation and features config Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMDisks(virConfPtr conf,.........); which formats domain disks config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMCharDev(virConfPtr conf,........); which formats Char devices config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMEventActions(virConfPtr conf,.........); which formats event actions instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMTimeOffset(virConfPtr conf,........); which formats time config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMMem(virConfPtr conf,...........); which parses memory config instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com>
-
由 Kiarie Kahurani 提交于
introduce function xenFormatXMGeneralMeta(virConfPtr conf,......); which parses uuid and name instead Signed-off-by: NKiarie Kahurani <davidkiarie4@gmail.com> Signed-off-by: NJim Fehlig <jfehlig@suse.com>
-
由 Pavel Hrdina 提交于
Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
- 14 8月, 2014 7 次提交
-
-
由 Jianwei Hu 提交于
The correct vlanid range is 0~4095. After merging this patch, we can not validate a interface xml with vlanid >= 4096. [root@localhost ~]# cat vlan.xml <interface type='vlan' name='eno1.4096'> <start mode='onboot'/> <protocol family='ipv4'> <dhcp/> </protocol> <vlan tag='4096'> <interface name='eno1'/> </vlan> </interface> [root@localhost ~]# virt-xml-validate vlan.xml vlan.xml:1: element interface: Relax-NG validity error : Invalid sequence in interleave vlan.xml:6: element vlan: Relax-NG validity error : Element interface failed to validate content vlan.xml:6: element vlan: Relax-NG validity error : Element vlan failed to validate attributes vlan.xml fails to validate [root@localhost ~]# Here is a ip command help on this. [root@localhost /]# ip link add link eno1 name eno1.90 type vlan help Usage: ... vlan [ protocol VLANPROTO ] id VLANID [ FLAG-LIST ] [ ingress-qos-map QOS-MAP ] [ egress-qos-map QOS-MAP ] VLANPROTO: [ 802.1Q / 802.1ad ] VLANID := 0-4095 FLAG-LIST := [ FLAG-LIST ] FLAG FLAG := [ reorder_hdr { on | off } ] [ gvrp { on | off } ] [ mvrp { on | off } ] [ loose_binding { on | off } ] QOS-MAP := [ QOS-MAP ] QOS-MAPPING QOS-MAPPING := FROM:TO
-
由 Richard Weinberger 提交于
The gid value passed to devpts has to be translated by hand as virLXCControllerSetupDevPTS() is called before setting up the user and group mappings. Otherwise devpts will use an unmapped gid and openpty() will fail within containers. Linux kernel commit 23adbe12 ("fs,userns: Change inode_capable to capable_wrt_inode_uidgid") uncovered that issue. Signed-off-by: NRichard Weinberger <richard@nod.at> Signed-off-by: NJán Tomko <jtomko@redhat.com>
-
由 Jianwei Hu 提交于
Should like below: <interface type='server'> <mac address='52:54:00:22:c9:42'/> <source address='192.168.0.1' port='5558'/> </interface> ... <interface type='client'> <mac address='52:54:00:8b:c9:51'/> <source address='192.168.0.1' port='5558'/> </interface>
-
由 Sam Bobroff 提交于
During a QEMU live migration several warning messages about job handling could be written to syslog on the destination host: "entering monitor without asking for a nested job is dangerous" The messages are written because the job handling during migration uses hard coded asyncJob values in several places that are incorrect. This patch passes the required asyncJob value around and prevents the warnings as well as any issues that the warnings may be referring to. https://bugzilla.redhat.com/show_bug.cgi?id=1130089Signed-off-by: NSam Bobroff <sam.bobroff@au1.ibm.com> Signed-off-by: NJán Tomko <jtomko@redhat.com>
-
由 Jincheng Miao 提交于
Perl is necessary to our build processing, it will invoke a lot of generating script, like: gendispatch.pl. If perl is missing, it's ok for build from git checkout, because autogen.sh will tell you. But for compiling from a release tarball, configure will just record a missing message, and continue, then build failed, like: https://www.redhat.com/archives/libvirt-users/2014-August/msg00050.html So need to enhance configure script to handle this negative case. Reported-by: NHongbin Lu <hongbin@savinetwork.ca> Signed-off-by: NJincheng Miao <jmiao@redhat.com> Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
由 Mo yuxiang 提交于
commit d9504941 introduces two new attributes "cmd_per_lun" and "max_sectors" same with the names QEMU uses for virtio-scsi. But the case of parsing them is not exact. Change to parse them if controller has "driver" element. Signed-off-by: NMo yuxiang <moyuxiang@huawei.com>
-
由 Chen Hanxiao 提交于
This patch changes the setmaxmem function to support the '--live', '--config', and '--current' flags by revectoring the code through the setmem function using the VIR_DOMAIN_MEM_MAXIMUM flag. The setmem code is refactored to handle both cases depending on the flag. The changed maxmem code for the MEM_MAXIMUM path will not allow modification to the memory values of an active guest unless the --config switch is used. Signed-off-by: NChen Hanxiao <chenhanxiao@cn.fujitsu.com>
-
- 13 8月, 2014 1 次提交
-
-
由 Peter Krempa 提交于
Libvirt is really chatty when the DEBUG log level is enabled. When a host uses journald we'd enable debug logging to journald when only specifying the debug log level. As journald may employ rate throttling this would lock up the daemon until it's able to flush all debug messages. This patch changes the default log level to VIR_LOG_INFO when using the default (unconfigured) log output to journald. To still allow debug logging to journald the user now has to explicitly specify journald as a log output with priority 1 in the "log_outputs" configuration option. This patch also changes the config file template to be explicit about this change and notify the user about the possible consequence of debug logging into journald. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1121955
-