From jtower at gmail.com Sun Apr 1 20:26:11 2007 From: jtower at gmail.com (Jason Tower) Date: Sun, 1 Apr 2007 16:26:11 -0400 Subject: [Fedora-xen] looking for older fc5 kernel rpms Message-ID: anyone know where i can find the following: kernel-xenU-2.6.16-1.2133_FC5.x86_64.rpm kernel-xenU-2.6.17-1.2174_FC5.x86_64.rpm none of the mirrors has them, they've been replaced by newer versions. google turns up nothing. any help would be appreciated. From graham at vpac.org Mon Apr 2 02:20:48 2007 From: graham at vpac.org (Graham Jenkins) Date: Mon, 02 Apr 2007 12:20:48 +1000 Subject: [Fedora-xen] Backing Up a Xen Guest .. Message-ID: <1175480448.2162.31.camel@sys09.vpac.org> Here's the problem. We perform full tar backups of our CentOS 4 machines in real-time at regular intervals. And when a disaster happens, we are able to restore those backups onto virgin filesystems, make the /dev/null, /dev/zero and /dev/console devices .. and boot the machine. This has worked well on standalone systems, and also on Xen 3.0.3 guests on CentOS 4.4 machines, where each guest filesystem resides on regular (Xen-host) real filesystem. But there's no way we've been able to make it work for FC6 guests on FC6 Xen hosts, where each guest disk resides in a file. The strategy goes something like: * losetup -o 32256 /dev/loop0 /XenGuests/Guest1 * mkfs -t ext3 /dev/loop0 * mount -t ext3 /dev/loop0 /mnt * cd /mnt && tar xjpf /tmp/Guest1.tbz * for i in console null zero; do /sbin/MAKEDEV -d /mnt -x $i; done * cd /tmp; umount /srv/vm1; losetup -d /dev/loop0 * xm create -c Guest1 And it always gets most of the way through .. then the guest dies. I'm guessing it's got something to do with getting the guest grub to write boot blocks. Ideas anyone .. please? -- Graham Jenkins +61 3 9925 4909 Victorian Partnership for Advanced Computing http://www.vpac.org/ PO Box 201, Carlton South, Vic. 3053, Australia From jacliburn at bellsouth.net Mon Apr 2 01:02:19 2007 From: jacliburn at bellsouth.net (Jay Cliburn) Date: Sun, 1 Apr 2007 20:02:19 -0500 Subject: [Fedora-xen] Kernel oops 2.6.20-2925.5.fc7xen with atl1 driver Message-ID: <20070401200219.0bd81040@osprey.hogchain.net> I saw reference to the atl1 driver causing a xen kernel oops in another thread on this list. I'm a co-maintainer of the atl1 driver, and I'm trying to modify the driver to work under a xen kernel in response to the poster's error report submitted over at sourceforge. I initially sent this message to fedora-kernel-list, but then discovered fedora-xen and realized it may make more sense to send it here. I can duplicate the problem under 2.6.20-2925.5.fc7xen. It happens when we load the atl1 module. Here's the oops: Unable to handle kernel paging request at ffff880382180ae8 RIP: [] swiotlb_map_page+0x54/0x125 PGD 1100067 PUD 0 Oops: 0000 [1] SMP last sysfs file: /class/net/eth0/address CPU 0 Modules linked in: atl1 mii i915 drm netloop netbk blktap blkbk ipt_MASQUERADE iptable_nat nf_nat xt_physdev bridge w83627ehf hwmon i2c_isa eeprom nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 ipt_LOG ipt_recent iptable_filter ip_tables ip6t_LOG nf_conntrack_ipv6 xt_state nf_conntrack nfnetlink xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 video sbs i2c_ec dock button battery asus_acpi backlight ac parport_pc lp parport snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss i2c_i801 i2c_core snd_pcm serio_raw snd_timer snd iTCO_wdt iTCO_vendor_support pcspkr soundcore snd_page_alloc shpchp sr_mod cdrom floppy sg dm_snapshot dm_zero dm_mirror dm_mod ata_piix ata_generic libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd Pid: 2710, comm: ip Not tainted 2.6.20-2925.5.fc7xen #1 RIP: e030:[] [] swiotlb_map_page+0x54/0x125 RSP: e02b:ffff880019f2bd28 EFLAGS: 00010246 RAX: 7fffffffffffffff RBX: ffff880000f4c070 RCX: 000000007003975d RDX: ffff880001fb5000 RSI: ffff881881f6ec58 RDI: 0000000000000012 RBP: 0000000000000002 R08: 0000000000000002 R09: ffff88002ba8a580 R10: ffff880038383780 R11: 00000000000000d0 R12: 00000000000005f0 R13: ffff88002ba8a880 R14: 0000000000000000 R15: ffff88002ba8a580 FS: 00002aaaaaac6820(0000) GS:ffffffff80579000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 0000000019d24000 CR4: 0000000000002620 Process ip (pid: 2710, threadinfo ffff880019f2a000, task ffff880026a73080) Stack: ffff88002ba8a880 0000000000000000 ffff880019f99000 ffff880019db1800 0000000000000001 ffffffff883d2be0 ffff880019f99000 ffff88002ba8a000 ffff880000f4c000 00000000fffffff4 ffff88002ba8a580 ffff88002ba8a000 Call Trace: [] :atl1:atl1_alloc_rx_buffers+0x180/0x220 [] :atl1:atl1_up+0x2f/0x660 [] :atl1:atl1_open+0x2b/0x60 [] dev_open+0x2f/0x6e [] dev_change_flags+0x5a/0x11a [] devinet_ioctl+0x235/0x59c [] __might_sleep+0x26/0xd0 [] sock_ioctl+0x1c8/0x1e5 [] do_ioctl+0x21/0x6b [] vfs_ioctl+0x25c/0x275 [] sys_ioctl+0x59/0x78 [] tracesys+0xb2/0xb7 Code: 48 8b 14 ca 48 21 c2 48 c1 e2 0c 48 85 db 48 8d 04 3a 74 11 RIP [] swiotlb_map_page+0x54/0x125 RSP CR2: ffff880382180ae8 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20 in_atomic():0, irqs_disabled():1 Call Trace: [] down_read+0x15/0x23 [] acct_collect+0x42/0x18e [] do_exit+0x200/0x809 [] do_page_fault+0x129c/0x134b [] link_path_walk+0xc5/0xd7 [] __rmqueue+0x50/0xf9 [] error_exit+0x0/0x6e [] swiotlb_map_page+0x54/0x125 [] :atl1:atl1_alloc_rx_buffers+0x180/0x220 [] :atl1:atl1_up+0x2f/0x660 [] :atl1:atl1_open+0x2b/0x60 [] dev_open+0x2f/0x6e [] dev_change_flags+0x5a/0x11a [] devinet_ioctl+0x235/0x59c [] __might_sleep+0x26/0xd0 [] sock_ioctl+0x1c8/0x1e5 [] do_ioctl+0x21/0x6b [] vfs_ioctl+0x25c/0x275 [] sys_ioctl+0x59/0x78 [] tracesys+0xb2/0xb7 I'm pretty sure what's happening is that swiotlb -- apparently used by Xen to do IO memory mapping -- doesn't like pci_map_page(). Here's the driver code snippet that does the dma mapping for our receive buffers: static u16 atl1_alloc_rx_buffers(struct atl1_adapter *adapter) { [snip} skb_reserve(skb, NET_IP_ALIGN); skb->dev = netdev; buffer_info->alloced = 1; buffer_info->skb = skb; buffer_info->length = (u16) adapter->rx_buffer_len; page = virt_to_page(skb->data); offset = (unsigned long)skb->data & ~PAGE_MASK; buffer_info->dma = pci_map_page(pdev, page, offset, adapter->rx_buffer_len, PCI_DMA_FROMDEVICE); rfd_desc->buffer_addr = cpu_to_le64(buffer_info->dma); rfd_desc->buf_len = cpu_to_le16(adapter->rx_buffer_len); rfd_desc->coalese = 0; [snip] } The Xen kernel seems to work okay if I change pci_map_page() to pci_map_single(), but there are other dma mappings in the code that seem to /need/ pci_map_page(). (We inherited this driver from the vendor, BTW.) Should swiotlb_map_page() work? I can't even /find/ the function in 2.6.21-rc5 (non-xen). Thanks, Jay From sjafri at purdue.edu Mon Apr 2 03:38:52 2007 From: sjafri at purdue.edu (sjafri at purdue.edu) Date: Sun, 1 Apr 2007 23:38:52 -0400 Subject: [Fedora-xen] Problem with compiled guest Message-ID: <1175485132.46107acc42f86@webmail.purdue.edu> The problem I am currently facing is that I cannot start a guest domain on my domain-0 I am using version 3.0.4_1 version of xen's source code. I compiled it to make a domain-0 kernel with all drivers. ( I used make install ). The domain 0 kernel compiled correctly and is now running, I can connect to the hypervisor through the virtual manager interface. The version of this kernel is 2.6.16.33-xen Now I am trying to use the same kernel as a guest domain, however I keep on getting an error (err 22: invalid argument). Most resurces on the internet state that this is a very generic error and carries very little information within. I also tried a kernel specifically compiled to act as a guest domain (make domainU), however I get the same results. The literature provided with the code states that the kernel compiled with all features can act as domain-0 and as guest domains. I am adding an excerpt from the xend-debug.log file Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line 77, in op_create dominfo = self.xd.domain_create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 228, in domain_create dominfo = XendDomainInfo.create(config) File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 194, in create vm.construct() File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1268, in construct handle = uuid.fromString(self.info['uuid'])) Error: (22, 'Invalid argument') From philipp.jaggi at snct.lu Mon Apr 2 07:50:25 2007 From: philipp.jaggi at snct.lu (=?ISO-8859-2?Q?Philipp_J=E4ggi?=) Date: Mon, 2 Apr 2007 09:50:25 +0200 Subject: [Fedora-xen] xend just running on localhost Message-ID: Dear all I've got a stupid problem with fedora core 6 and xend 3... When I specify in xend-config.spx file the xend-address to '' or '[my-ip]' nothing happens. Xend is still listening to 127.0.0.1. Does somebody know a hint for me? Where is this specified? bye Philipp =============================================== Philipp J?ggi SNCT Sandweiler bp 23 L-5230 Sandweiler +352 35'72'14'342 mailto: philipp.jaeggi at snct.lu -------------- next part -------------- An HTML attachment was scrubbed... URL: From asraikhn at gmail.com Mon Apr 2 19:16:34 2007 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 3 Apr 2007 00:16:34 +0500 Subject: [Fedora-xen] kernel OoPs after updating to 2.6.20-1.2933.fc6xen In-Reply-To: <5f0f8dba0703270426ob16c0b8o74582bd17561a809@mail.gmail.com> References: <5f0f8dba0703261404j487f03a6q29683f6dfa7a596d@mail.gmail.com> <20070326221351.GQ29393@edu.joroinen.fi> <5f0f8dba0703270426ob16c0b8o74582bd17561a809@mail.gmail.com> Message-ID: <5f0f8dba0704021216q78b0fba8ndf8d34d985c3cfb9@mail.gmail.com> Still no update for this kernel bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234008 I am wondering if they release another kernel-xen without fixing it, and we go for update it will remove our last working kernel :( And this is not something acceptable, so do you people want to to put kernel-xen in yum "exclude" ? Thanks. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Mon Apr 2 19:37:18 2007 From: bench at silentmedia.com (Ben) Date: Mon, 2 Apr 2007 12:37:18 -0700 (PDT) Subject: [Fedora-xen] kernel OoPs after updating to 2.6.20-1.2933.fc6xen In-Reply-To: <5f0f8dba0704021216q78b0fba8ndf8d34d985c3cfb9@mail.gmail.com> References: <5f0f8dba0703261404j487f03a6q29683f6dfa7a596d@mail.gmail.com> <20070326221351.GQ29393@edu.joroinen.fi> <5f0f8dba0703270426ob16c0b8o74582bd17561a809@mail.gmail.com> <5f0f8dba0704021216q78b0fba8ndf8d34d985c3cfb9@mail.gmail.com> Message-ID: In general, my experience is that xen in fedora is unstable. It usually works pretty well, but it has its rough edges, and this is hardly the first time a kernel update has broken xen. In the past, on the FC5 line, it's taken anywhere from a few days to a month or so for the fedora guys to fix an "unacceptable" problem. That said, it's not like you're paying anybody money for Fedora.... I'm sure xen is much more stable in RHEL5. BTW, you're aware you can have yum stop erasing old kernels, right? On Tue, 3 Apr 2007, Asrai khn wrote: > And this is not something acceptable, so do you people want to to put > kernel-xen in yum "exclude" ? From asraikhn at gmail.com Mon Apr 2 20:10:16 2007 From: asraikhn at gmail.com (Asrai khn) Date: Tue, 3 Apr 2007 01:10:16 +0500 Subject: [Fedora-xen] kernel OoPs after updating to 2.6.20-1.2933.fc6xen In-Reply-To: References: <5f0f8dba0703261404j487f03a6q29683f6dfa7a596d@mail.gmail.com> <20070326221351.GQ29393@edu.joroinen.fi> <5f0f8dba0703270426ob16c0b8o74582bd17561a809@mail.gmail.com> <5f0f8dba0704021216q78b0fba8ndf8d34d985c3cfb9@mail.gmail.com> Message-ID: <5f0f8dba0704021310i11930d54g234232e984cbb2e8@mail.gmail.com> Hi Ben, On 4/3/07, Ben wrote: > > In general, my experience is that xen in fedora is unstable. It usually > works pretty well, but it has its rough edges, and this is hardly the > first time a kernel update has broken xen. In the past, on the FC5 line, > it's taken anywhere from a few days to a month or so for the fedora guys > to fix an "unacceptable" problem. > > That said, it's not like you're paying anybody money for Fedora.... I'm > sure xen is much more stable in RHEL5. > > BTW, you're aware you can have yum stop erasing old kernels, right? Nope I duno how to stop yum removing old kernels :-S Thanks. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Mon Apr 2 20:31:10 2007 From: bench at silentmedia.com (Ben) Date: Mon, 2 Apr 2007 13:31:10 -0700 (PDT) Subject: [Fedora-xen] kernel OoPs after updating to 2.6.20-1.2933.fc6xen In-Reply-To: <5f0f8dba0704021310i11930d54g234232e984cbb2e8@mail.gmail.com> References: <5f0f8dba0703261404j487f03a6q29683f6dfa7a596d@mail.gmail.com> <20070326221351.GQ29393@edu.joroinen.fi> <5f0f8dba0703270426ob16c0b8o74582bd17561a809@mail.gmail.com> <5f0f8dba0704021216q78b0fba8ndf8d34d985c3cfb9@mail.gmail.com> <5f0f8dba0704021310i11930d54g234232e984cbb2e8@mail.gmail.com> Message-ID: Then you'll be interested in this conf file: /etc/yum/pluginconf.d/installonlyn.conf Note that while it's easy to roll back to an earlier kernel (assuming you still have it installed) the same is not true for rolling back xen userspace code updates, which have been just as risky to upgrade as the kernel, in my experience. Just so you know. :) On Tue, 3 Apr 2007, Asrai khn wrote: > Hi Ben, > > On 4/3/07, Ben wrote: >> >> In general, my experience is that xen in fedora is unstable. It usually >> works pretty well, but it has its rough edges, and this is hardly the >> first time a kernel update has broken xen. In the past, on the FC5 line, >> it's taken anywhere from a few days to a month or so for the fedora guys >> to fix an "unacceptable" problem. >> >> That said, it's not like you're paying anybody money for Fedora.... I'm >> sure xen is much more stable in RHEL5. >> >> BTW, you're aware you can have yum stop erasing old kernels, right? > > > Nope I duno how to stop yum removing old kernels :-S > > Thanks. Askar > From maiftikh at learn.senecac.on.ca Mon Apr 2 20:55:16 2007 From: maiftikh at learn.senecac.on.ca (Muhammad Asif Iftikhar) Date: Mon, 02 Apr 2007 16:55:16 -0400 Subject: [Fedora-xen] what are the benchmarking tools required for para and fully virtualized xen guest domains Message-ID: Can someone let me know the benchmarking tools or any code for benchmarking the performance of para and fully virtualized xen guest domains. From sakaia at jp.fujitsu.com Tue Apr 3 00:12:45 2007 From: sakaia at jp.fujitsu.com (Atsushi SAKAI) Date: Tue, 03 Apr 2007 09:12:45 +0900 Subject: [Fedora-xen] what are the benchmarking tools required for para andfully virtualized xen guest domains In-Reply-To: References: Message-ID: <200704030013.l330DJK2011194@fjmscan502.ms.jp.fujitsu.com> Hi, Have you seen this list? http://wiki.xensource.com/xenwiki/XenTest Anyway at this moment, we just need to compare native and guest performance. Thanks Atsushi SAKAI Muhammad Asif Iftikhar wrote: > Can someone let me know the benchmarking tools or any code for benchmarking the performance of > para and fully virtualized xen guest domains. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From graham at vpac.org Tue Apr 3 01:07:22 2007 From: graham at vpac.org (Graham Jenkins) Date: Tue, 03 Apr 2007 11:07:22 +1000 Subject: [Fedora-xen] Migrating An OS Installation from a Physical Machine to a Xen Paravirtual Guest Message-ID: <1175562442.24888.11.camel@sys09.vpac.org> It has been said that it's possible to do the above. Does anybody have details of how one might go about it? It's easy enough to create, then extract from .. tar images. But I can't figure how to do the grub stuff. Suggestions? -- Graham Jenkins +61 3 9925 4909 Victorian Partnership for Advanced Computing http://www.vpac.org/ PO Box 201, Carlton South, Vic. 3053, Australia From adrian at creative.net.au Tue Apr 3 01:28:42 2007 From: adrian at creative.net.au (Adrian Chadd) Date: Tue, 3 Apr 2007 09:28:42 +0800 Subject: [Fedora-xen] Migrating An OS Installation from a Physical Machine to a Xen Paravirtual Guest In-Reply-To: <1175562442.24888.11.camel@sys09.vpac.org> References: <1175562442.24888.11.camel@sys09.vpac.org> Message-ID: <20070403012842.GF26697@skywalker.creative.net.au> On Tue, Apr 03, 2007, Graham Jenkins wrote: > It has been said that it's possible to do the above. Does anybody have > details of how one might go about it? It's easy enough to create, then > extract from .. tar images. > > But I can't figure how to do the grub stuff. Suggestions? Do you need to use py-grub? All my migrations worked fine - move the entire OS into an LVM, install the Xenified kernel inside the VM and in dom0 so the kernel can boot from dom0 and the modules can load inside domU; install Xen-happy libraries so you don't get hit by the massive amounts of logging the Redhat/fedora kernels do when dealing with fixing up segment hacks. I haven't had (yet) to use py-grub. Adrian From graham at vpac.org Tue Apr 3 01:38:22 2007 From: graham at vpac.org (Graham Jenkins) Date: Tue, 03 Apr 2007 11:38:22 +1000 Subject: [Fedora-xen] Migrating An OS Installation from a Physical Machine to a Xen Paravirtual Guest In-Reply-To: <20070403012842.GF26697@skywalker.creative.net.au> References: <1175562442.24888.11.camel@sys09.vpac.org> <20070403012842.GF26697@skywalker.creative.net.au> Message-ID: <1175564302.24888.17.camel@sys09.vpac.org> On Tue, 2007-04-03 at 09:28 +0800, Adrian Chadd wrote: > On Tue, Apr 03, 2007, Graham Jenkins wrote: > > It has been said that it's possible to do the above. Does anybody have > > details of how one might go about it? It's easy enough to create, then > > extract from .. tar images. > > > > But I can't figure how to do the grub stuff. Suggestions? > > Do you need to use py-grub? > > All my migrations worked fine - move the entire OS into an LVM, install the > Xenified kernel inside the VM and in dom0 so the kernel can boot from dom0 > and the modules can load inside domU; install Xen-happy libraries so you > don't get hit by the massive amounts of logging the Redhat/fedora kernels do > when dealing with fixing up segment hacks. > > I haven't had (yet) to use py-grub. OK .. but how do you make the FC6 Xen kernel access physical partions. Something like: -- disk = [ 'phy:VolumeGroup00/ng2Root,sda1,w', 'phy:VolumeGroup00/ng2Swap,sda2,w'] -- .. doesn't work with the supplied Xen kernel. -- Graham Jenkins +61 3 9925 4909 Victorian Partnership for Advanced Computing http://www.vpac.org/ PO Box 201, Carlton South, Vic. 3053, Australia From adrian at creative.net.au Tue Apr 3 01:59:15 2007 From: adrian at creative.net.au (Adrian Chadd) Date: Tue, 3 Apr 2007 09:59:15 +0800 Subject: [Fedora-xen] Migrating An OS Installation from a Physical Machine to a Xen Paravirtual Guest In-Reply-To: <1175564302.24888.17.camel@sys09.vpac.org> References: <1175562442.24888.11.camel@sys09.vpac.org> <20070403012842.GF26697@skywalker.creative.net.au> <1175564302.24888.17.camel@sys09.vpac.org> Message-ID: <20070403015914.GI26697@skywalker.creative.net.au> On Tue, Apr 03, 2007, Graham Jenkins wrote: > On Tue, 2007-04-03 at 09:28 +0800, Adrian Chadd wrote: > > On Tue, Apr 03, 2007, Graham Jenkins wrote: > > > It has been said that it's possible to do the above. Does anybody have > > > details of how one might go about it? It's easy enough to create, then > > > extract from .. tar images. > > > > > > But I can't figure how to do the grub stuff. Suggestions? > > > > Do you need to use py-grub? > > > > All my migrations worked fine - move the entire OS into an LVM, install the > > Xenified kernel inside the VM and in dom0 so the kernel can boot from dom0 > > and the modules can load inside domU; install Xen-happy libraries so you > > don't get hit by the massive amounts of logging the Redhat/fedora kernels do > > when dealing with fixing up segment hacks. > > > > I haven't had (yet) to use py-grub. > > OK .. but how do you make the FC6 Xen kernel access physical partions. > Something like: > -- > disk = [ 'phy:VolumeGroup00/ng2Root,sda1,w', > 'phy:VolumeGroup00/ng2Swap,sda2,w'] disk = [ 'phy:data/XEN_cindy_root,sda1,w', 'phy:data/XEN_cindy_swap,sda2,w' ] Linux hosting-2 2.6.18-1.2257.fc5xen0 #1 SMP Fri Dec 15 17:35:10 EST 2006 i686 athlon i386 GNU/Linux Watch your domU dmesg and make sure that there's no errors relating unmatched Xen devices or such; you need to be sure the domU has the Xen block and network devices loaded (the Xen block device being loaded in initrd or compiled into the kernel!) or your domU won't be able to mount the root device. Adrian From rjones at redhat.com Tue Apr 3 13:02:10 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 03 Apr 2007 14:02:10 +0100 Subject: [Fedora-xen] The console is currently unavailable / vnc port = -1 Message-ID: <46125052.4050104@redhat.com> I have a machine where this is happening right now. Is there anything I can do to debug it? # uname -a Linux oirase 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:23:59 EST 2007 x86_64 x86_64 x86_64 GNU/Linux Latest libvirt/virt-manager from CVS/Mercurial. All I did was begin an FC7 install. Note the section in the XML below. # virsh dumpxml 3 fc7 d5cbd41195dc9e838387cf261583f28a linux /var/lib/xen/virtinst-vmlinuz.qfYZJ9 /var/lib/xen/virtinst-initrd.img.EOuJOf method=http://download.fedora.devel.redhat.com/pub/fedora/linux/core/development/x86_64/os/ 512000 1 destroy destroy destroy