http://blog.gmane.org/gmane.linux.redhat.fedora.xen hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5774 <pre>Hey folks. Right now the package owner for xen in fedora is the xen-maint alias account. Originally this was an alias that was mapped to various &lt; at &gt;redhat folks who were doing xen development, and was used for both fedora and internal RHEL stuff. Nowadays it's not really used in upstream/fedora land and fedora-virt-maint is a better suited alias. Additionally &lt; at &gt;redhat isn't doing much xen work these days so we should just have a single package owner which reflects reality. So I propose we drop xen-maint as the package owner, and Michael can 'officially' take on package ownership. If that sounds fine I'll file a ticket with fedora infrastructure to make the change (required AFAIK for alias account changes). Michael, does that sound good to you? Thanks, Cole -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Cole Robinson 2012-05-15T15:24:52 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5770 <pre>My approach is to install a DomU on top of a Fedora 16, 32 bit machine. I don't have any X running, so I need a real text install. Anaconda starts, but nothing happens after that. Below is the output. Hope someone can help. -------------------- [root&lt; at &gt;fox ~]# virt-install -l http://download.fedoraproject.org/pub/fedora/linux /releases/16/Fedora/i386/os --ram 512 --disk /var/lib/libvirt/images/f16.img,siz e=4 -n f16 --graphic none Starting install... Retrieving file .treeinfo... Retrieving file vmlinuz- Retrieving file initrd-PA Creating domain... Connected to domain f16 Escape character is ^] [ 0.000000] Reserving virtual address space above 0xf5800000 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.1.0-7.fc16.i686.PAE (mockbuild&lt; at &gt;x86-11.phx2.fedoraproject.org) (gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) ) #1 SMP Tue Nov 1 20:53:45 UTC 2011 [ 0.000000] ACPI in unprivileged domain disabled [ 0.000000] released 0 pa</pre> Lars Bjørndal 2012-05-14T06:11:37 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5764 <pre>I have built 4.1.3-rc1 for F17 and it is temporarily available for testing at http://koji.fedoraproject.org/koji/taskinfo?taskID=4063767 . Michael Young -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> M A Young 2012-05-09T19:08:35 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5750 <pre>Hi All, I've put together some resources for the Xen testing effort. http://openetherpad.org/xen-fedora-testing Please let me know if you are planning to help with this effort and I will continue to coordinate. Thanks, Todd </pre> Todd Deshane 2012-04-10T16:32:51 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5746 <pre>I'm not able to install a guest OS. I give the following command on my Fedora 16 machine, running i686: 'virt-install --connect xen:/// --os-type linux \ -l http://download.fedoraproject.org/pub/fedora/linux/releases/16/Fedora/i386/os \ --ram 512 --disk /var/lib/libvirt/images/f16.img,size=4 --name F16 \ --graphic none --paravirt --virt-type=xen \ -x "serial console=tty0 console=ttyS0,115200"' I get the following output: 'Starting install... Retrieving file .treeinfo... | 1.8 kB 00:00 ... Retrieving file vmlinuz-PAE... | 7.9 MB 00:03 ... Retrieving file initrd-PAE.img... | 257 MB 01:47 ... Creating domain... | 0 B 00:04 Connected to domain F16 Escape character is ^] error: Unable to open stream for '(null)': Bad address Domain installation still in progress. You can reconnect to the console to complete the installation process.' I'm not able to reconnect. How can I solve this problem? </pre> Lars Bjørndal 2012-04-07T12:01:01 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5745 <pre>I'm testing Xen dom0 on a Fedora 16 i686 box. I notice a process called /usr/libexec/colord, that leads to high cpu load, resulting in a spinning cpu fan. The process also runs when Xen is not running, but then the TIME reported by 'ps ax' is 0:00. As I'm blind and don't use any X or GUI, I think I don't need the colord process, so I did 'killall -9 /usr/libexec/colord'. However, this doesn't work from a script, like /etc/rc.d/rc.local, and I need to do it manually after every reboot. Where is colord started, and how can I get rid of the process? Thanks and regards, Lars -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Lars Bjørndal 2012-04-07T11:42:25 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5744 <pre>The Fedora community is holding a virtualization test day [1] next week (Thursday) and it would be great if we could help them on the Xen side of things Let me know if you are interested in helping out and I'll coordinated the Xen efforts. Thanks, Todd [1] http://fedoraproject.org/wiki/Test_Day:2012-04-12_Virtualization_Test_Day </pre> Todd Deshane 2012-04-06T17:16:38 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5725 <pre>I installed Fedora 16 and then ran: sudo yum install xen Xen installed without errors and I rebooted. In the Grub2 list I selected Xen 4.1.2 and then selected the option: Fedora Linux, with Xen 4.1.2 and Linux 3.3.0-4.fc16.x86_64 The boot process starts (i notice that loading ramdisk is very short) and then shortly thereafter the boot fails and the system reboots without any error. I tried checking the boot log but I'm not sure I'm looking at the right log. The only problem I see in the boot is Started SYSV: sandbox, xguest and other apps that want to use pam_names$ Failed to start Xenstored - daemon managing xenstore file system -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Chris Jones 2012-03-24T21:07:23 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5724 <pre>I'm having a problem with mdraid running in a DomU. The issue is that mdraid declares one leg of the raid to have failed (when there's actually nothing wrong). DomU is fc16 - 3.2.2-1.fc16.x86_64 Dom0 is fc14 - 2.6.32.26-174.2.xendom0.fc12.x86_64 The same DomU running on Dom0 fc16 - 3.2.7-1.fc16.x86_64 runs perfectly. This appears to be a known issue, however the resolution (which seems to be to disable barriers on the fly) doesn't seem to work in this case. My question is: Is it possible to pass a parameter to the blkfront driver to ask it not to enable barrier during initialization? or is there another work around? [ 1.033058] blkfront: xvda: barrier: enabled [ 1.099153] xvda: xvda1 xvda2 [ 1.102871] blkfront: xvdb: barrier: enabled [ 1.130876] xvdb: xvdb1 xvdb2 [ 1.292692] md: bind&lt;xvdb1&gt; [ 1.413416] md: bind&lt;xvda1&gt; [ 1.419411] md: raid1 personality registered for level 1 [ 1.419836] bio: create slab &lt;bio-1&gt; at 1 [ 1.419953] md/raid1:md127: active with 2 out of 2 mirr</pre> Virgil 2012-03-19T02:35:19 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5723 <pre>Hi List, I have a strange issue someone, hopefully, can advise me on. I have two external connections into a host: em1 is behind a firewall machine which is connected to an internet backbone link, while em2 is an adsl all-u- can-eat deal with a cheap router. Both are bridged. So there's pem1 and pem2 which are connected to the em1 and em2 bridges respectively. There is a domU router which nats (and is connected to both bridges). Some domU servers (a variety of fc6 to fc16 32 and 64) default route to the domU router and go out the all-u-can-eat link. The issue is, I recent upgraded the host from Fedora8 to Fedora16, and now the domU machines that once happily used the all-u-can-eat link, no longer can. However, in an act of desperation, I moved one of the domUs to a backup machine. Nothing else changed. Bingo. That domU works. All resources are still on the original machine (i.e. the DB servers, the router, etc. etc.). It seems that the router does't seem to nat domUs on the same host. You move </pre> Virgil 2012-03-13T06:16:26 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5718 <pre>Inglés : Many already we have contributed to the first project of free software dedicated to self-management in this campaign of collective financing, it collaborates and it spreads!/ Beginning campaign collective financing http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion?lang=en Login to enter with user of social networks and for would register in Goteo : http://www.goteo.org/user/login?lang=en Rebelaos! Publication by self-management A massive publication that floods the public transport, the work centers, the parks, the consumption centers, by means of distribution of 500,000 gratuitous units, acting simultaneously in all sides and nowhere. We announce the main tool of a vestibule Web for the management of self-sustaining resources by means of Drupal, in addition in the publication there will be an article dedicated to free software, hardware, It is being prepared in inglès, the machinery You can see more details in the index of the publication https://n-1.cc/pg/file/re</pre> Orquidea Salt mas 2012-03-02T15:00:07 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5717 <pre>Hi, My Fedora 17 3.3-rc4.git1 kernel boots on bare metal, but it dies very early on in the boot process when loading on top of Xen. It's got CONFIG_XEN_DOM0=y and all the other CONFIG_XEN* options are either "y" or "m". Linux panics with init[1] trap invalid opcode ip:7f99a072ff15 sp:7fffbf2a5088 error :0 in libc-2.15.so[7f99a05f8000+1ac000] init used greatest stack depth: 2392 bytes left Kernel panic - not syncing: Attempted to kill init! The kernel itself seems able to execute on top of Xen because I see a very normal-looking Xen init, then the screen blanks, then Linux initializes and starts executing early boot, stuff like the USB stack and SATA starts to come up, and then it tries to run the init process in userspace and it all comes crashing down. This is on Sandy Bridge hardware with all the CPU optional instruction sets enabled. Any ideas? Thanks, Sean -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Sean McNamara 2012-03-01T04:04:34 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5712 <pre>Hi, I tried to install a fedora onto my xen domain with virt-manager. At the third attempt I reached some success: # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3005 1 r----- 6236.5 MobileOtp 1024 1 0.0 MobileOtp2 1024 1 0.0 MobileOtp3 3 800 1 -b---- 338.4 But, when trying to issue # xm console MobileOtp3 the terminal becomes stuck and only killing the xenconsole process frees it. The installation itself did not run, how can I step ahead? - Gergely -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Gergely Buday 2012-02-07T12:46:10 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5709 <pre>Hi, I would like to install a fedora as a subdomain operating system on my fedora box. virt-manager throws the following error: libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Error creating domain: Disk image does not exist: /home/gergoe/Downloads/Fedora-16-x86_64-Live-Security.iso') I wonder as /home/gergoe/Downloads/Fedora-16-x86_64-Live-Security.iso exists. What can be the problem? - Gergely -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Gergely Buday 2012-02-06T15:46:29 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5708 <pre>Hi All, I have installed Fedora 16. [root&lt; at &gt;RSJ boot]# uname -a Linux RSJ 3.1.0-7.fc16.i686 #1 SMP Tue Nov 1 21:00:16 UTC 2011 i686 i686 i386 GNU/Linux [root&lt; at &gt;RSJ boot]# Then: 1. yum intsall xen xen got install successfully but it could not update grub entry with xen. 2. [root&lt; at &gt;RSJ boot]# xl info libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such file or directory cannot init xl context [root&lt; at &gt;RSJ boot]# 3. Then i manually updated the grub [entry = /etc/grub.d/20_linux_xen], now grub.conf: ----------------/etc/grub2/grub.conf-------------------------------- # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="${saved_entry}" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_en</pre> Rajeshwar Singh Janwar 2012-02-05T03:16:22 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5706 <pre>I have a problem with network interfaces after installing Xen. Network interface has network address but can't to bring up. [root&lt; at &gt;dom0 ~]# uname -r 3.2.2-1.fc16.i686.PAE [root&lt; at &gt;dom0 ~]# yum list | grep xen-hyper xen-hypervisor.i686 4.1.2-2.fc16 With default kernel system works perfectly. But after booting with xen kernel # dmesg | grep eth [ 15.860121] e100 0000:00:04.0: eth0: addr 0xfeafe000, irq 9, MAC addr 00:e0:81:21:53:96 [ 15.884513] e100 0000:00:05.0: eth1: addr 0xfeafd000, irq 5, MAC addr 00:e0:81:21:53:97 [ 18.506585] udevd[458]: renamed network interface eth1 to em2 [ 18.568406] udevd[457]: renamed network interface eth0 to em1 # lsmod | grep e100 e100 36014 0. mii 13311 1 e100 # lspci | grep Ethernet 00:04.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08) 00:05.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08) # ifup em1 RTNETLINK answ</pre> Sergey A. Pechiony 2012-02-03T11:59:49 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5705 <pre>I have a problem with network interfaces after installing Xen. [root&lt; at &gt;dom0 ~]# uname -r 3.2.2-1.fc16.i686.PAE [root&lt; at &gt;dom0 ~]# yum list | grep xen-hyper xen-hypervisor.i686 4.1.2-2.fc16 &lt; at &gt;updates With default kernel system works perfectly. But after booting with xen kernel # dmesg | grep eth [ 15.860121] e100 0000:00:04.0: eth0: addr 0xfeafe000, irq 9, MAC addr 00:e0:81:21:53:96 [ 15.884513] e100 0000:00:05.0: eth1: addr 0xfeafd000, irq 5, MAC addr 00:e0:81:21:53:97 [ 18.506585] udevd[458]: renamed network interface eth1 to em2 [ 18.568406] udevd[457]: renamed network interface eth0 to em1 # lsmod | grep e100 e100 36014 0. mii 13311 1 e100 # lspci | grep Ethernet 00:04.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08) 00:05.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08) # /etc/init.d/network status Configured devices: lo em1 em2 Currently activ</pre> Sergey A. Pechiony 2012-02-03T10:43:15 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5704 <pre> D.Srinivas-- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> srinivas d 2012-02-02T04:21:41 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5695 <pre>Hi All, I just update one of my Fedora 14 domU to Fedora 16 and everything when ok in the update process. But once I did the first domU reboot than I got the Error: Boot loader didn't return any data! while virt-manager reports: Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err "Boot loader didn't return any data!") details reports: raceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 589, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err "Boot loader didn't return any data!") My thought is that since Fedora 16 comes with grub2, my current xen setup doesn't support it. I also did a backport of xen4.2.1 from </pre> Roberto Fichera 2012-01-24T19:24:28 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5684 <pre>Hi there, I have installed xen through yum. How can I start it? I started xend via its init.d script but still xm info says that it cannot connect xend. What should I do then? - Gergely -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Gergely Buday 2012-01-11T15:51:42 http://comments.gmane.org/gmane.linux.redhat.fedora.xen/5672 <pre>This is what happened: normally ran 'yum install xen' and that gave no problems, but then i rebooted to get to the xen kernel, it resulted on black screen (could change consoles with Alt + F2 etc.) so i rebooted and tried the regular 3.1.2 kernel with same results. uninstalled xen with 'yum history undo' so it would also remove all dependencies then rebooted. nothing. anyone knows what could have caused this? im running f16 x86_64 on an asus g74sx-bbk7(core i7-2630qm, geforce gtx560m, 8GB DDR3 ram) -- xen mailing list xen&lt; at &gt;lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen</pre> Carlos Felipe Santacruz 2011-12-06T15:14:57 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.redhat.fedora.xen