virt

virt@lists.centos.org

2 participants
1612 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt