similar to: Problem with convert config file to xml

Displaying 20 results from an estimated 200 matches similar to: "Problem with convert config file to xml"

2015 Oct 01
0
xen and spice problem
Am 2015-10-01 12:24, schrieb Fabio Fantoni: > > Qemu seems crashed, can you post qemu log of this domU for see the > exact problem? > Also domU's xl cfg can be useful and/or backtrace of qemu crash with > gdb depending on the error of qemu crash. > thats the config of domU: builder = 'hvm' memory = 2048 vcpus=8 boot="c" name = "marax"
2017 Apr 14
0
optimal windows xml config for xen
Hi I use this config to start win7 64bit via virsh: <domain type='xen' id='21'> <name>marax</name> <uuid>6df7f16c-50e1-4541-b5b1-a91ff675a7c2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>8</vcpu>
2013 Sep 20
0
[PATCH v2] libxl: spice usbredirection support for upstream qemu
Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. It requires an usb controller and creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. The default is disabled (0). Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> --- docs/man/xl.cfg.pod.5 | 6 ++++++ tools/libxl/libxl.h |
2013 Oct 08
0
[PATCH v3] libxl: spice usbredirection support for upstream qemu
Usage: spiceusbredirection=NUMBER (default=0) Enables spice usbredirection. Creates NUMBER usbredirection channels for redirection of up to 4 usb devices from spice client to domU''s qemu. It requires an usb controller and if not defined will automatically adds an usb2 controller. Changes from v2: - updated for usbversion patch v7 - now usbredirection cannot be used with usb and
2020 Feb 06
1
Re: PCI/GPU Passthrough with xen
I know these are mostly gamers but they have a lot of experience doing PCI pass though: https://discord.gg/du9ecG I have found them extremely helpful in the past doing libvirt PCI passthough. *Paul O'Rorke* On 2020-02-05 10:13 a.m., Jim Fehlig wrote: > On 2/4/20 1:04 AM, Christoph wrote: >> this config does not work... why? > > Without more details, I don't know why
2020 Jul 27
0
Problem with xen config
Hi all, I 've such a config on xen (4.14): name = "marax.chao5.int" uuid = "e0de3cb7-3937-417d-8d63-b0993b377b6a" maxmem = 16384 memory = 16384 kernel = '/usr/lib64/xen/boot/hvmloader' vcpus = 16 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vif = [
2020 Feb 04
0
Re: PCI/GPU Passthrough with xen
this config does not work... why? <domain type='xen'> <name>marax.chao5.int</name> <uuid>72f8f7cf-d538-41cd-828a-9945b9157719</uuid> <memory unit='GiB'>32</memory> <currentMemory unit='GiB'>32</currentMemory> <vcpu placement='static'>16</vcpu> <os> <type
2015 Oct 01
5
xen and spice problem
Hi it is possible to use xen and spice already? If yes is there any howto or doc how? If I turn on spice in cfg of a hvm domU, I get this error: Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail:
2013 Nov 19
13
[PATCH v7 1/2] libxl: usb2 and usb3 controller support for upstream qemu
Usage: usbversion=1|2|3 (default=0, no usb controller defined) Specifies the type of an emulated USB bus in the guest. 1 for usb1, 2 for usb2 and 3 for usb3, it is available only with upstream qemu. The old usb and usbdevice parameters cannot be used with this. Changes from v6: - now usbversion cannot be used with usb and usbdevice parameters - now default is 0 (no usb controller defined) Will be
2013 Aug 27
3
[PATCH v4] libxl: Spice vdagent support for upstream qemu
Usage: spicevdagent=1|0 (default=0) Enables spice vdagent. The Spice vdagent is an optional component for enhancing user experience and performing guest-oriented management tasks. Its features includes: client mouse mode (no need to grab mouse by client, no mouse lag), automatic adjustment of screen resolution, copy and paste (text and image) between client and domU. It also requires vdagent
2019 Apr 26
2
5.2.0 xen and maxGrantFrames
Hi libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). I get ever an error if I use it in the config: <domain type='xen'> <name>satan.chao5.int</name> <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory>
2019 Apr 26
0
Re: 5.2.0 xen and maxGrantFrames
On Fri, Apr 26, 2019 at 11:25:13AM +0200, Christoph wrote: > > Hi > > libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). > I get ever an error if I use it in the config: Hi > <domain type='xen'> > <name>satan.chao5.int</name> > <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> > <memory
2010 Mar 29
0
Interesting lockdep message coming out of blktap
I''m getting this: blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_validate_params: aio:/dev/vg_lilith-raid/xen-f13-64: capacity: 20971520, sector-size: 512 blktap_device_create: minor 0 sectors 20971520 sector-size 512 blktap_device_create: creation of 253:0: 0 INFO: trying to register non-static key. the code is fine but needs
2019 Apr 26
1
Re: 5.2.0 xen and maxGrantFrames
error: Failed to create domain from /etc/libvirt/libxl/satan_pvh.xml error: internal error: libxenlight failed to create new domain 'satan.chao5.int' and with an other domU with this config: <domain type='xen'> <name>abaddon.chao5.int</name> <uuid>2ebe8981-b443-4052-a996-22f377c19cc6</uuid> <memory
2012 Nov 14
0
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3
Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol
2012 Apr 17
0
Save/restore error with xen-unstable and qemu upstream
Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version 3.2.12-1, package blktap-dkms and all dependency packages for xen, spice and usb redirection. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is 25194:6b72eb3b40cf) # Qemu
2012 Nov 14
1
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3
Hello, I've tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can't support SPICE, so I installed upstream qemu. (http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and spice-protocol
2012 Nov 14
1
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) when creating VM using upstream qemu on Xen 4.2.
Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and
2015 Oct 01
0
xen and spice problem
On Thu, Oct 1, 2015 at 10:06 AM, Christoph <mangel at gmx.de> wrote: > Hi > > it is possible to use xen and spice already? If yes is there any howto or > doc how? Fabio has been the one working on getting spice working. Fabio, any ideas? > > If I turn on spice in cfg of a hvm domU, I get this error: > > Parsing config from /etc/xen/marax.cfg > libxl: detail:
2015 Oct 01
0
xen and spice problem
Am 2015-10-01 12:33, schrieb Fabio Fantoni: > Should be something like /var/log/xen/qemu-dm-marax.log oh ok: qemu-system-i386: -spice port=6000,tls-port=0,addr=0.0.0.0,password=test,agent-mouse=on: There is no option group 'spice' spice is not supported by this qemu build. qemu-system-i386: -spice port=6000,tls-port=0,addr=0.0.0.0,disable-ticketing,agent-mouse=on: There is no