September 2007 - xen - Fedora Mailing-Lists

by Shirazi, Goodarz

Hi, I'm running FC7 with the 2.6.20-2931.fc7xen kernel and used virt-manager to configure a xp guest domain. I receive the following message after trying to run the xp guest: virsh # start xp (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') virsh # dumpxml xp <domain type='xen' id='-1'> <name>xp</name> <uuid>0fe4b14b-ce6a-d84c-dc69-1f9e0cce544d</uuid> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <memory>512000</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <devices> <emulator>/usr/lib/xen/bin/qemu-dm</emulator> <interface type='bridge'> <source bridge='eth0'/> <target dev='vif-1.0'/> <mac address='00:16:3e:72:d3:89'/> </interface> <disk type='file' device='disk'> <driver name='file'/> <source file='/var/lib/xen/images/xp.img'/> <target dev='hda'/> </disk> <disk type='file' device='cdrom'> <driver name='file'/> <source file='/var/lib/xen/images/winxp.iso'/> <target dev='hdc'/> <readonly/> </disk> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1'/> </devices> </domain> winxp.iso one provided in such a way: dd if=/dev/cdrom of=/var/lib/xen/images/winxp.iso for an assistance I am very grateful, Goodarz

16 years, 7 months

1
0
0 / 0

Resend: qemu-kvm error message

by John Lagrue

Can anyone throw some light on this? I get the following message when starting qemu-kvm on Fedora 7 Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. But /proc/sys/dev/rtc doesn't exist! JDL

16 years, 7 months

2
1
0 / 0

domU disregard static IP information at boot time

by Costa Kavanides

