similar to: Bug#631102: Config Files

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: grave File: xen Justification: renders package unusable Debian Squeeze Dom0, up to date. Networking is handled by OS scripts, such that br0 and br1 are bridge interfaces. Without warning, the DomU (Ubuntu 10.04 LTS) loses inbound connectivity. It tends to happen after several hours. It doesn't seem to be affected by throughput

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

Comparing my last know working configuration with the current one, it appears to be gagging on the new localhost\.localdomain that is in the configuration file. I don''t know if this got added by my machine when compiling. diff -ur xen-3.0-testing.hg/install/etc/xen/xend-config.sxp xen-unstable.hg/install/etc/xen/xend-config.sxp --- xen-3.0-testing.hg/install/etc/xen/xend-config.sxp

Package: xen-utils-common Version: 3.2.0-1~bpo4+1 Severity: minor I use the version from backports, but it's still present in sid. In /etc/xen/xend-config-sxp : #(xen-tcp-xmlrpc-server-address 'localhost') #(xen-tcp-xmlrpc-server-port 8006) should be #(xend-tcp-xmlrpc-server-address 'localhost') #(xend-tcp-xmlrpc-server-port 8006) Small typo in a commented line, but

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

Hi! New installation (debian jessie) -> missing of /etc/xen/xend-config.sxp file. Package: xen-utils-common (4.4.1-3) -- (O__ ------------------------------------------------------ //\ / Varosi Csokonai Konyvtar // ) | Tel.: 59/503-152 V__/_ szistvan at tux.hu \ szistvan at mail.vcsk.hu

Hello, I''m using Debian Squeeze with Xen 4.0 HVM. Both running 64bits. I''ve got 4 domU''s requiring the bridged setup to work, I''ve got an IP address for each. Now I need to setup routed networking for the rest of domU''s. I just changed the configuration in xend-config.sxp and restarted Xen. Routing started to work, while there are still

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, since pinning the cpu cores to Dom0 and the DomUs the shutdown of the VMs doesn''t work anymore. When shutting down or rebooting a DomU the DomU just freezes after the shutdown process but won''t reboot or stop the DomU. The shutdown itself seems to be complete though. We can reproduce this problem on 4 different servers.

Package: xen-utils-common Version: 3.0.3-0-2 Error message: # xm create test.cfg -c Error: Device 0 (vif) could not be connected. Backend device not found. /etc/xen/xend-config.sxp contains an error in its default configuration. Line 87 should read: (network-script network-bridge) Not: (network-script network-dummy)

Package: xen-utils-4.0 Version: 4.0.1-5.2 After clean upgrade from Lenny I got xend highly use CPU resources causing domU don't being created - due to timeouts for vifs and vbds (mostly CPU Steal Time was increasing - no iowaits). Tried Xen boot options acpi=noirq|ht without success. Option acpi=off solved that issue, but performance of the server was horrible. The final workaround was to

> On Sat, Apr 16, 2016 at 5:40 PM, rgritzo <rgritzo at gmail.com <https://lists.centos.org/mailman/listinfo/centos-virt>> wrote: > > so i guess i was not paying too close attention and upgraded to xen 4.6.1 before i migrated my domU configurations to libxl :{ > > Just FYI, as a fall-back you can always move yourself to the Xen 4.4 "track" by: > 1.

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

testing, uname -ri 2.6.33-rc5-4-xen x86_64 rpm -qa | grep -i Xen-4 xen-4.0.0_20873_01-29.1.x86_64 cat test.cfg name = ''test'' builder = ''linux'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [

Package: xen-utils-common Version: 4.4.1-9 Severity: important This bug was already reported as #763102 and was brushed off because maintainer says it implicates xend which is not there in 4.4 anymore. However, this problem is present during upgrade from wheezy to jessie and means that reboots are not possible without physical interventions. As noted in #763102, during shutdown, we can see this

Hi folks, is there a tool to convert a vm''s classic config file to sxp? I tried "xm create OLDCONF -n" and pasted the output in a config file at /var/lib/xend/domains/SOMEFOLDER/config.sxp, but that did not make virsh recognize the vm at all (although I restrarted xend, which helps for example after virt-clone). I am trying this on Xen4 using Debian6. Dirk

so i guess i was not paying too close attention and upgraded to xen 4.6.1 before i migrated my domU configurations to libxl :{ i have tried for a couple of hours this morning to find a way to do the conversion in a post xend world, but can?t seem to do it. I still have all my disk images, and i see the domain config.sxp configuration files in /var/lib/xend/domains/<uuid> but i am not enough

Hello! I use kernel-xen.x86_64 2.6.20-2931.fc7 virt-manager.x86_64 0.4.0-2.fc7 xen-libs.x86_64 3.1.0-2.fc7 xen.x86_64 3.1.0-2.fc7 with FC7. I want bridged networking for my virtual machines, so I create fully virtualized DomUs with virt-manager and add eth0 (bridged, as ethernet device). When I

Greetings and Happy Holiday Season: I filed an open issue with Fedora installer and rpm because of the same error. I was suggested to look in the xend-debug.log for detailed logs on the problem. This is enabled in nano /etc/xen/xend-config.sxp by adding the following lines (logfile /var/log/xend.log.debug) (loglevel DEBUG) then removing the logs rm -f /var/log/xend.log rm -f

Hi all, This is a dom0 NAT question. /etc/xen/xend-config.sxp (network-script my-network-bridge) (vif-script vif-bridge) there are two physical network cards on the box and my-network-bridge creates two bridges. domU''s use these bridges. I have some windows pc''s connected to one of the nics and I would like to use dom0 route their traffic and do SNAT. (firewall/router setup)

Hi I was experimenting with Xen(-2.0) on NetBSD last summer and I have been trying it on Debian GNU/Linux recently. I was surprised to see that my guest OS had no Internet connectivity. I took the Xen documentation, but did not find any clue: the doc basically tells ``everything should work out of the box''. I spoke about that with a friend who had already used Xen under Debian and he