December 2007 - xen - Fedora mailing-lists

How is network bridging for Xen handled in F7?
by Christian Reiter 06 Feb '08

06 Feb '08

Hi! Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. All what i want is: xenbrINTERNET should bridge to eth1 xenbrLAN should bridge to eth0 eth0 and eth1 of my dom0 should also have an IP Address. I do not want routing or nat for my domUs. Thanks! regards, christian

3 7

Guest VM dropping connection.
by Ubaidul Khan 15 Jan '08

15 Jan '08

I am running RHEL5 Guest and Host. The guest OS is dropping network connections occasionally(I noticed my ssh session suddenly terminated). The guest is configured with private network interface and a public network interface. Following are the bridge/network settings for the host: bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif2.0 vif1.0 peth0 vif0.0 xenbr1 8000.fefffffffffe no vif2.1 peth1 vif0.3 xenbr1 is dedicated to provide the private network link for the guest os. Following is the guest OS configuration: # Automatically generated xen config file name = "saleen_webvm0" memory = "1000" disk = [ 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w' ] vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1, bridge=xenbr1',] # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',] vfb = ["type=vnc,vncunused=1"] uuid = "122374dc-26a3-cb0d-99f8-3393e2481777" bootloader="/usr/bin/pygrub" vcpus=2 on_reboot = 'restart' on_crash = 'restart' Following is the output of ifconfig: eth0 Link encap:Ethernet HWaddr 00:14:4F:40:D8:70 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:79313 errors:0 dropped:0 overruns:0 frame:0 TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6619719 (6.3 MiB) TX bytes:115448 (112.7 KiB) eth1 Link encap:Ethernet HWaddr 00:14:4F:40:D8:71 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:720 (720.0 b) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:105404 errors:0 dropped:0 overruns:0 frame:0 TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9122426 (8.6 MiB) TX bytes:1997833 (1.9 MiB) Base address:0x8c00 Memory:fa5e0000-fa600000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FE inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0 TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12420212276 (11.5 GiB) TX bytes:523849820 (499.5 MiB) Base address:0x8800 Memory:fa5c0000-fa5e0000 vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:2174 errors:0 dropped:0 overruns:0 frame:0 TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:446031 (435.5 KiB) TX bytes:6941997 (6.6 MiB) vif2.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:10084 errors:0 dropped:0 overruns:0 frame:0 TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1186096 (1.1 MiB) TX bytes:7380350 (7.0 MiB) vif2.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:5337343 errors:0 dropped:0 overruns:0 frame:0 TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:403712612 (385.0 MiB) TX bytes:12383227754 (11.5 GiB) Any help is greately appreciated. _________________________________________________________________ http://liveearth.msn.com

3 3

Are 64bit Intel Core 2 Quad fedora 8 supported?
by George Refseth 08 Jan '08

08 Jan '08

The 64 bit xen host kernel are unstable (timer/scheduling issue?) So I wonder if this is supported or not. Another Fedora 8 x86_64 installation on an Intel Core 2 Duo seems to run flawlessly, except it is running on a laptop, and not meant for server use. Attached are smolt output. I would be grateful for any input, this was meant to be a system where multiple services should run (several 64bit F8's) serving dns, web and mail, and replace at least two current lumps of hardware.. regards, George -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

5 7

RE: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
by Christian Lahti 03 Jan '08

03 Jan '08

Hi Mark: Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow! /Christian ________________________________ From: Mark Nielsen [mailto:mnielsen@redhat.com] Sent: Sat 12/1/2007 3:19 PM To: Christian Lahti Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? hmm, did you mean "Hi Mark" ?? I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP for cluster suite communications on the dom0 (physical) cluster. Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public network for the dom0 cluster on bond1.100 (for example, that would be VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each of these bond/VLAN devices. This allows me to put any particular VM on any particular (or combination up to 3) of these xen bridged bonded VLAN device. My document explains, in detail, how to do all of this :) The only added step is that I have to "undefine" (virsh net-undefine default) the default network that the new libvirt creates (virbr0). Even with this new NAT thing they added, I've been told (by our devs) that the preferred way to do static network configurations is with the method I lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, etc). I'm pretty sure there weren't any significant changes in Fedora 8 (we've dropped the word "core" now, btw) that don't exist in RHEL 5.1 with respects to the network. 5.0 -> 5.1 is when that NAT change came down the pipe. Mark p.s. I'm happy to answer any other questions you may have about my document. I'm quite certain that, if you follow it, you'll have what you're looking for. Christian Lahti wrote: > Hi Dale: > > I work with David who posted the original question to the mailing > list. I think we need to give a bit more background info on what we > are trying to do. We are running a mixed environment of mostly CentOS > 3, 4and 5, we do have a few windows servers and XP systems as well. > We are looking to virtualize all these platforms. Normally we have a > bonded pair of NICs for the physical hosts, we were able to get this > running using CentOS 5 x86_64 with no problems, the guest machines use > the bonded pair in bridged mode as expected after a bit of tweaking. > The biggest issue we found with EL5 is that windows guest performace > is dismal at best, hence our decision to have a look at Fedora Core 8 > x86_64. I am happy to report that performance for all of our guest > platforms is *very* good with FC8, but it seems that libvirt changed > the way networking is setup for Xen. The default NAT configuration is > pretty useless for production server environment. Thanks to the > mailing list we are now able to bridge a single NIC on FC8 (like eth0 > for example), but we cannot figure out how to get a bridge for bond0 > (comprised of eth0 and eth1) defined and available to Xen. All the > tweaks that worked find on EL5 have not worked so far on FC8. I am > going to review your document tomorrow and give it a try, but any idea > on whether your methodology will work on FC8 and libvirt? I am > willing to blow a Sunday to get this worked out once and for all :) > > Basically we are after good performance on both para and fully > virtualized guests using a bonded pair of GB NICs for speed and > redundancy. If this can be achieved with enterprise linux then that > would be preferable, but we will go FC8 if the bonding thing can be > sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 > and has pretty good performance but their free version is limited to > 32bit (and hence 4GB ram). Adding the clustering failover is the next > step of course :) > > Thanks again for the help so far. > > /Christian > > > > >>>>>>>>>>> > just FYI for the list, I have a how-to for a bonded and VLAN tagged network. > > http://www.certifried.com > > ODT and PDF formats available. > > > It might not be the best way, but I've sent it out to my colleagues > several times and have never received any negative feedback. > Mark > > > > Dale Bewley wrote: > > > I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen redhat com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > **************************************************************************** > Checked by MailWasher server (www.Firetrust.com) > WARNING. No FirstAlert account found. > To reduce spam further activate FirstAlert. > This message can be removed by purchasing a FirstAlert Account. > **************************************************************************** > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen >

5 9

Preview Xen 3.2 rc* packages
by Ian Jackson 02 Jan '08

02 Jan '08

I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I have managed to get a set of packages which appear to be able to work at least in my simple `does this work at all' test. I'm mentioning it here so that you can have a look at what I've done and comment on it. We'll probably be making official upstream rpms for Fedora 8. Please send me feedback either here on-list or privately. Most of the patches from -13.fc8 have been incorporated upstream so I just deleted them from my srpm. A couple of these patches I've included I have also submitted upstream and they'll be in xen-unstable.hg soon if they're not already. There were two patches that looked like they would be useful upstream: xen-qemu-bootmenu.patch pygrub-manykernels.patch but I wasn't able to find clear attribution for the source of this code. Xen upstream operates a `Signed-off-by' protocol to ensure that we don't get bitten by copyright problems. Where should I look to try to find the authors/contributors to check on the copyright status ? In my package I have included the hypervisor in the xen-*.rpm rather than making a kernel package too. This is more in line with practice upstream. The new hypervisor seems to work for me with the 2.6.21-2952.fc8xen kernel. I have not included xen-net-bridge.patch which seemed quite a surprising set of changes to me. I was rather puzzled by the part of xen-initscript.patch which removes most of xend's startup code. I agree that xend's arrangements are not entirely ideal but is there really much to be gained by making that changes, which obviously makes the patchset much more fragile ? You can find the actual files here: http://www.chiark.greenend.org.uk/~ijackson/xen-3.2rc-fedora8/ THESE PACKAGES SHOULD NOT BE USED FOR PRODUCTION - they're previews, and Xen 3.2 is still unreleased and in need of more testing. Please check the SHA256's before installing them: 1209de4470cf505113e684fe8f1f5c13faad40ad8eb4c456e8741eddbe5b6254 xen-3.1.9-0.fc8.i386.rpm 18ad4f2b35c6918ab3070e43d238487f6cbaf10a682cfc90b1d11c4640957395 xen-3.1.9-0.fc8.src.rpm 428da514ccf9064244017a5068c399ec0e7c5816c2d2f4ded17e9af031d50759 xen-debuginfo-3.1.9-0.fc8.i386.rpm 98305f6fc7de7c965b7cb0426a0bed4cb977394a8fce1cedf6fb35d6780df0c5 xen-devel-3.1.9-0.fc8.i386.rpm f45e0ed7ff40bf7ef4e8cd236f639060caba27d3573003745bfa37f3ae0f4943 xen-libs-3.1.9-0.fc8.i386.rpm Regards, Ian.

2 5

Where's my VM gone?
by Evan Lavelle 30 Dec '07

30 Dec '07

I'm on F8, and decided to have a go a creating a PV guest on LVM (x86_64 F8 DomU on x86_64 F8 Dom0) using virt-install. virt-manager doesn't appear to do anything on my (out-of-the-box) F8 Dom0; you just enter a root password, and the GUI disappears. I've already done a couple of other guests 'manually' on this DomU, without problems. It took me a few hours to get through installation, because of various problems with NFS firewalls, DNS problems, and so on. I had to abort the install several times. when this happened, my previous VM name was 'used up'. xm list showed a zombie domain with that name, even if the installation had barely started. I couldn't start a new installation with the same name, because virt-install complained that the VM already existed. So, I Googled around, found others with the same problem, and found out that I could remove the zombie entry with 'virsh undefine'. I eventually created a VM with the correct name, which ran Ok, and shut down the machine. This morning I turned on the box, did an 'xm list', and found what appeared to be a zombie with the new VM name (no ID, no status; just a name). So, I virsh undefined it. This seems to have been a big mistake. I then discovered that virt-install doesn't create a config file, and there was nothing in /var/lib/xend/domains, presumably because of the undefine (none of this is documented in Fedora7VirtQuickStart, by the way). How do I get my VM back? Is there some way to get the XML config back? If not, is my only option to manually make an /etc/xen config file? There's a little bit of information in xend.log which I could use for the config file. Finally, I'm (very) confused about what exactly is 'Xen' and what exactly is 'Fedora'. You seem to have done various things which I'm guessing are Fedora-specific, but which don't seem to be documented (I've had a lot of trouble with /etc/inittab, for example). Is this documented somewhere? And am I going to run into any problems if I convert a virt-install domain back to plain-old-Xen? Thanks - Evan

2 2

kvm crash on f8
by John Summerfield 29 Dec '07

29 Dec '07

I looked at some images in /var/lib/xen/images/ and since they have partition tables and look, to me, just like disks, I copied part of my hard disk to /var/lib/xen/images/WindowsXP.img The reason is that I want to try the Windows XP that came preinstalled, and copying /dev/sda for a length I calculated includes the entire /dev/sda1 partition seems a likely way to test it. These are the commands: dd if=/dev/sda of=/var/lib/xen/images/WindowsXP.img count=76597082 dd of=/var/lib/xen/images/WindowsXP.img seek=320072933376 bs=1 count=0 the second makes the disk image seem to be the proper size. I tried to start it like so: qemu-kvm -boot c -snapshot -m 256 -smp 2 -std-vga \ /var/lib/xen/images/WindowsXP.img and it choked: [root@potoroo ~]# qemu-kvm -boot c -snapshot -m 256 -smp 2 -std-vga /var/lib/xen/images/WindowsXP.img vram_pointer=0x2aaac0b5d000 exception 0 (0) rax 0000000000000022 rbx 0000000000007000 rcx 000000000064e165 rdx 0000000000000100 rsi 00000000ffff7c05 rdi 000000000008ffea rsp 0000000000001ffe rbp 0000000000000000 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 000000000000fce2 rflags 00033206 cs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 0800 (00008000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr 0000 (10850000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt fad00/30 idt 0/3ff cr0 60000010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 code: d5 03 e4 fc 24 44 d5 03 3e 00 d4 03 00 c0 f8 01 00 00 d5 03 --> f6 fc 24 44 d5 03 3f 00 d4 03 00 c0 f8 01 00 00 d5 03 08 fd 24 44 d5 03 40 00 d4 03 00 c0 Aborted [root@potoroo ~]# Here is the source disk: Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd42ad42a Device Boot Start End Blocks Id System /dev/sda1 * 1 8669 69633711 7 HPFS/NTFS /dev/sda2 8671 9715 8393962+ 7 HPFS/NTFS /dev/sda3 9716 9728 104422+ 72 Unknown /dev/sda4 9729 38913 234428512+ 5 Extended /dev/sda5 9729 9741 104391 83 Linux /dev/sda6 9742 38913 234324058+ 8e Linux LVM [root@potoroo ~]# Partitions 2 and up are unimportant. fdisk on the disk image reports: Command (m for help): p Disk /var/lib/xen/images/WindowsXP.img: 0 MB, 0 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd42ad42a Device Boot Start End Blocks Id System /var/lib/xen/images/WindowsXP.img1 * 1 8669 69633711 7 HPFS/NTFS /var/lib/xen/images/WindowsXP.img2 8671 9715 8393962+ 7 HPFS/NTFS /var/lib/xen/images/WindowsXP.img3 9716 9728 104422+ 72 Unknown /var/lib/xen/images/WindowsXP.img4 9729 38913 234428512+ 5 Extended Command (m for help): q but I had to specify the number of cylinder, 38913 but qemu-kvm rejects that nonsense. Is there a better way to do this? I really want to test running this Windows under Linux before allowing it to use the real disk. -- 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 You cannot reply off-list:-)

6 18

Accessing data on a xen guest disk image
by Dennison Williams 29 Dec '07

29 Dec '07

I asked this question in the fedora forums (http://forums.fedoraforum.org/showthread.php?t=176102) but no one seemed to have a answer. I have installed and worked with a few different xen guests via the instructions at FedoraXenQuickstartFC6 (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6) In doing this I installed the guests on a LVM volume and would like to access the guest disk image. There is documentation on howto do this in the above wiki (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184ae…) The problem I have is that my dom0 has the same logical and physical volume names for its root device as my domU (ie. VolGroup00, LogVol01). Does anyone know how to get around this name space collision so that I can mount my guest disk? Sincerely, Dennison Williams

2 6

Problem in xend http server
by chetan saundankar 28 Dec '07

28 Dec '07

Hi all, I have a problem with starting the xend http server, following are the details. I would like to know the cause of the problem and solution for the same. Thanx in advance Regards Chetan /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Setup: Intel core 2 duo 2.33, Intel DG33 mboard Fedora Core 8 Xen 3.1.2 Installed using xen RPM's (dom0: 2.6.21-2952.fc8xen) ////////////////////////////////////////////// xend-config.sxp //////////////////////////////////////////////////////// (Commented part removed) (xend-http-server yes) (xend-unix-server yes) (xend-unix-path /var/lib/xend/xend-socket) (xend-port 8000) (xend-address '') (xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') (network-script network-bridge) (vif-script vif-bridge) (dom0-cpus 0) (vncpasswd '') /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////// brctl show //////////////////////////////////////////////////////// bridge name bridge id STP enabled interfaces eth0 8000.0019d1960140 no peth0 virbr0 8000.000000000000 no /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////// xm log output //////////////////////////////////////////////////////// [?1034h[2007-12-28 04:05:58 2174] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 04:05:58 2174] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 04:05:58 2174] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 19962276671L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 04:05:58 2174] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 04:05:58 2174] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 04:05:58 2174] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 04:05:58 2174] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 04:05:58 2174] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 04:05:58 2174] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 04:08:55 2174] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 12:17:24 2237] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 12:17:24 2237] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 12:17:24 2237] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 24247516743L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 12:17:24 2237] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 12:17:24 2237] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 12:17:24 2237] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 12:17:24 2237] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 12:17:25 2237] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 12:17:25 2237] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 12:55:51 2237] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 13:16:19 2191] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 13:16:19 2191] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 13:16:19 2191] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 21997384561L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 13:16:19 2191] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 13:16:19 2191] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 13:16:19 2191] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 13:16:19 2191] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 13:16:20 2191] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 13:16:20 2191] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 13:30:32 2191] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 13:46:15 2359] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 13:46:15 2359] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 13:46:15 2359] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 22162061462L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 13:46:15 2359] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 13:46:15 2359] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 13:46:15 2359] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 13:46:15 2359] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 13:46:19 2359] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 13:46:19 2359] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 02:38:32 2359] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 02:38:34 31390] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 02:38:34 31390] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 02:38:34 31390] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 02:38:34 31390] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5353219220361L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 02:38:34 31390] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 02:38:34 31390] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 02:38:34 31390] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 02:38:34 31390] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 02:38:34 31390] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 02:38:34 31390] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 02:38:34 31390] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 02:52:15 31390] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 02:52:16 31614] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 02:52:16 31614] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 02:52:16 31614] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 02:52:16 31614] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5461808608907L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 02:52:16 31614] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 02:52:16 31614] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 02:52:16 31614] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 02:52:16 31614] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 02:52:16 31614] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 02:52:16 31614] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 02:52:16 31614] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:12:05 31614] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:12:05 32047] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:12:05 32047] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:12:05 32047] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:12:05 32047] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5590097350536L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:12:05 32047] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:12:05 32047] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:12:05 32047] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:12:05 32047] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:12:05 32047] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:12:05 32047] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:12:05 32047] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:13:48 32047] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:13:49 32119] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:13:49 32119] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:13:49 32119] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:13:49 32119] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5598967971398L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:13:49 32119] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:13:49 32119] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:13:49 32119] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:13:49 32119] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:13:49 32119] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:13:49 32119] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:13:49 32119] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:14:19 32119] ERROR (SrvServer:144) Server HttpServer did not initialise! [2007-12-29 03:36:38 32119] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:36:39 32295] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:36:39 32295] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:36:39 32295] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:36:39 32295] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5758188473089L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:36:39 32295] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:36:39 32295] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:36:39 32295] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:36:39 32295] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:36:39 32295] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:36:39 32295] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:36:39 32295] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:37:09 32295] ERROR (SrvServer:144) Server HttpServer did not initialise! [2007-12-29 03:53:40 32295] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:53:40 32462] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:53:40 32462] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:53:40 32462] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:53:40 32462] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5937486844602L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:53:40 32462] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:53:40 32462] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:53:40 32462] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:53:40 32462] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:53:40 32462] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:53:40 32462] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:53:40 32462] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:54:11 32462] ERROR (SrvServer:144) Server HttpServer did not initialise! ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

1 0

problem booting xen-kernel on fedora core 6 plz help!!
by shashank rachamalla 20 Dec '07

20 Dec '07

I installed fedora core 6 by turning acpi off and fc6 (kernel without xen) boots properly but the xen-kernel is not booting. i get the message "unknown interrupt" while udev is starting.

1 0

Starting system message bus take very long
by Yonas Abraham 20 Dec '07

20 Dec '07

starting f8 guest on f8 host , takes very long time (like 10 min) after it printed Starting system message bus It continue with out any error message after that. any idea? /yonas

2 1

Single User Mode
by Boin, Paul (Cont, ARL/CISD) 19 Dec '07

19 Dec '07

I'm testing some kickstarts on xen. Everything's OK, but I'm stuck on one part. I've researched my question well, and I'm just not getting one piece. The pw set during install is intentionally bogus. I now want to go to my grub menu, go single-user and set it via 'passwd'. ( Which we typically do on non-virtual installations. ) On RHEL, where I have much more experience, I can just "xm create -c mydomain" to get an immediate attach and see the grub menu. It looks like this newer xen/libvirt on FC8 is setup to use virsh, and it has the XML configs over in /var/lib/xend/domains/, etc. So, how do I get to the grub menu using virsh, since xm seems to want to work with plaintext configs in /etc/xen, which I do not have? Or, how would you suggest I change the bogus root pw, that no one knows? Thanks and have a fine day. # rpm -q xen xen-3.1.0-13.fc8 # rpm -q libvirt libvirt-0.3.3-2.fc8

1 0

virt-install hangs for fc6,7
by john maclean 19 Dec '07

19 Dec '07

Hey guys, First post and apologies if this has been up OT before. virt-install fails to create a domU for FC6/7. Distro of node is BLAG, an FC derivative. Just jump to the end to the end of the boot up message to see where the domU hangs. /var/log/xen/xend.log indicate no warnings or explanations why this domain has failed to be "born". Commands used:- /usr/sbin/virt-install --name fx6foo \ --paravirt \ --ram 256 \ --nographics \ --file-size 10 \ --file /dev/zulu_images/fx6foo \ --location http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/o… or [root@zulu ~]# virt-install --paravirt \ > --name fx7template \ > --ram 256 \ > --nographics \ > --file-size 10 \ > --file /dev/zulu_images/fx7template \ > --location http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/o… Typical output:- Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file Fedora... 434 kB 00:02 Retrieving file vmlinuz.. 100% |=========================| 2.1 MB 00:09 Retrieving file initrd.im 100% |=========================| 5.4 MB 00:26 libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:01 Linux version 2.6.20-2925.9.fc7xen (kojibuilder(a)xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red H at 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000010800000 end: 0000000010800000 type: 1 Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection Zone PFN ranges: DMA 0 -> 67584 Normal 67584 -> 67584 HighMem 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 67056 Kernel command line: method=http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora… Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c135f000 soft=c133f000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 2806.356 MHz processor. Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1064 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 Memory: 245120k/270336k available (2030k kernel code, 16724k reserved, 1079k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xd1000000 - 0xf4ffe000 ( 575 MB) lowmem : 0xc0000000 - 0xd0800000 ( 264 MB) .init : 0xc130e000 - 0xc133b000 ( 180 kB) .data : 0xc11fb8b9 - 0xc1309714 (1079 kB) .text : 0xc1000000 - 0xc11fb8b9 (2030 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 7023.08 BogoMIPS (lpj=14046165) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 7, 524288 bytes) TCP bind hash table entries: 8192 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7264k freedIA-32 Microcode Update Driver: v1.14-xen <tigran(a)veritas.com> audit: initializing netlink socket (disabled) audit(1196625149.792:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k # Everything seems to hang from here. Made a few cups of coffee/cigarettes to see if it was just the box being slow.... # detached and listed domains... # detaching from console... Domain installation still in progress. You can reconnect to the console to complete the installation process. [root@zulu ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1000 2 r----- 1072.2 cx5foo 256 1 24.7 cx5template 256 1 0.0 cxmon 256 1 24.7 fx6foo 256 1 0.0 fx7template 13 256 1 -b---- 1.7 fxfoo 256 1 0.0 zcx1dump 256 1 0.0 /var/log/xen/xend.log is not reporting any problems. Clues? Would be nice to be able diagnose this one. -- Regards, John Maclean Msc (DIC) + 44 7739 1717 531

3 4

Booting from floppy image
by Costa Kavanides 19 Dec '07

19 Dec '07

I read other entries about this subject but none explain why it is not possible to boot from a floppy image with XEN even though it is possible to do so with QEMU. Under dom0(2.6.21-6.fc7xen) I issue the command: qemu -boot a -fda <my-floppy-image> -hda <my-C-disk-image> and I get to boot from the floppy image, whereas when I use xen whose config file contains 'file:<my-floppy-image>,ioemu:fda:fda,r' or 'file:<my-floppy-image>,fda,r' in the <disk> clause, I get the following message in the booting window: Booting from Floppy... Boot from Floppy failed: could not read the boot disk FATAL: No bootable device. The QEMU monitor shows that, while disk-C image was taken into consideration as such, the equivalent <file> command for the floppy disk was completely ignored. Furthermore, it expects the floppy media to be present in the drive, as the following lines from the monitor's <info block> command show: hda: type=hd removable=0 file=<my-disk-C-image> ro=0 drv=raw hdb: type=cdrom removable=1 locked=0 [not inserted] fda: type=floppy removable=1 locked=0 [not inserted] Can somebody explain whether that behaviour was the result of a design choice or error? Let me emphasize the importance to have this feature. Thanks, Costa ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

1 0

Re: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core
by Darryl Bowler 18 Dec '07

18 Dec '07

I'm sure its not a bios setting, because when I boot into Vista it sees 2 cpus. ----- Original Message ---- From: Lamont Peterson <lamont(a)gurulabs.com> To: Fedora Xen <fedora-xen(a)redhat.com> Sent: Tuesday, December 18, 2007 2:55:21 AM Subject: Re: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core On Monday 17 December 2007 10:41:26 pm Darryl Bowler wrote: > I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200. > > Xen only detects one of two cores Have you checked your BIOS config? I've heard of (though none of my multi-core systems have such) support in some BIOSes to enable/disable he 'extra' cores. -- Lamont Peterson <lamont(a)gurulabs.com> Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

1 0

AMD 64 X2 5200 - XEN only detects one core
by Darryl Bowler 18 Dec '07

18 Dec '07

I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200. Xen only detects one of two cores First I installed Fedora 8 + Xen that ships with the distro and found that only one core was detected when DOM0 booted. Out of frustration I decided to install CentOS 5.1 as a quick resolution to the problem, but found the same problem. checking /proc/cpuinfo there is only one core [root@dom0 lib]# more /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ stepping : 2 cpu MHz : 2593.594 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht sysca ll nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy bogomips : 6485.48 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc Heres dmesg from CentOS Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet) Linux version 2.6.18-53.el5xen (mockbuild(a)builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2 -14)) #1 SMP Mon Nov 12 02:46:57 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000a5250000 (usable) On node 0 totalpages: 676432 DMA zone: 676432 pages, LIFO batch:31 DMI 2.5 present. ACPI: RSDP (v002 ACRSYS ) @ 0x00000000000f80c0 ACPI: RSDT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe3000 ACPI: FADT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe3080 ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x00000000affe7cc0 ACPI: HPET (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000098) @ 0x00000000affe7f80 ACPI: SLIC (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000020) @ 0x00000000affe7fc0 ACPI: MCFG (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe8140 ACPI: MADT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe7c40 ACPI: DSDT (v001 ACRSYS ACRPRDCT 0x00001000 MSFT 0x03000000) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override.Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2593.594 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Software IO TLB enabled: Aperture: 64 megabytes Kernel range: 0xffff880004847000 - 0xffff880008847000 PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Memory: 2563840k/2705728k available (2357k kernel code, 133072k reserved, 1326k data, 172k init) Calibrating delay using timer specific routine.. 6485.48 BogoMIPS (lpj=12970967) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 (SMP-)alternatives turned off ACPI: Core revision 20060707 Brought up 1 CPUs sizeof(vma)=168 bytes sizeof(page)=56 bytes sizeof(inode)=560 bytes sizeof(dentry)=216 bytes sizeof(ext3inode)=760 bytes sizeof(buffer_head)=96 bytes sizeof(skbuff)=240 bytes ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to xen Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at b4000000 (gap: b0000000:30000000) Built 1 zonelists. Total pages: 676432 [2007-12-18 01:59:05 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_me mory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destr oy', 'name': 'Domain-0', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '2635', 'o n_crash': 'restart', 'maxmem': '2635'} ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

inittab corrupted/serial console broken on Xen-ified kernel?
by Evan Lavelle 14 Dec '07

14 Dec '07

[this is a message that I sent to xen-users yesterday, but I guess this list may be better - this looks like a problem either in Xen, or in the packaging of 2.6.21-2952.fc8xen]. I've just installed Fedora 8 / xen-2.6.21 on a headless server, but I can't get a serial console login on the Xen version of the kernel. 1 - If I boot into 2.6.23.8-63.fc8, the serial console login works as expected 2 - If I boot into 2.6.21-2952.fc8xen instead, I get all the expected serial output up to the end of the boot process, but no login. When I boot into the xen kernel, inittab is modified, and the modification removes the agetty on ttyS0. If I compare the old inittab with the new inittab, I get: 46,47c46 < # co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav < co:12345:respawn:/sbin/agetty ttyS0 115200 vt100 --- > co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav In other words, a commented entry was uncommented, and the following line was deleted, which explains why I can't log in. This is so bizarre that it almost looks like it was done on purpose (was it ? :)) Anyone seen this? Any ideas? Thanks - Evan

2 3

Problem installing a para 32 bit FC5 guest on a 32 bit FC7 domU
by Greg Hellings 11 Dec '07

11 Dec '07

I'm trying to install a 32 bit FC5 paravirt guest on a 32 bit FC7 domU and I'm getting the following error: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Everything I read says this should work. The hypervisor will allow me to install a 32 bit FC7 guest fine. The following is a cut and paste the commands I'm actually putting in and their output; [root@localhost ~]# virt-install --os-variant=fedora5 --name=dddev --location=http://167.208.15.27/FC5/i386 -f /var/lib/xen/images/dddev.img -p -r 3072 --vnc --vcpus=4 Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file fedora.cs 100% |=========================| 2.3 kB 00:00 Retrieving file vmlinuz.. 100% |=========================| 1.2 MB 00:00 Retrieving file initrd.im 100% |=========================| 2.0 MB 00:00 libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start dddev'; otherwise, please restart your installation. Mon, 10 Dec 2007 08:50:01 ERROR virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Traceback (most recent call last): File "/usr/sbin/virt-install", line 474, in <module> main() File "/usr/sbin/virt-install", line 438, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 708, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 725, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 573, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 i686 i386 GNU/Linux [root@localhost ~]# cat /proc/cpuinfo |egrep pae flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr Does anyone have any idea what I'm doing wrong? Please help. -- Greg Hellings

2 1

RE: [Fedora-xen] (no subject) - (Win HVM not booting) - FIXED!
by Gary Catalano 11 Dec '07

11 Dec '07

Thanks to everyone who sent me responses on my original issue. I got it resolved and it's humming along! =) I've been doing some benchmarking on my Windows-on-Xen instance and the numbers are pretty low for certain kinds of tests. Is there a general assumption about the performance that one can expect from a Xen-instance (i.e. 70% of the speed of a real system, etc.)? I've got my virtual machine running with 1 virtual cpu and 2gb of RAM, running windows xp. Many thanks! Gary Catalano

1 0

align fix for vmm-create.glade
by Dan Horák 11 Dec '07

11 Dec '07

Hello, in the virt-manager's new VM wizard there is a small alignment inconsistency on the "Locating installation media" page for paravirtualized machine. The second and third label are right aligned, while the first (Install Media URL) is not. The included patch fixes this issue. With regards, Dan Horak

2 1

Fedora 8 - Linux HVM Guest - PV Drivers
by Emre Erenoglu 11 Dec '07

11 Dec '07

Hi, I'm trying to use a linux HVM guest (DomU) with Paravirtual drivers for network and disk access on my updated Fedora 8 setup. In order to achieve this, I've downloaded the source package of appropriate (same version) Xen Hypervisor from redhat website, then copied this source to my DomU and compiled the unmodified_drivers folder following the steps mentioned in the README file. Everything went fine and I got my xen-platform-pci, xen-baloon, xen-vnif and xen-vbd (.ko) drivers. They modprobe fine, however, after some time, the DomU freezes up. Specifically, system freezes quicker (usually) with only vbd, and takes more time to free with only xen-vnif loaded into memory. When I say only, xen-platform-pci always loaded, but only the mentioned driver is netfront or block-front, others are ioemu. xen-vnif also complains about a memory leak when it's rmmod 'ed. Shall I file a bug report? Thanks, Emre Erenoglu erenoglu(a)gmail.com

2 1

Network Problem after update 3.0 -> 3.1: blkback
by kadafax 11 Dec '07

11 Dec '07

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 "$dir/network-bridge" "$@" vifnum=2 " So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The interfaces are good in the domU, all seems to be ok but there are no connectivity at all (no arp entries). This message shows up on the dom0 each time I launch a domU: blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) Do someone know what is happening ? this is very embarrassing after a simple upgrade... Hopefully I have another identical server (Centos 5.0 with 5.1 domUs) which is still in 3.0 but I cant stay not updated. Thanks for any help. xm info: host : host.foo.com release : 2.6.18-53.1.4.el5xen version : #1 SMP Fri Nov 30 01:21:23 EST 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100800:00000000:00000180:0000641d total_memory : 4095 free_memory : 3246 xen_major : 3 xen_minor : 1 xen_extra : .0-53.1.4.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Fri Nov 30 00:37:12 EST 2007 xend_config_format : 2

3 3

xen-unstable => 3.2, binary packages
by Ian Jackson 10 Dec '07

10 Dec '07

We hope to be releasing upstream Xen 3.2 soon. As you'll know, we've been in the habit of producing binary packages for our releases, including for Fedora. It seemed to me that the best approach would be, where possible, to use a distro's own packaging setup. That would be more likely to generate packages which integrate well with the distro and behave more like the distro's own Xen packaging arrangements. I haven't looked at the FC6 srpm in detail yet but what would you think about it if we were to generate our 3.2 binary rpms based on that ? Regards, Ian.

6 18

(no subject)
by Gary Catalano 10 Dec '07

10 Dec '07

Greetings! I'm having a problem with fedora8 and Xen 3.1.0. I'm trying to get Windows to run under Xen (I've been using these instructions http://www.xensource.com/files/xen_install_windows.pdf) and I get all the way to the last steps but when I start my virtual machine I get an error saying it can't find a bootable drive: CDROM boot failure code : 0002 Boot from CD-Rom failed: could not read the boot disk FATAL: No bootable device. Here's the .hvm I'm using to launch my virtual machine: # -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses 'hvm'. builder='hvm' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 1024 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. # shadow_memory = 8 # A name for your domain. All domains must have different names. name = "win2k3-001" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to 'xm create'. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # The number of cpus guest platform has, default=1 #vcpus=1 # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 # Enable/disable HVM guest ACPI, default=1 (enabled) #acpi=1 # Enable/disable HVM APIC mode, default=1 (enabled) # Note that this option is ignored if vcpus > 1 #apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ 'type=ioemu, mac=00:16:3e:00:00:94, bridge=xenbr0' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' ] #disk = [ 'file:/.img,hda,w', ',hdc:cdrom,r' ] #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'destroy' # # restart = 'always' means on_poweroff = 'restart' # on_reboot = 'restart' # on_crash = 'restart' # # restart = 'never' means on_poweroff = 'destroy' # on_reboot = 'destroy' # on_crash = 'destroy' #on_poweroff = 'destroy' #on_reboot = 'restart' #on_crash = 'restart' #============================================================================ # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' #----------------------------------------------------------------------------- # Disk image for cdrom= "/tmp/win2k3srv.iso" #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="d" #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 vnc=0 #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #---------------------------------------------------------------------------- # set VNC display number, default = domid #vncdisplay=1 #---------------------------------------------------------------------------- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #---------------------------------------------------------------------------- # enable spawning vncviewer for domain's console # (only valid when vnc=1), default = 0 #vncconsole=0 #---------------------------------------------------------------------------- # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect #serial='pty' #----------------------------------------------------------------------------- # Qemu Monitor, default is disable # Use ctrl-alt-2 to connect #monitor=1 #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw='sb16' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------------- # set the real time clock offset in seconds [default=0 i.e. same as dom0] #rtc_timeoffset=3600 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) #usb=1 # Enable USB mouse support (only enable one of the following, `mouse' for # PS/2 protocol relative mouse, `tablet' for # absolute mouse) #usbdevice='mouse' #usbdevice='tablet' #----------------------------------------------------------------------------- # Set keyboard layout, default is en-us keyboard. #keymap='ja' Any help would be appreciated. Gary Catalano IT Manager Cryptic Studios (408) 399 -1969 x150 (office) (650) 776-2500 (cell) www.crypticstudios.com

2 1

Panic with 32bit RHEL4 on 64bit RHEL5
by Jim Klein 07 Dec '07

07 Dec '07

Am experiencing a domU panic when running 32bit RHEL4 (2.6.9-67.ELxenU) on 64bit RHEL5 (2.6.18-53.el5xen) under high load conditions. Problem has not occurred (so far) when hosting the same domU on 32bit RHEL5, so I'm a little stumped. Any ideas or recommendations would be greatly appreciated. Thanks in advance! Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01496c9 2c84c000 -> *pde = 00000000:9a3e9027 1b3eb000 -> *pme = 00000000:bfd81067 1c064000 -> *pte = 00000000:00000000 Oops: 0000 [#1] SMP Modules linked in: md5 ipv6 autofs4 sunrpc dm_mirror xennet ext3 jbd dm_mod xenblk sd_mod scsi_mod CPU: 0 EIP: 0061:[<c01496c9>] Not tainted VLI EFLAGS: 00010287 (2.6.9-67.ELxenU) EIP is at zap_pte_range+0x279/0x489 eax: 00046000 ebx: 00000000 ecx: f5392000 edx: 00000000 esi: 000b0b21 edi: c1f75bc0 ebp: 00000000 esp: e5aa3e04 ds: 007b es: 007b ss: 0068 Process amavisd (pid: 30894, threadinfo=e5aa3000 task=e54146c0) Stack: b0b21067 00000000 00000000 00000000 00000000 00000000 00046000 0a800000 c202d2a0 e548a2a8 0a846000 00000000 0a800000 c0149980 c202d2a0 e548a2a0 0a800000 00046000 00000000 0a7c6000 e5486008 0a846000 00000000 c01499e5 Call Trace: [<c0149980>] zap_pmd_range+0xa7/0xcb [<c01499e5>] unmap_page_range+0x41/0x65 [<c0149ad6>] unmap_vmas+0xcd/0x1e8 [<c014ec19>] exit_mmap+0x85/0x15b [<c011a2d9>] mmput+0x52/0x77 [<c011a74b>] copy_mm+0x36c/0x396 [<c011b26a>] copy_process+0x6b5/0xb0b [<c011b7ad>] do_fork+0x8a/0x16b [<c0105cff>] sys_clone+0x24/0x28 [<c010734f>] syscall_call+0x7/0xb Code: 8b 4c 24 14 8b 41 04 85 c0 75 0a 83 39 00 0f 45 c1 89 44 24 14 c7 44 24 10 00 00 00 00 8b 44 24 18 39 44 24 10 0f 83 08 02 00 00 <8b> 55 00 8b 4d 04 85 d2 75 08 85 c9 0f 84 e6 01 00 00 88 d0 a8

2 1

Update to Xen 3.1.2 available for testing
by Daniel P. Berrange 07 Dec '07

07 Dec '07

FYI, in both Fedora 7 & and Fedora 8, I have got new updates of the Xen userspace to be sync to the latest Xen 3.1.2 bugfix release available for testing. If you wish to test this, you can do yum --enablerepo=updates-testing update xen If there are no major problems reported I will push these to 'updates' in about a week. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

2 2

fedora 8 : exit a windows VM
by nooroon 07 Dec '07

07 Dec '07

Hi, I'm testing a fedora 8 and it was a good surprise for me : virtualization tools are more usable, and virtualization with xen seems more stable. I'm using xen to create a windows xp VM. the only issue that I have, is when i ask windows to stop the machine, with traditionnal windows tools : start>shutdown computer the windows OS is stopping but the VM doesn't stop. It hangs on a windows screen that says "you can now safely stop the computer". With xen and fedora 7, I didn't have this issue. Does anyone have an explanation?

2 2

Problem booting Fedora 8 guest on FC6 host
by Robin Bowes 06 Dec '07

06 Dec '07

Hi, I'm trying to get a Fedora 8 para-virtual guest to run on a FC6 host. I had problems with the install because of the bugs in the 0.200 release of virtinst. I fixed this by doing a source install of virtinst-0.300. The F8 install completed succesfully, but when the guest boots I get this msg: <snip initial boot msgs> md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "vg_skeggles/lv_root" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Has anyone got any ideas about how to fix this? I am currently using kernel-xen-2.6.20-1.2952.fc6 and xen 3.0.3-9.fc6 (I've upgraded to kernel-xen-2.6.20-1.3002.fc6 and xen-3.0.3-13.fc6 but not rebooted yet). My xen config file (created automatically by virt-install) is as follows: name = "skeggles" uuid = "a8912edd-ea7c-f324-f1bb-fdbc0c1a4b65" maxmem = 512 memory = 512 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" sdl = 0 vnc = 0 vncunused = 0 disk = [ "phy:/dev/vg_guests/lv_skeggles,xvda,w" ] vif = [ "mac=00:16:3e:4c:82:c7,bridge=xenbr0" ] Thanks, R.

1 0

recompile for using sdl and vnc
by nooroon 05 Dec '07

05 Dec '07

Hello, I'm using fedora 7 with xen 3.1 from binaries rpm. I try to use the sdl display, but when i configure my VM with *<graphics type='sdl'/> * no window pops up. Thanks to goolgle, I've found someone how got the same issue, and it seems that qemu-dm was not compile whith sdl support. What is the best way to recompile qemu-dm whith sdl support? In fact, I'd like to have sdl for local display of my VM, and vnc for remote access to it. What configuration should I use to do so? Thanks

4 5

Guest Image File Size
by Aaron Metzger 04 Dec '07

04 Dec '07

virt-install has a checkbox which suggests that you can avoid preallocating the entire guest image size -- that the guest image file will grow on demand. Does this work for Xen or is it only supported for KVM and the QEMU COW files? My experience when creating Xen guests as regular files is that I end up with a file that is the full size even when I pick the option to not preallocate the entire image. -- Thanks, Aaron

7 10

Xen : virsh error
by unixfoo 04 Dec '07

04 Dec '07

Greetings, When I try to use "virsh", I get the below error. ( xm list returns details though ). I use Fedora 8 and xen. [root@un1xf00 ~]# virsh virsh: error: failed to connect to the hypervisor [root@un1xf00 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 4885 4 r----- 399430.4 webhttp10000 11 2048 2 -b---- 65141.6 webhttp10001 18 2560 2 -b---- 358.0 webhttp10002 14 2048 2 -b---- 81720.5 [root@un1xf00 ~]# Any configuration to be done for virsh. Please help -unixfoo http://unixfoo.blogspot.com

5 9

Best practices questions
by Lopez, Denise 03 Dec '07

03 Dec '07

Hi all, I am in the process of building a new Xen server from scratch and wanted to ask a couple of questions about best practices. First, should the guest domains be image files or LVM's or just regular ext3 partitions? What are the pros and/or cons of each? Second, since the Dom0 is supposed to be kept secure, and most of my servers I don't install any X11 server on, is there any security risk installing an X11 server on the Dom0 in order to take advantage of the virt-manager GUI interface? Thank you in advance for any thoughts and or opinions. Denise Lopez UCLA - Center for Digital Humanities Network Services Linux Systems Engineer 337 Charles E. Young Drive East PPB 1020 Los Angeles, CA 90095-1499 310/206-8216

6 6

lv as "partition"?
by Maximilian Freisinger 01 Dec '07

01 Dec '07

Hello, im just trying to use a logical volume as a partition (for example sdc1) in my domU. As there seems to be no possibility to define such things on virt manager, i tried virsh with attach-disk and attach-device. But i always get: libvir: Xen Daemon Fehler: POST Operation schlug fehl. (Xend.err 'Device 2081 not connected') my xml for device: my definition for disk: virsh attach-disk /dev/master/part01 sdc1 my question is where is my error, or how can i achieve my aim? thx _________________________________________________________________ You keep typing, we keep giving. Download Messenger and join the i’m Initiative now. http://im.live.com/messenger/im/home/?source=TAGLM

1 0

Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging?
by Christian Lahti 01 Dec '07

01 Dec '07

Hi Dale: I work with David who posted the original question to the mailing list. I think we need to give a bit more background info on what we are trying to do. We are running a mixed environment of mostly CentOS 3, 4and 5, we do have a few windows servers and XP systems as well. We are looking to virtualize all these platforms. Normally we have a bonded pair of NICs for the physical hosts, we were able to get this running using CentOS 5 x86_64 with no problems, the guest machines use the bonded pair in bridged mode as expected after a bit of tweaking. The biggest issue we found with EL5 is that windows guest performace is dismal at best, hence our decision to have a look at Fedora Core 8 x86_64. I am happy to report that performance for all of our guest platforms is *very* good with FC8, but it seems that libvirt changed the way networking is setup for Xen. The default NAT configuration is pretty useless for production server environment. Thanks to the mailing list we are now able to bridge a single NIC on FC8 (like eth0 for example), but we cannot figure out how to get a bridge for bond0 (comprised of eth0 and eth1) defined and available to Xen. All the tweaks that worked find on EL5 have not worked so far on FC8. I am going to review your document tomorrow and give it a try, but any idea on whether your methodology will work on FC8 and libvirt? I am willing to blow a Sunday to get this worked out once and for all :) Basically we are after good performance on both para and fully virtualized guests using a bonded pair of GB NICs for speed and redundancy. If this can be achieved with enterprise linux then that would be preferable, but we will go FC8 if the bonding thing can be sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 and has pretty good performance but their free version is limited to 32bit (and hence 4GB ram). Adding the clustering failover is the next step of course :) Thanks again for the help so far. /Christian >>>>>>>>>>> just FYI for the list, I have a how-to for a bonded and VLAN tagged network. http://www.certifried.com ODT and PDF formats available. It might not be the best way, but I've sent it out to my colleagues several times and have never received any negative feedback. Mark Dale Bewley wrote: I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -- Fedora-xen mailing list Fedora-xen redhat com https://www.redhat.com/mailman/listinfo/fedora-xen **************************************************************************** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. ****************************************************************************

1 0

FYI: The plan for Xen kernels in Fedora 9
by Daniel P. Berrange 01 Dec '07

01 Dec '07

This is a friendly alert of the major plans we have for Xen kernels in Fedora 9 timeframe... Since we first added Xen in Fedora Core 5, our kernels have been based on a forward-port of XenSource's upstream Xen kernels, to new LKML. For a long time we ported their 2.6.16 tree to 2.6.18. Now we do ports of their 2.6.18 tree to 2.6.21/22/23, etc. At the same time, upstream Linux gained Xen support for i386 DomU, and shortly x86_64 DomU, and is generally getting ever more virtualization capabilities. As everyone knows, we have tended to lag behind Fedora's state-of-the-art bare metal kernels by several releases due to the effort required to port Xen to newer LKML releases. Despite our best efforts, this lag has been getting worse, not better. We have taken the decision, that this situation is unacceptable for Fedora 9. We simply cannot spend more time forward porting Xen kernels. Either Xen has to be dropped entirely, or we need a different strategy for dealing with the kernels. Since people seeem to use Xen, we have decided not to drop it :-) So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. LKML already has i386 pv_ops + Xen DomU. We intend to build on this to add: - x64_64 pv_ops - x86_64 Xen DomU on pv_ops - i386 & x86_64 Xen Dom0 on pv_ops - memory balloon - paravirt framebuffer - save/restore All of this based on same LKML release as Fedora bare metal. If all goes to plan it may even be in the base kernel RPM, instead of kernel-xen, but thats a minor concern compared to the actual coding. Getting all this done for Fedora 9 is seriously ambitious, but it is the only long term sustainable option, other than dropping Xen entirely. What this means though, is that Fedora 9 Xen will certainly be going through periods of instability and will certainly be even buggier than normal. F9 may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no PCI device passthrough, or CPU hotplug). On the plus side though we will be 100% back in sync with bare metal kernel versions & hopefully even have a lot of this stuff merged in LKML to make ongoing maintainence sustainable. Short term pain; Long term gain! I have not got any ETA on when any of these kernel changes will appear in rawhide - some time before the F9 feature freeze date is best guesstimate. We will alert people when the time comes. There is a F9 feature page with some amount of info about the plan... http://fedoraproject.org/wiki/Features/XenPvops In terms of Fedora 6/7/8 maintainence... The kernel-xen in these existing releases already lags behind the bare metal kernel version by 2-3 releases. We do not intend to continue trying to rebase the kernel-xen in existing Fedora releases. It will be essentially important bug-fix mode only. This is neccessary to enable maximum resources to be focused on the critical Fedora 9 Xen work. Regards, Dan ...on behalf of some very busy Fedora Xen kernel developers :-) -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

5 6

Fedora Core 8 + Xenbr0 + network bridging?
by David Levinger 30 Nov '07

30 Nov '07

Hello all, I was working with Xen and Cent OS and by default a virtual networking driver called Xenbr0 was created that acted as a "pass through" for the virtual machine. IE that machine contacted our real DHCP server and requested an IP address and all was well. However, on Fedora Core 8 it seems that the default networking setup is to use virbr0 and to have a totally different subnet and the host machine assigning IP addresses to the guests... How can I get back to just a pure network bridge that had the guests contact our DHCP server for leases? Thanks! David **************************************************************************** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. ****************************************************************************

4 7

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen December 2007