xen November 2007

xen@lists.fedoraproject.org

39 participants
39 discussions

xen and lvm
by Augusto Castelan Carlson 08 Nov '07

08 Nov '07

Hi! I'm using fedora 7 for both host and guests. I would like to be able to borrow unused space from one guest to be used in another one. Looking for how to do that I only found instructions from people that creates logical volumes and install the system using debootstrap. I would like to use virt-manager to install my guests with lvm. How can I do the partitioning for guests during my host install? Thanks in advance. Regards, -- Augusto

3 5

Re: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart
by Aaron Metzger 07 Nov '07

07 Nov '07

yonas Abraham wrote: >> >> So, my question is, is it possible to properly manage the start up and >> shut down of guest domains on host start up and shutdown or is that just >> not supported yet. >> >> If there is a way to do this, it would be a very helpful section to add >> to the Quick Start document because I would expect anyone migrating from >> a pure Xen environment to have the same issue. Google reveals that >> several have asked this question in the past on Fedora 7 etc and I have >> not seen any answer other than people suggesting to link the >> configuration file under "/etc/xen/auto". >> >> Thanks, >> Aaron > > > I am in same boat as you. I want to know how to atuo start an image in > F7 or F8. I have seen this question asked several times and I have > seen no answer. May be it is not posible to do it. > I think I have it figured out! Edit your "/var/lib/xend/domains/<domain-uuid>/config.sxp" file. Look for the lines containing (on_xend_start ignore) (on_xend_stp ignore) and change them to be (on_xend_start start) (on_xend_stop shutdown) This will restart the domain when the xend daemon starts. Mine still fails for the case where I "reboot" the host instead of shutdown, powerup because it seems like it can not restart from the virtual machine image saved in "/var/lib/xen/save". I tried to post a log file with that failure to this list but it looks like the e-mail was to large to post or something because it hasn't shown up in this list yet. At least now I have a solution which will work when my UPS shuts down the server during a power outage. -- Aaron

2 1

What is XendInvalidDomain?
by John Summerfield 07 Nov '07

07 Nov '07

Google shows where it was introduced (it maps to a xend_ error), but not what it means. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: <Fault 3: 'ClarkConnect-4.2'> I've been trying to run this command: virsh undefine ClarkConnect-4.2 probably you won't be surprised that virt-manager hangs too, and needs a little force from KDE. At one point I found it appropriate to killall sleep vtpm-delete as there were several of each apparently going noplace. I know of these: Nov 6 12:49:29 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:51:04 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:52:40 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:54:15 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:55:50 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:57:26 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:59:01 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:00:36 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:02:13 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:03:48 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:05:23 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:06:59 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:08:36 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:10:12 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:11:47 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:11:55 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:13:22 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:14:58 potoroo logger:last message repeated 2 times Nov 6 13:16:33 potoroo logger:last message repeated 2 times Nov 6 13:18:09 potoroo logger:last message repeated 2 times Nov 6 13:19:44 potoroo logger:last message repeated 2 times Nov 6 13:19:50 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:21:20 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:22:55 potoroo logger:last message repeated 2 times Nov 6 13:24:31 potoroo logger:last message repeated 2 times Nov 6 13:26:06 potoroo logger:last message repeated 2 times Nov 6 13:27:42 potoroo logger:last message repeated 2 times Nov 6 13:29:17 potoroo logger:last message repeated 2 times Nov 6 13:30:53 potoroo logger:last message repeated 2 times Nov 6 13:32:28 potoroo logger:last message repeated 2 times but a little debugging code in /etc/xen/scripts/locking.sh hasn't case any light on my difficulties. I am running: [root@potoroo ~]# rpm -qf /etc/fedora-release /etc/xen/ /usr/bin/virt-manager fedora-release-8-2 xen-3.1.0-12.fc8 virt-manager-0.5.2-2.fc8 -- Cheers John -- spambait 1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list

3 6

f7 guest on f8t3
by John Summerfield 07 Nov '07

07 Nov '07

This is my command line, it's similar to one that worked for Debian etch and ClarkConnect 4.2 (and Windows XP): virt-install --name=Fedora7 --ram=384 --vcpus=2 --file=/var/lib/xen/images/Fedora7.img --file-size=4 --vnc --hvm --cdrom=/net/ns/var/local/mirrors/linux/Fedora/7/Fedora/x86_64/iso/F-7-x86_64-DVD.iso --os-type=linux os-variant=fedora7 Windows is fine Debian's fine ClarkConnect's fine f7 took ages loading ata_piix4 (actually it was a little further than this, that's just want was on the install screen). Ages > half an hour after which I went off to lunch. I cam back and, to my pleasant surprise, it was at the "choose your language" screen. From there things went smoothly until I chose to install from my CDROM which, of course, is that NFS mount I just booted from. Just to be absolutely clear: The host CPU is EMT-64 and virtualisation-capable. It's running 64-bit Linux. selinux is in whingealotmode, not enforcing. It's whingeing a lot, but that's for another time. The ISO image is automounted, and as it booted and loaded some stuff off it, it seems clear to me that access is fine. I've looked at the list's archive, the closest I found is an unaswered question from Greg Huber on June 13. I'm running xen 3.1, he had 3.0.? and he got much further than I can. A lot of possibly-relevant messages scrolled of the screen (fortunately I said "vga=791" so I have a reasonable number), but I can see kernel messages back to its recognising sda. There's nothing to suggest it found the virtual DVD-ROM drive. I'll scout around for some IA32 binaries, it doesn't matter a lot which I install for the purpose of this test. In the meantime, are there any pointers? -- Cheers John -- spambait 1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list

1 2

Profoss virtualisation call for papers
by Raphaël Bauduin 07 Nov '07

07 Nov '07

Hi, Profoss is organising events to spread objective information about professional uses of Free and Open Source based solutions, and is looking for speakers for its next event about virtualisation, taking place in Brussels on 22nd and 23rd january. If you have deployed a Free or Open Source virtualisation technology in a demanding professional environment, if you're a services company with extended expertise with virtualisation, or if you have developed a virtualisation software under an open source license, or built a product based on open source technology, and want to share your experience with your peers, please don't hesitate to submit your proposal as described below. Talks should not be commercial shows, but bring interesting information for professional ICT users, based on real world experience. It is not a xen specific event. Each speaker get a 50 minutes slot, and talks are to be given in english. Travel and hotel costs for speakers are taken in charge by the organisation. Please submit your proposal at http://www.profoss.eu/events/january-2008-virtualisation/call-for-papers If you have further questions, don't hesitate to send a mail to info at profoss dot eu thanks Raph

1 0

Upgrading base Fedora installation with xen
by Keith Roberts 05 Nov '07

05 Nov '07

I'm wondering if it would be possible to upgrade from one version of Fedora to another newer version using xen, without any down-time, apart from rebooting the machine to activate the new installation? Something like this; 1) create a secondary linux root partition. 2) from the current active linux partition use xen to install the new version of Fedora on the secondary linux root partition. 3) compile and install any programs to /usr/local/xyz for the new kernel on the new linux root partition. 4) tweak and setup the new linux installation on the secondary partition, so it is ready to boot into. 5) reboot the machine so that the new Fedora root partition is now the active root partition. So in theory, going from an older Fedora root partition, to a completely new installation of Fedora would only incurr the downtime of having to reboot the machine, into the ready and functioning new Fedora installation on the new root partition? Is this possible, and has anyone tried it yet please? I got as far a running xen on my machine OK, but KDE and X crashed when I tried to do anything else. Kind Regards Keith Roberts ------------------------------------------------------------ http://www.karsites.net http://www.raised-from-the-dead.org.uk This email address is challenge-response protected with http://www.tmda.net ------------------------------------------------------------

2 1

Re: [Fedora-xen] RHEL4 DomU Update Problem
by Chris Lalancette 02 Nov '07

02 Nov '07

Jim Klein wrote: > Closer. It doesn't panic any more and even sees all the partitions and > mounts, but stalls at the following point: > > SCSI subsystem initialized > Registering block device major 202 > Using cfq io scheduler > xvda: xvda1 xvda2 xvda3 xvda4 < xvda5 > > device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel(a)redhat.com > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > SELinux: Disabled at runtime. > > Processor spins all the way up to 97 percent and sits there. An xm > shutdown works (md: stopping all md devices. md: md0 switched to > read-only mode. Power down.) so it seems to be stuck in a loop. OK. That probably means you are all the way booted, and just not seeing the init output. You can try one of two things here: 1) Add "console=xvc0" to the kernel command-line when booting the RHEL-4 kernel; that should force the init output to go to the serial console. 2) Use virt-manager to view the console. At least there you should be able to see what is going on. Chris Lalancette

2 1

RHEL4 DomU Update Problem
by Jim Klein 02 Nov '07

02 Nov '07

Am attempting to update a RHEL4 domU from a custom created Xen kernel (created before RHEL5) to a supported kernel (2.6.9-55.0.9.ELxenU) and RHEL5 host without success. For some reason, the kernel can no longer find xvda. Boots fine on the old kernel and host, so I'm at a bit of a loss. Host has other domUs booted off the same SAN, with no security restrictions, so I don't see how it could be hardware. Copy of configs and partial debug log below. Ideas? Conf: name = "do5" memory = "1024" disk = [ 'phy:/dev/mpath/msa-mpathv0p1,xvda,w', ] vif = [ 'mac=00:16:3e:55:a5:65, bridge=xenbr2' ] vfb = ["type=vnc,vncunused=1"] bootloader="/usr/bin/pygrub" vcpus=1 Grub: root (hd0,0) kernel /vmlinuz-2.6.9-55.0.9.ELxenU ro root=/dev/xvda2 rhgb quiet initrd /initrd-2.6.9-55.0.9.ELxenU.img Debug: [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'do5'], ['memory', '1024'], ['vcpus', 1], ['bootloader', '/usr/bin/pygrub'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']]], ['device', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]]]) [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'do5'], ['memory', '1024'], ['vcpus', 1], ['bootloader', '/usr/bin/pygrub'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']]], ['device', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]]] [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'do5', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 1024, 'device': [('vbd', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]), ('vkbd', ['vkbd']), ('vfb', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']])], 'bootloader': '/usr/bin/pygrub', 'cpu': None, 'maxmem': None} [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 9 1.0 [2007-10-30 12:41:21 xend 4121] DEBUG (balloon:127) Balloon: 1049112 KiB free; need 1048576; done. [2007-10-30 12:41:21 xend 4121] INFO (image:136) buildDomain os=linux dom=9 vcpus=1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:199) dom = 9 [2007-10-30 12:41:21 xend 4121] DEBUG (image:200) image = /var/lib/xen/vmlinuz.6u2e9w [2007-10-30 12:41:21 xend 4121] DEBUG (image:201) store_evtchn = 1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:202) console_evtchn = 2 [2007-10-30 12:41:21 xend 4121] DEBUG (image:203) cmdline = ro root=/dev/xvda2 rhgb quiet [2007-10-30 12:41:21 xend 4121] DEBUG (image:204) ramdisk = /var/lib/xen/initrd.MpxKQP [2007-10-30 12:41:21 xend 4121] DEBUG (image:205) vcpus = 1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:206) features = [2007-10-30 12:41:21 xend 4121] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda'

3 8

HVM Xen guest CPUs allocation
by Songtao Liu 02 Nov '07

02 Nov '07

I use intel Core2 on my test PC. It seems that the configuration of Xen config file cpus="1" does not work,I want to set it load on processor1, but HVM guest will always load on processor0? Any one has ideas for this problem? Thanks

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen November 2007