My dom0 has kernel 2.6.20-2931.fc7xen whereas the fully virtualised domU has kernel 2.6.21-1.3194.fc7. I wanted a static IP address for the domU thus I specified it during installation + in the xen config file. Notwithstanding all my efforts to tell it that it has to use a static IP address, whenever domU boots it always look for a DHCP server to get its IP address from. Even changing the lines in ifcfg-eth0 to define a static IP address is not a solution. With next reboot it still wants a DHCP server to provide the IP address. Changing ifcfg-eth0 + issuing an "service network restart" works as long as there is no reboot. As soon as I reboot the odd behaviour prevails. Where may act to change this behaviour? costa ------------------------- domU xen config file -------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 256 shadow_memory = 8 name = "Test_2_FC7" vif = [ 'type=ioemu, ip=192.168.2.29, mac=00:16:3e:00:00:11, bridge=xenbr0' ] disk = [ \ 'file:/home/XEN/images/FC7_disk_2.img,hda,r', \ 'phy:/dev/cdrom,hdb:cdrom,r', \ ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' boot = "c" sdl=1 vnc=0 stdvga=0 serial='pty' usbdevice='tablet' ____________________________________________________________________________________ Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. http://tv.yahoo.com/

16 years, 7 months

1
1
0 / 0

Guest Installation via local http fails

by Claus Reheis

Hi all! I found some time and thought about playing around with Xen 3.1 in Fedora 7! I tried to setup Fedora 7 as a para-virtualized guest on a Fedora 7 host with help of a nice howto in the O`Reilly book about Fedora what suggest the folling steps: 1)Setup a network installation server in Dom0: setenforce 0 ln -s /media/disk/ /var/www/html/fedora service httpd start 2)Start the Installation with virt-manager The installation starts up fine until I can choose the installation method!I choose http and after I always get the Error message: "Unable to retrieve http://192.168.0.123/fedora//images/stage2.img " The strange things are the two *//* !I cant get rid of it!I tried any combination who came to my mind, but no success until now... When I open Firefox and go to http://192.168.0.123/fedora/images/stage2.img or localhost/fedora/images/stage2.img the file just downloads fine without any error! I tried the http installation from a fedora server: http://limestone.uoregon.edu/ftp/fedora/linux/7/Fedora/x86_64/os/ No problem either! So what is wrong with my attempt to install from the local server? Thanks for your help, Claus

16 years, 7 months

3
3
0 / 0

Re: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7

by Jim Klein

Oops! Sorry guys - this was my fault. I had read somewhere (I thought it was on this list) that there was compilable source for paravirt drivers in there, but hadn't actually checked it out before I mentioned it to Jack. I said that I hadn't had a chance to check them out, but I wasn't real clear in my email (was typing on a cell phone, so I wasn't real wordy.) My bad. --Jim >Date: Thu, 13 Sep 2007 14:20:32 +0100 >From: "Daniel P. Berrange" <berrange(a)redhat.com> >Subject: Re: [Fedora-xen] Xen Windows paravirtualized drivers in >Fedora 7? >To: "achan(a)jonathan360.com" <achan(a)jonathan360.com> >Cc: fedora-xen(a)redhat.com >Message-ID: <20070913132031.GC23525(a)redhat.com> >Content-Type: text/plain; charset=us-ascii > >On Thu, Sep 13, 2007 at 09:08:11AM -0400, achan(a)jonathan360.com wrote: >> It was my understanding that windows drivers in paravairtualization is >> not possible because of the windows kernel, not because of lack of >> drivers. For it to work properly the kernel would need altered which is >> against the EULA of Microsoft. At least that was my understanding. > >That is partially true. If you want to use the DDK, then it is not possible >to make your drivers GPL, but you could choose other open source licenses >I believe. You would end up with a situation where the source was technically >one license, but the binary became a different license. eg BSD source, but >Combined BSD / Microsoft DDK for the binary. In theory you don't have to >use the DDK, but not doing so would involve huge amounts of extra programming >work. It all rather sucks, but that's Windows for you. IANAL btw :-) > >Dan. >

16 years, 7 months

1
0
0 / 0

Xen Windows paravirtualized drivers in Fedora 7?

by Pasi Kärkkäinen

http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid3... "Finally, Klein said the Windows drivers are already included in the latest Fedora 7 updates but he hasn't had a chance to test them yet. "They are clearly sticking to the timeline they suggested at the Red Hat Summit, in that they won't be releasing the paravirt drivers for Windows until after the 5.1 release," Klein said." Could someone comment on this.. Xen in Fedora 7 includes windows paravirtualized drivers?? -- Pasi

16 years, 7 months

3
5
0 / 0

Fedora 7 + kernel 2.6.20-2931 + Xen + clvmd gives spinlock bug and hangs

by Robert Verspuy

Hi All, I'm pretty new in the xen and clustering stuff, but I have the following setup: 2 server (2 x dual Xeon 2GHz, 6GB RAM, 2 x 160GB SATA + 4 x 400GB SATA) Running both fedora 7, latest updates (kernel 2.6.20-2931.fc7xen) I want to set this up as both Dom0's are the storage nodes (with GFS2) And both server are running 2 or 3 XEN VM's with the application (2 x bind, 2 x postfix, 1 x mysql, 1 x postgresql). And the possibility to migrate a VM to the other server in case of any problems. The 2 x 160GB is setup as an raid 1, on top of that LVM with local volumes for /boot, / and <swap> This should hold the local files the 4 x 400GB is setup as 3 disks RAID 5 and 1 disk spare, giving me about 800GB of usable diskspace. On top op the RAID 5 I have DRBD, to keep both raid devices between both server in sync. With DRBD v8 it is possible to use them active/active, if you use a cluster aware file system (like GFS2) So I've setup openais, and cman. Running on both servers, interacting fine. When starting clvmd, I get the following (on both servers): Sep 10 10:08:55 fosfor kernel: BUG: spinlock already unlocked on CPU#0, dlm_recoverd/4016 (Not tainted) Sep 10 10:08:56 fosfor kernel: lock: ffff88016158fd50, .magic: dead4ead, .owner: <none>/-1, .owner_cpu: -1 Sep 10 10:08:56 fosfor kernel: Sep 10 10:08:56 fosfor kernel: Call Trace: Sep 10 10:08:56 fosfor kernel: [<ffffffff8020b97c>] _raw_spin_unlock+0x2e/0x7f Sep 10 10:08:56 fosfor kernel: [<ffffffff88370233>] :dlm:dlm_lowcomms_get_buffer+0xf7/0x1cb Sep 10 10:08:56 fosfor kernel: [<ffffffff8836c375>] :dlm:create_rcom+0x3a/0xb3 Sep 10 10:08:56 fosfor kernel: [<ffffffff8836cb81>] :dlm:dlm_rcom_status+0x58/0x137 Sep 10 10:08:56 fosfor kernel: [<ffffffff8836d066>] :dlm:dlm_set_recover_status+0x1a/0x2e Sep 10 10:08:56 fosfor kernel: [<ffffffff8836beb8>] :dlm:dlm_recover_members+0x332/0x3ea Sep 10 10:08:56 fosfor kernel: [<ffffffff80294813>] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [<ffffffff8836df8f>] :dlm:dlm_recoverd+0x399/0x3e3 Sep 10 10:08:56 fosfor kernel: [<ffffffff8836dbf6>] :dlm:dlm_recoverd+0x0/0x3e3 Sep 10 10:08:56 fosfor kernel: [<ffffffff80294813>] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [<ffffffff80232bae>] kthread+0xd0/0xff Sep 10 10:08:56 fosfor kernel: dlm: got connection from 1 Sep 10 10:08:56 fosfor kernel: [<ffffffff8025ba68>] child_rip+0xa/0x12 Sep 10 10:08:56 fosfor kernel: [<ffffffff80294813>] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [<ffffffff80232ade>] kthread+0x0/0xff Sep 10 10:08:56 fosfor kernel: [<ffffffff8025ba5e>] child_rip+0x0/0x12 Sep 10 10:08:56 fosfor kernel: After that, two dlm processes are running at 100% cpu load at one processor. (also on both servers) When I stop the clvmd service, the server hangs (only the server, where I stop the clvmd) According to http://www.redhat.com/archives/linux-cluster/2007-April/msg00133.html and specially http://www.redhat.com/archives/linux-cluster/2007-April/msg00171.html I should use a kernel 2.6.21 or newer. But this is not available for fedora 7 with xen. I also tried to use an older kerne (2.6.20-2925.9.fc7xen) both that doesn't work also. Or can the cause of this problem be located somewhere else? Does anybody know when a newer kernel for fedora 7 with xen will be released (don't see any new kernel in testing also...) Thnx in advance, Robert Verspuy

16 years, 7 months

1
0
0 / 0

How do Xen 3.1x guest connect to a sound card?

by kosago

How do you pass the pci sound card to xen 3.1x guest using virsh?

16 years, 7 months

2
1
0 / 0

restore failed

by Augusto Castelan Carlson

Hi! I have Xen (fedora 7 with xen 3.1.0) running with 2 guests (both fedora 7). At night I save both guest and mount their partitions to do a backup. Then I restore the saved machines. Everything appears to be working fine, but I had some problems with restore this weekend. When I arrived to work, one of the guest was not running properly. I tried to shutdown the machine and start it again, but got the following error when trying to start: virsh # start virtual_machine_name libvir: Xen Daemon error : POST operation failed: (xend.err "'uname'") error: Failed to start domain virtual_machine_name Seeking for any problem in log files I found some errors: [2007-09-07 09:14:16 2285] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it. : : [2007-09-07 09:14:18 2557] DEBUG (XendDomainInfo:1463) XendDomainInfo.constructDomain [2007-09-07 09:14:18 2557] DEBUG (balloon:113) Balloon: 64248 KiB free; need 2048; done. [2007-09-07 09:14:18 2557] ERROR (XendDomainInfo:434) VM resume failed : : I can attach my full log if needed. I did a restore with a previous saved session and the guest is running ok now. What can be done so that those errors do not occur any more? Thanks in advance, -- Augusto Castelan Carlson

16 years, 7 months

1
0
0 / 0

qemu-kvm error message

by John Lagrue

Can anyone throw some light on this? I get the following message when starting qemu-kvm on Fedora 7 Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. But /proc/sys/dev/rtc doesn't exist! JDL

16 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen September 2007