similar to: RE: domU not starting

>> I think he''s having problems with Dom0 changing >> Mac address, rather than the domU (is that right?) Yes, you are correct. It''s dom0 that seems to be getting a random MAC and because of that Xen can''t t find the NIC and won''t load eth0 because the MAC is different than what is expected. I''ve seen others with the same problem and their

CentOS 4.1, Xen 2.0.7. My dom0 is booting up but can''t get to the outside network because eth0 won''t start due to, apparently, Xen providing a different mac address than expected. How do I tell Xen to start eth0 at the bootup with a specific mac address that lines up with the HWADDR= line in my ifcfg-eth0? Note that a normal bootup into CentOS 4.1 outside of the Grub Xen bootup

On Thu, 2015-09-10 at 09:06 +0200, Wolfgang Karall-Ahlborn wrote: > After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto > fails with errors like this > > Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. > Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

Hi All, I have searched for a bit and haven''t found anything. I am having an issue with DomU''s persisting (even after a reboot) that aren''t running, and can''t be destroyed. Problem is I cant create one with the same name either. This is Xen 3.3.0 on Centos 5.2. [root@COBRA1 ~]# xm list Name ID Mem VCPUs State

Hello list, I''m trying to build a linux kernel module that uses xenstore to report on the modules loaded into a DomU''s kernel. When building against the current unstable (changeset 15080:089696e0c603) I''m getting build errors about not being able to find mach_mpspec.h and mach_apicdef.h make -C /root/xen-unstable.hg/linux-2.6.18-xen O=/root/xen-

Hopefully I summed up the jist of the problem in the subject line. ;) I have a GFS cluster with ten Xen 3.0 dom0s sharing an iSCSI LUN. There are on average 8 domUs running on each Xen server. The dom0 on each server is hard-coded to 2 CPUs and 2GB of RAM with no ballooning, and has 2GB of partition-based swap. When creating a new domU on any of the Xen servers, just after the completion of

Package: xen-utils-4.1 Version: 4.1.3-4 Severity: important Tags: patch Bug presented in sid, with patch attached. Similar bug is also present in stable and testing versions. How to reproduce: Install xen-utils-4.1 in a domU, and run: /etc/init.d/xen start Expected result: xenstored running (or to have any other easy way to get it running within a domU) xenstored is not just something

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

Hi, I want to know how everything communicates with XenStore. Do domUs use the front-end/back-end driver to dom0 and then the back-end driver contacts xenstored? In particular, how do the xenstore-* commands work on a dom0 and domU? And when should unix-domain sockets be used to communicate with xenstored? Thanks, Hayawardh _______________________________________________ Xen-users mailing

Hey everyone, I''m trying to write a simple python program in dom0 that registers a watch on the xenstore to determine when a domU has shutdown. Is there a particular token I should use? Looking through the tools/python/xen/*.py code, I''ve come across the ''control/shutdown'' token... seems promising? My code is attached below. As is, if fails to call the

After startup of the DomU with xm create mydomu.cfg ­c The startup always stops, when starting the Cron-Daemon. [ 1.810477] EXT3 FS on xvda1, internal journal Loading kernel modules...done. Cleaning up ifupdown.... Setting up networking.... Activating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 done. Mounting local filesystems...done. Activating swapfile

Hi, I am posting this message because past 36 hours have been nightmare for me. I finally have solved the problem I by temporarily moving put the xml files from /var/lib/xend directories reboot then xend started. And DomU''s were failing to start the above xml files I kept back and got all DomU''s back. I am very very surprised.I do not have any logical answer to this some one

Hi, I''ve got Xen running on an FC5 system with two DomU guests defined. They both start Ok when the server boots, or if I manually start them using "xm create ..." However, one one of them the network doesn''t start automatically. i have to connect to the console and run "service network start" to bring up eth0. It starts OK when I do it manually. I then

Hi. I compiled the xen binaries and the kernel with the sources. DomO starts without any problems, but when I run domU, it stops and freeze. My domU is a clone of my domO. ___________________________________________ unmounting old /dev unmounting old /proc unmounting old /sys INIT: version 2.86 booting rtc: IRQ 8 is not free. modprobe: FATAL: Error inserting rtc

Hi, I am not able to start a new domainU on FC5. To start the new domain I give command xm create -c domU.conf vmid=1. This gives me the following error: VFS: Mounted root (ext3 filesystem) readonly. Kernel panic - not syncing: No init found. Try passing init= option to kernel. Call Trace: <ffffffff80128d62>{panic+134} <ffffffff801083a6>{init+908}

It seems that xenstore watches do not work from domU userspace (they obviously do for drivers). In some preliminary debugging of this, there are two aspects of the failure: not sending the watch to xenstore and not handling watch events for userspace watches. The former can be easily fixed by adding the missing ''case XS_WATCH:'' to xenbus_dev_write() in xenbus_dev.c. The

At least from the ''xm'' commands'' interface, it looks like domU''s just disappear after an ''xm destroy'', which I''ve been using to cut turn off the virtual power switches of domU''s. Is this by design? I''m trying to think of a good way to identify a domU throughout its lifecycle, which for me goes all the way from

I got a strange problem: I need to get sysinfo() data from domU in my application, running in dom0. Right now I using a userspace daemon in every domU, updating information in xenstore, and my application read this information... But I think, it really strange: why we can not get those info directly from PV kernel without going to kernel and back to userspace multiple times? Is any way to get

Hello! I''m investigate strange behaviour of vfb in paravirt domU (centos 5) VNC servers started after creating domain, but information in xenstore appears sometimes after 1-2 minutes after start. Why this happening? And how can i get VNC port immediate after creating of domU? Thank''s. -- Vasiliy G Tolstov <v.tolstov@selfip.ru> Selfip.Ru

When installing xen-utils-V in a driver domain domU, it drags in xen-utils-common, which also contains the init script for xenstored and xenconsoled. Installing the package will fail right away, because it exits non-zero after checking whether it's running in a xen dom0 or not: systemd[1]: Starting LSB: Xen daemons... xen[7215]: Starting Xen daemons: (warning). systemd[1]: xen.service: