March 2008 - virt - lists.centos.org

Open VPN connection problem on Virtual Box
by Todd and Margo Chester 02 May '08

02 May '08

Hi All, I am working on a mystery. I am using openvpn-2.1_beta7-gui-1.0.3-install on all the computers in question. All computers are running XP-Pro-SP2. (Mine is running in a virtual window -- details below.) This configuration works perfectly from my office. I use it to call five facilities: remote aa.bb.cc.dd port 5030 proto udp dev tap ifconfig 192.168.240.30 255.255.255.0 secret iamnottellingyou.txt ping-restart 60 ping-timer-rem persist-tun persist-key resolv-retry 86400 ping 10 comp-lzo verb 6 mute 10 But, this EXACT config works on TWO other computers, but not mine: remote ww.xx.yy.zz 5020 client dev tap proto udp resolv-retry infinite nobind persist-key persist-tun ca foo-ca.crt cert foo-client1.crt key foo-client1.key ns-cert-type server ping 10 comp-lzo verb 3 The only difference between the two computers that MY config works on and mine, is that my computer is running in a virtual window. Host: Cent OS 5.1 Guest XP-Pro-SP2 VM: VirtualBox-1.5.6_28266_rhel5-1.i586.rpm The host and the guest are connected by a bridge (br0): DEVICE=br0 TYPE=Bridge BOOTPROTO=static BROADCAST=192.168.255.255 IPADDR=192.168.255.10 NETMASK=255.255.255.0 NETWORK=192.168.255.0 GATEWAY=192.168.255.10 ONBOOT=yes USERCTL=yes IPV6INIT=no PEERDNS=no PROMISC=yes When trying to connect, the same error message pops up on my computer (virtual XP) and on the distant end's (XP) server: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) The SAME error message! Why does the first config work, but not the second? It is obviously not the config: it is identical on the other two computers that it works on. I think it may be the way open vpn is reacting to my bridge, but then, again, the first config works. Editorial comment: AAAAAAAAAHHHHHHHHHHHHHHHHHHH!!!! Anyone know what I am doing wrong? Many thanks, -T

2 2

xenbr0 isn't created anymore
by Kai Schaetzl 02 Apr '08

02 Apr '08

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0) and then running /etc/xen/scripts/network-bridge start xend-config.sxp still has (network-script network-bridge), logging shows no problems. It seems that the network-bridge script simply doesn't run, but why? I can't see any init script or so that might run it, so I assume it's xend doing that, but there's no error in any log. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

3 30

Re: CentOS-virt Digest, Vol 7, Issue 22
by Hristo Benev 30 Mar '08

30 Mar '08

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt(a)centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E(a)MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed to disable the creation of xenbr0 on boot-up of the host >> system. CentOS 5 with standard CentOS Xen. >> I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled >> virtlibd. Works fine. But when I later restarted the machine I found that >> all networking for guests had gone. On inspection there's no xenbr0 >> created anymore. I can get it up by stopping network (or eth0) and then >> running /etc/xen/scripts/network-bridge start >> xend-config.sxp still has (network-script network-bridge), logging shows >> no problems. It seems that the network-bridge script simply doesn't run, >> but why? I can't see any init script or so that might run it, so I assume >> it's xend doing that, but there's no error in any log. > >Kai, > >Snooping around I found this in /etc/xen/qemu-ifup: > ># ># Old style bridge setup with netloop, used to have a bridge name ># of xenbrX, enslaving pethX and vif0.X, and then configuring ># eth0. ># ># New style bridge setup does not use netloop, so the bridge name ># is ethX and the physical device is enslaved pethX ># ># So if... ># ># - User asks for xenbrX ># - AND xenbrX doesn't exist ># - AND there is a ethX device which is a bridge ># ># ..then we translate xenbrX to ethX ># ># This lets old config files work without modification > >So it turns out Xen networking changed in current releases and they never >updated their Wiki. > >Now I am not sure how the vif0.X and vethX interfaces fit into the >picture here... Maybe these are no longer used? > >vifX.Y interfaces are still used though for linking domU interfaces >with the physical interface. > > >-Ross > >______________________________________________________________________ >This e-mail, and any attachments thereto, is intended only for use by >the addressee(s) named herein and may contain legally privileged >and/or confidential information. If you are not the intended recipient >of this e-mail, you are hereby notified that any dissemination, >distribution or copying of this e-mail, and any attachments thereto, >is strictly prohibited. If you have received this e-mail in error, >please immediately notify the sender and permanently delete the >original and any copy or printout thereof. > > >

3 2

Migration Problem
by Brett Worth 29 Mar '08

29 Mar '08

Hi all! I've been experimenting with Xen on CentOS 5 and RHAS 5 for a while now with mixed success I thought I'd describe my latest challenge. I'll describe this from memory since all the equipment is at work and not contactable from here. I think I've described this config to the list before but here it is again: I have 2 x HP DL585 servers each with 4 Dual core Opterons (non-vmx) and 16GB RAM configured as Xen servers. These run CentOS 5.1 with the latest updates applied. These system both attach to an iSCSI target which is an HP DL385 running ietd and serving SAN based storage. Everything runs fine if I do no migration. I was having a "soft lockup" problem which has been solved by installing the latest test kernel from redhat. They've adjusted a timer as described in this report (comment 5): https://bugzilla.redhat.com/show_bug.cgi?id=250994 Anyway things are pretty stable now but... If I do a series of migrations, live or not, from one server to the other eventually I will get the process to fail. This could take up to an hour with the migrations happening every 5 minutes. It can also happen first try. The message in the xend.log file says that it is unable to find the device number for the virtualised storage i.e. sda. In my configuration I have dom0 connecting to the LUNs used by the VMs to the domU's are not doing iSCSI. I'm passing the "/dev/disks/by-path/iscsixxx:sda1" info in via the xen config file. If I mount and unmount the same LUN's filesystem to the dom0 over and over again it works every time so there's no fundamental problem with the iSCSI connection itself. Each server is using 3 gige interfaces: One for normal LAN access, a dedicated network for the iSCSI and a crossover cable between the third gige interfaces on the servers for the migration channel. I have a xentop running on both dom0's and can tell that its failed when the vm appears in the target but the memory used by the vm doesn't start incrementing. The end result is that the VM is hung and has to be destroyed and re-created. The error happens immediately after the failed migration is initiated. I've tried doing a read of the first few blocks of the LUN on the target immediately before initiating the migration which is successful but makes no difference. I realize this is pretty sketchy information but I was wondering if others were seeing similar problems. The ability to do reliable migration is basically the prime motivation for us wanting to do virtualization at all. Otherwise we'd just run the required services on the main machine. Anyway, any help would be appreciated. Brett

1 0

i386 VM on x86_64 host in Xen
by Frans Lawaetz 24 Mar '08

24 Mar '08

>/ On Mon, 2007-12-10 at 22:34 +0000, Karanbir Singh wrote: />>/ Just wondering if people had started using i386 Xen DomU's on a x86_64 />>/ dom0 machine with 5.1 as yet ? And just wondering what their experiences />>/ have been. /I thought I would chime in here with my experience. I am running a Cent5.1 x86_64 Dom0 with a Cent 5.1 x386 domU (both fully updated). Everything works well including installation and subsequent "xm create" boots. A gotcha that I have not been able to work around has to do with the automatic save/restore with the xendomains script. When I mimic Dom0 shutdown behavior (i.e., xendomains stop) and run "xm save sdatest /var/lib/xen/save/sdatest" the following gets generated to xend.log [2008-03-24 18:33:29 xend.XendDomainInfo 19801] INFO (XendDomainInfo:1719) Dev 51728 still active, looping... [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:1611) XendDomainInfo.resumeDomain: devices released [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:988) XendDomainInfo.handleShutdownWatch [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:791) Storing domain details: {'console/ring-ref': '6706833', 'console/port': '2', 'name': 'migrating-sdatest', 'console/limit': '1048576', 'vm': '/vm/a9b4b850-95ee-1364-6b2b-5e79375ce47e', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '131072', 'store/ring-ref': '6706834', 'store/port': '1'} [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'virtual-device': '51712', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51712'} to /local/domain/1/device/vbd/51712. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'domain': 'migrating-sdatest', 'frontend': '/local/domain/1/device/vbd/51712', 'dev': 'xvda', 'state': '1', 'params': '/dev/VolGroup00/sdatest.boot', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/51712. [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvdb: [Errno 2] No such file or directory: '/dev/xvdb' [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'virtual-device': '51728', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51728'} to /local/domain/1/device/vbd/51728. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'domain': 'migrating-sdatest', 'frontend': '/local/domain/1/device/vbd/51728', 'dev': 'xvdb', 'state': '1', 'params': '/dev/VolGroup00/sdatest', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'phy'} to /local/domain/0/backend/vbd/1/51728. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:110) DevController: writing {'mac': '00:16:3e:00:00:11', 'handle': '0', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2008-03-24 18:33:29 xend 19801] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'migrating-sdatest', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:00:00:11', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. [2008-03-24 18:33:29 xend.XendDomainInfo 19801] DEBUG (XendDomainInfo:1623) XendDomainInfo.resumeDomain: devices created [2008-03-24 18:33:29 xend.XendDomainInfo 19801] ERROR (XendDomainInfo:1628) XendDomainInfo.resume: xc.domain_resume failed on domain 1. Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1625, in resumeDomain xc.domain_resume(self.domid, fast) Error: (1, 'Internal error', "Couldn't map p2m_frame_list_list") [2008-03-24 18:33:29 xend 19801] DEBUG (XendCheckpoint:136) XendCheckpoint.save: resumeDomain ERROR Internal error: Couldn't map p2m_frame_list_list There are two errors of note -- [2008-03-24 18:33:29 xend 19801] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' and ERROR Internal error: Couldn't map p2m_frame_list_list Someone with greater knowledge of Xen's internal workings might comment as to whether they're related errors. It looks like this is a known issue with Xen based on the following bug report (which, alas, is not showing any activity). http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1064 I suppose a temporary workaround (for a development environment) is to alter the xendomains script so that a save is not conducted but a shutdown followed by a destroy. Cheers, Frans

1 0

Re: [CentOS-virt] DHCP for Xen VMs
by Ross S. W. Walker 24 Mar '08

24 Mar '08

You might want to check iptables in the dom0. I believe iptables gets set on eth0 before it 'pivots' to peth0 and I doubt it flushes it and retargets it to the new bridged eth0 afterwards, so the dhcp traffic may appear as unsolicited and dropped on dom0 as it enters the bridge. If that turns out to be the case you will need to have iptables stopped right before the creation of peth0 and restarted afterwards (and maybe file a bug report too). -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: centos-virt(a)centos.org <centos-virt(a)centos.org> Sent: Mon Mar 24 09:41:42 2008 Subject: Re: [CentOS-virt] DHCP for Xen VMs Ross S. W. Walker wrote on Sun, 23 Mar 2008 19:29:47 -0400: > Assuming you have a DHCP server on the local net, maybe ip tables in the dom0 is blocking the dhcp traffic? > > Did you configure xend to do bridged or nat'd? Default is bridged. Well, networking *does* work if I set an IP address manually and as I can reach it then from other machines it must be bridged. The problem is that I don't get an IP address when using dhcp :-( I wasn't aware that iptables is on and preconfigured in a domU that got setup with CentOS 5.1 virt-manager. Unfortunately, shutting it off doesn't solve the problem. Logging shows that the server gets a request from that MAC address and offers an IP address, but the client doesn't receive it. There's no firewall between the two, but the offer doesn't get back to the client somehow. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

Re: [CentOS-virt] DHCP for Xen VMs
by Ross S. W. Walker 24 Mar '08

24 Mar '08

Assuming you have a DHCP server on the local net, maybe ip tables in the dom0 is blocking the dhcp traffic? Did you configure xend to do bridged or nat'd? Default is bridged. -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: centos-virt(a)centos.org <centos-virt(a)centos.org> Sent: Sun Mar 23 18:31:15 2008 Subject: Re: [CentOS-virt] DHCP for Xen VMs Ross S. W. Walker wrote on Thu, 20 Mar 2008 11:59:17 -0400: > Configure the Xen VM to use the xen managed network xenbr0 instead of the > libvirt managed network virbr0. Unfortunately, doesn't work for me. If I change to xenbr0 the VM doesn't get an IP address. And as I'm having problems with the keymap I can't even look at the logs at the moment. If I set an IP address in the same subnet manually it works, but dhclient doesn't set one. Any ideas? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

console keymapping problems
by Kai Schaetzl 24 Mar '08

24 Mar '08

Supposedly CentOS 5.1 should fix the problems with foreign keyboards, but I cannot see any change. The description in http://misterd77.blogspot.com/2007/11/xen-graphical-console-and-foreign.html does not work for me. Nothing changes. Has had anyone better luck? If so, how? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

xenbr0 vs. virtbr0
by Kai Schaetzl 23 Mar '08

23 Mar '08

Just created the first completely new Xen VM with the Virtual Machine Manager after 5.0 became 5.1 and I notice these two differences: - there's now virbr0 instead of xenbr0. Which means I have now xenbr0 and vitbr0 interfaces running. As virbr0 just the new name for xenbr0? If so, can I just change that name in the older configuration files, so that all use the same interface name? - there is a (I think) new option for networking. There's virtual network and there's shared device. What's the latter? I don't remember this being available earlier. It doesn't list any devices for me. Does this refer to virtual devices of type eth0:5 etc. on the host? help is no help for this, it's empty for this section. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

DHCP for Xen VMs
by Kai Schaetzl 23 Mar '08

23 Mar '08

I created my first Xen VM that didn't use a static IP address. It grabs an IP from the 198.168.122.0 subnet (from I don't know where). I would rather want it to use my DHCP server. How can I achieve this? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

Re: [CentOS] Running CentOS 4.6 domUs on CentOS 5.1 dom0 and domUs crash
by Tim Verhoeven 21 Mar '08

21 Mar '08

On Mon, Mar 17, 2008 at 8:05 PM, Nathan Grennan <centos(a)cygnusx-1.org> wrote: > I have a CentOS 5.1 dom0 running on a machine with two cores and 4gb > of memory. It runs three 4.6 domUs and one 5.1 domU. Just out of the > blue the other night all the 4.6 domUs crashed, but the dom0 stayed up. > I ran xm console (domU-name) and got the Oops information below. I > didn't get anything from the 5.1 domU. I think it had been rebooted a > few days before and hadn't come up because of a initrd issue. > > First 4.6 domU: > > kernel BUG at arch/i386/mm/pgtable-xen.c:306! ...snip... Hi, I'm moving this thread to the CentOS-virt mailinglist (please remove the centos mailinglist to everyone replying to this mail) since it is more suited for these kind of questions. Question, If I read those crashes correctly your 4.6 domU is a 32 bit one ? What platform is your dom0 32 or 64 bit? Running a 32 bit domU on a 64 bit dom0 is currently not really stable. This is suppose to improve with 5.2 Regards, Tim -- Tim Verhoeven - tim.verhoeven.be(a)gmail.com - 0479 / 88 11 83 Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. (Linus Torvalds)

8 9

Xen Windows Clients - BSOD with Application Firewall Installs
by centos-virt＠mymail.isbest.biz 21 Mar '08

21 Mar '08

I have set up both Windows XP and Windows 2000 Server clients on Xen under Centos 5.1 and am unable to install an application firewall. I have tried the latest: 1) Agnitum Outpost Commercial Version 2) Comodo Firewall (ver 2 on Windows 2000) 3) Sunbelt Commercial Version With all of these when the firewall starts up it results in a BSOD. With Windows XP and Agnitum I can go back to a previous system restore point, with Windows 2000 and other firewalls on XP the only option is a backup of the Xen client as even a save mode command prompt startup results in a BSOD. I have tried on the Windows XP install using various HALS and switches for PAE ACPI and multi/single cpu support and have not had any success. Windows 2000 BSOD results from "an attempt was made to write to read only memory" NDIS.SYS Windows XP BSOD message is related to: Agnitum - sandbox.sys Others: "an attempt was made to write to read only memory" NDIS.SYS Has anyone any idea of how to set up Xen Windows clients to allow an application firewall to be installed successfully? Thanks Jesse

1 0

virt-install in CentOS 5
by Kanwar Ranbir Sandhu 21 Mar '08

21 Mar '08

Hi All, [I originally posted this message in the main CentOS users' list, but later found this list. So, I'm reposting it here since this is where it belongs.] I'm trying to install a Fedora 8 domU on a CentOS 5 dom0, but the following command fails: [root@xenmaster ~]# virt-install -p -n krs -r 512 -m 00:16:3E:66:94:5F -b xenbr0 --vnc --vncport=5910 -l http://10.19.75.200/mirror/fedora/linux/releases/8 -f /dev/vg00/krs -d Starting install... Sat, 08 Mar 2008 12:27:56 DEBUG Fetching URI http://10.19.75.200/mirror/fedora/linux/releases/8//Fedora Sat, 08 Mar 2008 12:27:56 DEBUG Saved file to /var/lib/xen/virtinst-Fedora.VhrSOC Retrieving Fedora... 100% |=========================| 965 B 00:00 Sat, 08 Mar 2008 12:27:56 DEBUG Detected a Fedora distro Sat, 08 Mar 2008 12:27:56 DEBUG Fetching URI http://10.19.75.200/mirror/fedora/linux/releases/8/images/xen/vmlinuz ERROR: Invalid URL location given: [Errno 14] HTTP Error 404: Not Found I have no idea why virt-install is looking for the xen kernel in http://10.19.75.200/mirror/fedora/linux/releases/8/images/xen/vmlinuz : it's actually here: http://10.19.75.200/mirror/fedora/linux/releases/8/Fedora/i386/os/images/xe… I've used the above syntax to install CentOS 5 domUs on the same host without any problems. What gives? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.22.14-72.fc6 i686 GNU/Linux 20:51:42 up 4 days, 9:58, 2 users, load average: 1.23, 0.63, 0.48

6 15

Re: [CentOS-virt] RE: [CentOS] Running CentOS 4.6 domUs on CentOS5.1 dom0 and domUscrash
by Ross S. W. Walker 20 Mar '08

20 Mar '08

Sorry for the top post, blackberry. Well I like to be able to install my machines in the xenstore with 'xm new' and then manage them from there, but virt-install and virsh are useful too, so I just use CentOS base then replace their xen with the one from xen.org keeping libvirt and now I have the best of both worlds. The commercial one isn't without gripes too. Like I wish they had developed a fully web based interface for creating and managing virtual machines like the one Microsoft has in their virtual server instead of the standalone java client. I never really like standalone java clients as it makes it one more thing you have to reach for when you need to get something done, when there is almost always a web browser available. -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: Discussion about the virtualization on CentOS <centos-virt(a)centos.org> Sent: Thu Mar 20 17:34:08 2008 Subject: Re: [CentOS-virt] RE: [CentOS] Running CentOS 4.6 domUs on CentOS5.1 dom0 and domUscrash Ross S. W. Walker wrote: > glues the Xen 3.0.3 user land tools onto a highly patched 3.1 > hypervisor forcing the user to try and use their swiss army > knife libvirt to manage the mess. Ugh! I just want Xen and > to manage it through Xen! I quite like the virsh and virt-install stuff included in the distro, I think xen tools themselves are quite pedestrian at the moment. Perhaps their commercial offerings are better - for me, the libvirt and virsh make Xen a lot more usable -- Karanbir Singh : http://www.karan.org/ : 2522219@icq _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

Clock fast - work around
by chanms 19 Mar '08

19 Mar '08

Well, to the clock being fast work around, I kind of found a way to work around it for now... 1) use a distribution that supports VMI (VMware's paravirtualization) 2) enable VMI paravirtualization support in VMware Workstation 6 VM's profile 3) use vmi-timer as the clocksource (as opposed to pit, acpi_pm, etc.) 4) CPU must be constantly at maximum frequency For 1), I use Ubuntu 7.10 For 2), the VM must be VMWare 6 profile type, then in Settings -> Options -> Advanced, check on "Enable VMware paravirtual kernel support"). I was unable to use VMI before because my entire Vista (x64 Ultimate) machine will BSOD when Ubuntu was booted with VMI turned on; only in the recent Workstation 6.0.3 patch that this bug has been fixed. For 3), Ubuntu default to vmi-timer if 1) and 2) are working properly; can be verified by /sys/devices/system/clocksource/clocksource0/available_clocksource and current_clocksource For 4), I didn't want to constantly lock the CPU of my laptop at highest speed at any time, as I don't need the CPU at full blast when I'm browsing website, or using MSOffice. So what I've done is by using distributed.net - this program uses idle CPU power to do calculations. This program keeps my CPU busy at all times but easily switched out when other programs need the CPU. With this, the Ubuntu's VM clock runs at a fairly accurate rate. The side effect is my CPU is constantly busy and the laptop cooling fan kept going and going (and no more putting my PC on my lap as it will be fairly hot). I also have a desktop with AMD Athlon X2 running Windows 2003 Server; with the above configuration (minus #4, as W2K3 Server keeps CPU clock rate constant) the Ubuntu VM's clock also was within 5 seconds compared to the host PC's clock over the period of a day. I hope that VMware will be able to devise a better way to keep VM clocks accurate in the future in their products.

1 0

help getting open-vm-tools installed
by Fletch Bowling 18 Mar '08

18 Mar '08

Hello, Newbie to CentOS and attempting to run it under a windows xp host. I see there is a open version of vmware tools available but getting various dependency errors when attempting to install. the rpms. Will these tools install for ver CentOS 5 or are they for an earlier version? P.S. How closely does CentOS match Redhat binaries? VMware tools (from workstation 6) install just fine but could not be configured due to various errors. Thanks, Fletch

2 7

Follow-up on Fast clock under VMWare
by chanms 15 Mar '08

15 Mar '08

Hi everyone: Just a follow up on the fast clock issue: "Can you double-check that 'cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq' outputs the same number as your 'cpuKHZ' setting in your config.ini file?" There is no cpufreq directory under /sys/devices/system/cpu/cpu0; all I see is "cache" (dir), "crash_notes" (a file) and "topology" (dir). However under /sys/devices/system/clocksource/clocksource0, available_clocksource reads acpi_pm jiffies tsc pit, current_clocksource reads pit. (I put in the line clocksource=pit) in the grub boot up line. Divider=10 in the bootup line causes the boot up process to hang and a reset has to be performed; removing it and the CentOS boots properly. I'm currently using 2.6.18-53.1.13.el5, with boot up options are "noapic nolapic quiet clocksource=pit" (took out divider=10). CentOS clock is going at around 2 seconds per every real second.

3 2

Fwd: 2 problems running CentOS 5.1 + kernel-vm in VMware Fusion
by Leonardo Vilela Pinheiro 07 Mar '08

07 Mar '08

Hi, Inside VMware Fusion 1.1.1, I have a virtual machine running CentOS 5.1 x86_64 with: - kernel-vm-2.6.18-53.1.13.el5.x86_64.rpm from http://people.centos.org/~tru/kernel-vm/5/RPMS/x86_64/ - kmod-open-vm-tools-0-0.20080123.2.6.18_53.1.13.el5vm.x86_64.rpm from http://people.centos.org/~hughesjr/open-vm-tools/5/x86_64/ First problem: Sometimes (most times) I get this error during boot (first error): "The VMware Tools poweron script did not run successfully in this virtual machine - If you have configured a custom poweron script in this virtual machine, please inspect it for errors; otherwise, please submit a support request." A screenshot of this error can be seen in: http://www.scribd.com/doc/2228546/VMware-Fusion-error-running-CentOS-51-ker… This problem is very strange, it doesn't happen on every boot, and usually when I boot another kernel (like change kernel-vm to "kernel-default" or back) it disappears and only appears again after some reboots using the kernel-vm. I don't know a safe path to reproduce this bug, and I also don't know for sure if it only happens with kernel-vm. Second problem: When I try to suspend the virtual machine (clicking on "Suspend Guest"), I get the error that can be seen in: http://www.scribd.com/doc/2232883/VMware-Fusion-running-CentOS-51-kernelvm-… When I try to suspend again, it gives no error and suspends, but when it resumes it gives the error that can be seen in: http://www.scribd.com/doc/2233720/CentOS-51-in-VMware-Fusion-resuming-from-… The second problem also happens when using: - kernel-2.6.18-53.1.14.el5 (default kernel) - kmod-open-vm-tools-0-0.20080123.2.6.18_53.1.13.el5vm.x86_64.rpm The second problem does *not* happen when using: - kernel-2.6.18-53.1.14.el5 (default kernel) or kernel-vm-2.6.18-53.1.13.el5.x86_64.rpm - default vmware-tools (which comes with VMware Fusion 1.1.1). So it might be a problem in kmod-open-vm-tools. If I may help debugging something, please tell me what to show you. -- Leonardo

1 1

Multi domU Xen Box Network Transparent Sound
by Ross S. W. Walker 07 Mar '08

07 Mar '08

I have a new development box at home that I am working on. Currently it has CentOS 5.1 + Xen 3.2 running several domUs. I am using XDMCP on the domUs and an X Chooser on dom0 for connecting to them and it works well, but now I want to be able to get sound from my domUs and I have been struggling. I can get some from network transparent sound by using ESD, but I have no way of controlling the mixer (volume) settings from within the domU which kind of sucks. I have been looking at the possibility of setting up a PulseAudio server in dom0 and installing the ALSA PulseAudio plugin on each domU set to use the dom0 server as from the web site it seems to be able to have remote mixer controls and can be handled as if it were a regular ALSA sound card, which should allow a majority of the apps to work as if there were a local sound card. My questions are: 1) Has anybody on the list used PulseAudio in this type of setup (not necessary Xen interface, but ALSA plugin to remote PulseAudio server)? 2) Does anybody on the list know a compatible repo that carries pre-compiled PulseAudio packages? Thanks in advance, Ross S. W. Walker Information Systems Manager Medallion Financial, Corp. 437 Madison Avenue 38th Floor New York, NY 10022 Tel: (212) 328-2165 Fax: (212) 328-2125 WWW: http://www.medallion.com <http://www.medallion.com/> ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

Question on best way of configuring this
by Stephen Harris 03 Mar '08

03 Mar '08

I have a Windows XP machine that I don't use very often, but I leave it powered up because once in a blue moon I need to remotely access it (eg from work), and to keep the Antivirus software up to date. When I do use it at the console I'm mostly doing basic video editting or transcoding (eg from transferred TiVo content). I sometimes play older games on it (eg Carmaggedon or Worms 2; I'm not into Warcrack, or City Of Heros or anything that needs a super-duper gaming card). I also have an aging Linux machine. This is my main workstation, although I primarily access it as a server (ssh into it, screen). I do occaisionally use the console as an X display, eg when scanning stuff or previewing my nroff documents before sending them to the printer. This machine has all my email, runs leafnode etc etc. What I'd like to do is run them both as virtual instances on a new machine (quad core duo) I've ordered. What I would really like to have is something like the dom0 being on tty0, map the Linux domU consoles to tty1->5, allow the Linux domU X server to run fullscreen on tty6, and have the windows GUI appear fullscreen on tty7. I really don't want to remotely access the windows GUI (it makes video editting harder, and game playing almost impossible), and would want to avoid displaying it inside another X session. Ideally it'd feel like a "real" machine. Does this sound like a feasible option? -- rgds Stephen

2 1

RE: [CentOS] error creating CentOS 5.1 x32 domU instance on CentOS 5.1 x64
by Ross S. W. Walker 03 Mar '08

03 Mar '08

Rudi Ahlers wrote: > Ross S. W. Walker wrote: > > Rudi Ahlers wrote: > > > Ross S. W. Walker wrote: <snip discussion on centos-virt subscribing> > > > > > > > > Did you verify that selinux is indeed disabled by looking in > > > > /etc/selinux/config that the line SELINUX=disabled is in there? > > > Yep: > > > > > > # This file controls the state of SELinux on the system. > > > # SELINUX= can take one of these three values: > > > # enforcing - SELinux security policy is enforced. > > > # permissive - SELinux prints warnings instead of enforcing. > > > # disabled - SELinux is fully disabled. > > > SELINUX=disabled > > > # SELINUXTYPE= type of policy in use. Possible values are: > > > # targeted - Only targeted network daemons are protected. > > > # strict - Full SELinux protection. > > > SELINUXTYPE=targeted > > > > > > > Good, just some users use setenforce 0 and think that's it done > > and then reboot and wonder why things are still not working > > properly. > > > > > > What was the actual contents of your domU's config file? > > > > > > > > > > > > > > > This is what I changed: > > > > > > # Dom0 will balloon out when needed to free memory for domU. > > > # dom0-min-mem is the lowest memory level (in MB) dom0 will > > > get down to. > > > # If dom0-min-mem=0, dom0 will never balloon out. > > > (dom0-min-mem 512) > > > > > > It was: > > > (dom0-min-mem 256) > > > > > > > Misunderstanding, I was hoping to see the config file of the > > domU you were trying to create. > > > You meant this? > > [root@gimbli ~]# more /etc/xen/vm03 > name = "vm03" > uuid = "cc3b0b01-7894-4ac2-06e6-a1a1307939fc" > maxmem = 512 > memory = 512 > vcpus = 1 > bootloader = "/usr/bin/pygrub" > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > vfb = [ ] > disk = [ "tap:aio:/home/vm/vm03.img,xvda,w" ] > vif = [ "mac=00:16:3e:0a:13:9d,bridge=xenbr0" ] Yes, it's a little lighter then I am use to, but it appears functional. I typically use an example config from /etc/xen and then change the appropriate parts for my VM and if necessary make sure the defines are up to date. Here's a Xen 3.2 PV config: ----- # Kernel image file. kernel = "/boot/vmlinuz-2.6.10-xenU" # Optional ramdisk. #ramdisk = "/boot/initrd.gz" # The domain build function. Default is 'linux'. #builder='linux' # Initial memory allocation (in megabytes) for the new domain. memory = 64 # A name for your domain. All domains must have different names. name = "ExampleDomain" # 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" # 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 # Number of Virtual CPUS to use, default is 1 #vcpus = 1 # By default, no network interfaces are configured. You may have one created # with sensible defaults using an empty vif clause: # # vif = [ '' ] # # or optionally override backend, bridge, ip, mac, script, type, or vifname: # # vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ] # # or more than one interface may be configured: # # vif = [ '', 'bridge=xenbr1' ] vif = [ '' ] # 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:hda1,hda1,w' ] # Define frame buffer device. # # By default, no frame buffer device is configured. # # To create one using the SDL backend and sensible defaults: # # vfb = [ 'type=sdl' ] # # This uses environment variables XAUTHORITY and DISPLAY. You # can override that: # # vfb = [ 'type=sdl,xauthority=/home/bozo/.Xauthority,display=:1' ] # # To create one using the VNC backend and sensible defaults: # # vfb = [ 'type=vnc' ] # # The backend listens on 127.0.0.1 port 5900+N by default, where N is # the domain ID. You can override both address and N: # # vfb = [ 'type=vnc,vnclisten=127.0.0.1,vncdisplay=1' ] # # Or you can bind the first unused port above 5900: # # vfb = [ 'type=vnc,vnclisten=0.0.0.0,vnunused=1' ] # # You can override the password: # # vfb = [ 'type=vnc,vncpasswd=MYPASSWD' ] # # Empty password disables authentication. Defaults to the vncpasswd # configured in xend-config.sxp. # Define to which TPM instance the user domain should communicate. # The vtpm entry is of the form 'instance=INSTANCE,backend=DOM' # where INSTANCE indicates the instance number of the TPM the VM # should be talking to and DOM provides the domain where the backend # is located. # Note that no two virtual machines should try to connect to the same # TPM instance. The handling of all TPM instances does require # some management effort in so far that VM configration files (and thus # a VM) should be associated with a TPM instance throughout the lifetime # of the VM / VM configuration file. The instance number must be # greater or equal to 1. #vtpm = [ 'instance=1,backend=0' ] # Set the kernel command line for the new domain. # You only need to define the IP parameters and hostname if the domain's # IP config doesn't, e.g. in ifcfg-eth0 or via DHCP. # You can use 'extra' to set the runlevel and custom environment # variables used by custom rc scripts (e.g. VMID=, usr= ). # Set if you want dhcp to allocate the IP address. #dhcp="dhcp" # Set netmask. #netmask= # Set default gateway. #gateway= # Set the hostname. #hostname= "vm%d" % vmid # Set root device. root = "/dev/hda1 ro" # Root device for nfs. #root = "/dev/nfs" # The nfs server. #nfs_server = '169.254.1.0' # Root directory on the nfs server. #nfs_root = '/full/path/to/root/directory' # Sets runlevel 4. extra = "4" #on_poweroff = 'destroy' #on_reboot = 'restart' #on_crash = 'restart' ----- So there are lots of options you can configure that aren't available through virt-install. You don't need to use virt-install either, that is a separate Xen management framework (actually general VM management framework for Xen and KVM). You could just do: # xm create <config file> On Xen 3.2, I add the VM directly into the xenstore with: # xm new <config file> Then the VM appears on xm list, and can be started stopped paused and is always able to query through the Xen API from third party management tools. # xm start <vm name> # xm pause <vm name> # xm resume <vm name> # xm shutdown <vm name> > > > > Also is this a workstation with Xen domU's for testing/development > > > > or a full blown Xen server for running production VMs? > > > > > > > This will be a full blown Xen server for production purposes. It will > > > run max 8 Xen guests with cPanel on each one. > > > > In that case if you don't want to shell out the $ for Xen Enterprise > > I would do these steps for setting up a Xen server: > > > > - for each server, minimal install, no X to reduce any possible dom0 > > issues, and to allow you to minimize dom0 memory usage, you can then > > run in 256MB with no X windows! > > > > - use the Xen 3.2 packages off of xen.org, compiled 64-bit, compile on > > separate 64-bit platform as the compilation will pull in a lot of other > > development packages and X. These packages use the Xen kernel from > > CentOS for the kernel image, and that package comes with the 3.1 Xen > > image so you'll need to edit the grub.conf to make sure the Xen 3.2 > > image is used instead of the 3.1 image every time you upgrade the kernel. > > These packages provide the latest features and fixes as well as the more > > capable management tools and API which will become a necessity when you > > manage from the command line and/or have more then 1 server which > > eventually you will for scalability, redundancy, etc. > > > > - Start seriously thinking about implementing an iSCSI SAN, your > > storage requirements will balloon crazy until your virtualization > > environment stabilizes, and SANs allows for better storage > > utilization, scalability and also allows for VM migration from one host > > to another and are a bitch to migrate to after the fact. > > > > - Build your Xen config files by hand, it's the only way to assure > > they are setup properly and the way you want. > > > > Since a Xen environment will be sensitive to change, maybe not as > > much as a LAMP environment, but still probably second to, you may > > want to manage your Xen build yourself, at least for the servers, > > as Redhat's Xen implementation is still evolving. > > > > I would use Redhat's Xen environments once they have a pure Xen 3.2 > > build, as their current Frankenstein environment is really aimed > > at workstation deployments, especially their hoaky X tool. > > > > Ross, you're talking about "scary" new stuff which I haven't even though > about. True, once it's done once it isn't as scary as it first seems though. > - What I'd like to accomplish, is to have a few dedicated servers (Our > company is the hosting company, and this is the first time we go into > virtualization ), each running up to say 10 VPS / VM's (which is much > cheaper than a full blown dedi to the client) > None of the servers have X (no point to it), and we use a very, very > minimal install (I don't even have FTP running, since cPanel will > provide this). The VPS's will either have 256MB (cPanel minimum) / 512 / > 786 / 1GB RAM - Obviously if more RAM is desired per VPS, less will be > run on 1 server, or the server will have more RAM & CPU's HDD space will > also either be 10 / 20 / 40 / 60 GB per VPS. The VPS' itself will only > run cPanel, no X - a server doesn't need X for anything. So, 10 VPS with > 512MB each = 12GB needed on host server. Many Xeon mobo's can take upto > 32GB RAM. Yes there is no problem there, and if you have multiple Xen servers using shared backend storage you can migrate VMs between the Xen servers on a resource needed basis. > - I'm a bit sceptic about using Xen 3.2 off the Xen site, as I don't > know how well it'll perform on CentOS and I believe that if CentOS > hasn't included in their repositories yet, then there must be a good > reason. I'll test it on a test server though to see what happens. I > think the other problem I have, is that these servers are deployed from > the standard CentOS 5.1 CD & a kickstart file with only the necessary > software & nothing more. Having to compile software on another machine > isn't fun for me. Well here's a clue. Xen Enterprise server uses CentOS as the OS for dom0. I believe they still use CentOS 4.X (maybe the latest uses 5.X) and the Xen 3.2 package was built on CentOS. Xen 3.2 performs very very well on CentOS 5.X (some say even better then the Xen shipping with CentOS). At my site I have setup a site specific repository for all in-house compiled RPMs and I have my kickstarts add the repo with a higher priority then the base/updates/extras repos for CentOS. Then I run a 'yum update' and my Xen 3.2 packages replace the CentOS ones on install and are there after updated from my internal repo. > - I just want to understand this better. If I run a 64bit host, and want > to install any other guest (preferably 32bit), then I need to use the > "fully virtualized guest" and not the para-virtualized option, right? No, with Xen 3.1 and 3.2 a 64-bit Xen host can run: 32-bit PVM 32-bit PAE PVM 32-bit HVM 64-bit PVM 64-bit HVM There have been reports that the CentOS version has problems with 32-bit PVM guests on 64-bit hosts. I don't know if they have all been resolved, but this should fully work on Xen 3.2. > - I like where you're heading with the suggestion of an iSCSI SAN, but > that's totally new to me as well, and not in my budget right now. Maybe > later on when this whole project takes off as I hope for it to take off. > But, since you mention it, do you then setup the server with a base OS, > and mount the iSCSI SAN as added storage? And then all the VM's get's > stored on the SAN, instead of the server's HDD's? And how well will such > a setup perform if I have say 5 / 10 servers connected to it? I guess > the SAN will then at least need 4 Gigabit NIC's, as the hubs in the DC > are only 100Mbit hubs. For a startup SAN, what would you suggest? I > guess a PC / server based SAN (in other words, I take a Xeon mobo with > plenty of HDD ports and put plenty HDD's on it) isn't really > an option? Yes, the VM's disks are located on the SAN and either mounted on the Xen host and booted off them, or the Xen VM's do an iSCSI boot directly off the SAN. There are a myriad of ways of doing this and it will depend on the VMs and Xen desired configuration. I run approximately 16 virtual guests off a single iSCSI server and the performance is very good. Of course I have the disk array setup as a RAID-10 for the VM's as 90% of all disk access will be random across the OS disks. I have a separate iSCSI server that provides the application data storage with different array types based on the storage. Currently we have used the iSCSI Enterprise Target software from sourceforge to provide cheap iSCSI and we are graduating to an appliance based solution soon. The appliance costs from Dell have dropped to a thin margin over the costs of the raw disks, so there isn't much cost factor any more. Talking around 20K for 15 146GB 15K SAS disks iSCSI array where once it was around 80-90K. Of course with the iSCSI Enterprise Target you can start simple with SATA and a cheap array. Then gradually evolve it to more and more complex/expensive setups as the need grows. > For now I'm going to manage the Xen stuff myself, I don't have anyone > capable of doing this kind of work yet. Plan it out carefully, ask advice on this list and the Xen list and you should be able to put together an effective setup very economically. -Ross ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 2

error installing Xen guests on CentOS 5.1 x64 - could not read tty from store
by Rudi Ahlers 02 Mar '08

02 Mar '08

Hi all I keep on getting this error when I try and install a Xen guest on a CentOS 5.1 x64 server with Xen installed from the repositories: [root@gimbli ~]# virt-install sdl=0 vnc=0 nographic=0 -v --location=http://intranet/kickstart/cPanel/centos/5.1/32/os/i386/ --ram=256 --file-size=10 --file=/home/vm/vps07.img --name=vps07 libvir: error : configuration file syntax error: expecting an assignment Would you like to enable graphics support? (yes or no) no Starting install... Retrieving CentOS... 91 kB 00:00 Retrieving boot.iso... 100% |=========================| 7.3 MB 00:00 Creating storage file... 100% |=========================| 10 GB 00:00 Creating domain... 0 B 00:00 Domain installation still in progress. You can reconnect to the console to complete the installation process. [root@gimbli ~]# xm console vps07 xenconsole: Could not read tty from store: No such file or directory [root@gimbli ~]# xm dmesg __ __ _____ _ ___ ____ _____ _ _ _____ _ ____ \ \/ /___ _ __ |___ / / | / _ \ | ___|___ / / | / |___ / ___| | ___| \ // _ \ \047_ \ |_ \ | || | | |_|___ \ |_ \ | | | | |_ \ / _ \ |___ \ / \ __/ | | | ___) || || |_| |__|__) |__) || |_| |___) | __/ |___) | /_/\_\___|_| |_| |____(_)_(_)___/ |____/____(_)_(_)_|____(_)___|_|____/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.1.0-53.1.13.el5 (mockbuild@) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) Tue Feb 12 12:55:35 EST 2008 Latest ChangeSet: unavailable (XEN) Command line: /xen.gz-2.6.18-53.1.13.el5 (XEN) 0000000000000000 - 000000000009f000 (usable) (XEN) 000000000009f800 - 00000000000a0000 (reserved) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000007f5e0000 (usable) (XEN) 000000007f5e0000 - 000000007f5e3000 (ACPI NVS) (XEN) 000000007f5e3000 - 000000007f5f0000 (ACPI data) (XEN) 000000007f5f0000 - 000000007f600000 (reserved) (XEN) 00000000d0000000 - 00000000e0000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) System RAM: 2037MB (2086396kB) (XEN) Xen heap: 13MB (14212kB) (XEN) Domain heap initialised: DMA width 32 bits (XEN) Processor #0 6:15 APIC version 20 (XEN) Processor #1 6:15 APIC version 20 (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2666.753 MHz processor. (XEN) HVM: VMX enabled (XEN) VMX: MSR intercept bitmap enabled (XEN) CPU0: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping 0b (XEN) Mapping cpu 0 to node 255 (XEN) Booting processor 1/1 eip 90000 (XEN) Mapping cpu 1 to node 255 (XEN) CPU1: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz stepping 0b (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) mtrr: your CPUs had inconsistent variable MTRR settings (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0xffffffff80200000 memsz=0x2c3c58 (XEN) elf_parse_binary: phdr: paddr=0xffffffff804c3c80 memsz=0x113270 (XEN) elf_parse_binary: phdr: paddr=0xffffffff805d7000 memsz=0xc08 (XEN) elf_parse_binary: phdr: paddr=0xffffffff805d8000 memsz=0x10af04 (XEN) elf_parse_binary: memory: 0xffffffff80200000 -> 0xffffffff806e2f04 (XEN) elf_xen_parse_note: GUEST_OS = "linux" (XEN) elf_xen_parse_note: GUEST_VERSION = "2.6" (XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0" (XEN) elf_xen_parse_note: VIRT_BASE = 0xffffffff80000000 (XEN) elf_xen_parse_note: PADDR_OFFSET = 0xffffffff80000000 (XEN) elf_xen_parse_note: ENTRY = 0xffffffff80200000 (XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xffffffff80206000 (XEN) elf_xen_parse_note: FEATURES = "writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel" (XEN) elf_xen_parse_note: LOADER = "generic" (XEN) elf_xen_addr_calc_check: addresses: (XEN) virt_base = 0xffffffff80000000 (XEN) elf_paddr_offset = 0xffffffff80000000 (XEN) virt_offset = 0x0 (XEN) virt_kstart = 0xffffffff80200000 (XEN) virt_kend = 0xffffffff806e2f04 (XEN) virt_entry = 0xffffffff80200000 (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0xffffffff80200000 -> 0xffffffff806e2f04 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 000000007a000000->000000007c000000 (470828 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80200000->ffffffff806e2f04 (XEN) Init. ramdisk: ffffffff806e3000->ffffffff80e3aa00 (XEN) Phys-Mach map: ffffffff80e3b000->ffffffff811e2960 (XEN) Start info: ffffffff811e3000->ffffffff811e349c (XEN) Page tables: ffffffff811e4000->ffffffff811f1000 (XEN) Boot stack: ffffffff811f1000->ffffffff811f2000 (XEN) TOTAL: ffffffff80000000->ffffffff81400000 (XEN) ENTRY ADDRESS: ffffffff80200000 (XEN) Dom0 has maximum 2 VCPUs (XEN) elf_load_binary: phdr 0 at 0xffffffff80200000 -> 0xffffffff804c3c58 (XEN) elf_load_binary: phdr 1 at 0xffffffff804c3c80 -> 0xffffffff805d6ef0 (XEN) elf_load_binary: phdr 2 at 0xffffffff805d7000 -> 0xffffffff805d7c08 (XEN) elf_load_binary: phdr 3 at 0xffffffff805d8000 -> 0xffffffff80611388 (XEN) Initrd len 0x757a00, start at 0xffffffff806e3000 (XEN) Scrubbing Free RAM: .done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen). The machine is an Intel Core 2 Duo 6750 -- Kind Regards Rudi Ahlers CEO, SoftDux

1 0

Re: [CentOS-virt] test email, please ignore
by Ross S. W. Walker 01 Mar '08

01 Mar '08

Got it. -Ross ----- Original Message ----- From: centos-virt-bounces(a)centos.org <centos-virt-bounces(a)centos.org> To: centos-virt(a)centos.org <centos-virt(a)centos.org> Sent: Sat Mar 01 13:37:07 2008 Subject: [CentOS-virt] test email, please ignore I've been trying to subscribe to this thread, but I don't know if I am, so I'm just testing -- Kind Regards Rudi Ahlers CEO, SoftDux Office: 087 805-9573 Fax No: 086 609 6128 Cell: 082 554 7532 Web: http://www.SoftDux.com Forum: http://Forum.SoftDux.com Join SA WebHostingTalk today, on http://www.WebHostingTalk.co.za _______________________________________________ CentOS-virt mailing list CentOS-virt(a)centos.org http://lists.centos.org/mailman/listinfo/centos-virt ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

1 0

test email, please ignore
by Rudi Ahlers 01 Mar '08

01 Mar '08

I've been trying to subscribe to this thread, but I don't know if I am, so I'm just testing -- Kind Regards Rudi Ahlers CEO, SoftDux Office: 087 805-9573 Fax No: 086 609 6128 Cell: 082 554 7532 Web: http://www.SoftDux.com Forum: http://Forum.SoftDux.com Join SA WebHostingTalk today, on http://www.WebHostingTalk.co.za

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt March 2008