Re: [CentOS-virt] domU reboot leaves VM crashing continually

2009-09-01 Thread Robert E. Moser
Hi Everyone,

 

I installed a fully virtualized VM on my system noted below.  To keep it
simple I made it puppy linux.  It runs as expected, including successful
reboots.  So… it appears that reboots are broken on my system for
paravirtualized systems.  I seem to recall the test install of windows I did
about a month ago seemed to work also as it was likewise fully virtualized.


 

Any ideas?

 

Thanks!


Robert Moser

 

From: centos-virt-boun...@centos.org [mailto:centos-virt-boun...@centos.org]
On Behalf Of Robert E. Moser
Sent: Saturday, August 29, 2009 5:05 PM
To: centos-virt@centos.org
Subject: [CentOS-virt] domU reboot leaves VM crashing continually

 

Greetings,

 

I’m new to xen virtualization on CentOS, but I have been unable to find the
answer to this problem I’m experiencing.  

 

My setup: AMD quad core (64bit), 8Gb ram.  CentOS 5.3 dom0, CentOS 5.3
domU’s (paravirtualized).  

Dom0 is set up with two NIC’s, the built-in and a PCI card, and I set up xen
bridging on both interfaces.   

 

My domU’s seem to boot up fine, run fine, and shutdown fine.  However, if I
attempt a reboot operation, they go into a state where they continually
crash on startup.  I have been unable to ascertain why this happens, and I
do not know how to fix it when it does happen.  So, my question is twofold:

 

1)  How do I get it out of the continual boot/crash cycle?  Xm destroy
doesn’t work, none of the GUI tools work.  So far the only answer has been
rebooting dom0, which is not a good answer L  

2)  Has anyone else seen this/solved this?  Besides being able to
manually fix it from #1 above, it sure would be nice to have it able to
reboot as expected.   

 

I haven’t worked with any fully virtualized guests yet, but I will try that
pretty soon and see if it evidences the same behavior.  

 

Uname –a è Linux prathis.localdomain 2.6.18-128.7.1.el5xen #1 SMP Mon Aug 24
09:14:33 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

 

Please let me know what additional information would be helpful or what I
can do to facilitate debugging this issue.  


Thanks!

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS-virt] Migrate windows VM from i386 Host to x86_64 host

2009-09-01 Thread Hildebrand, Nils, 232
Hi,

sounds strange.

Basically a dd should be enough to clone the machine.

I guess the hardware-model that gets through to the Windows-VM changes
when the Kernel-Achitecture changes.
So basically you swapped a 32-bit mainboard with a 64-bit mainboard - as
far as VM is concerned.

So I guess you have to reapair your Windows with some kind of
Windows-rescue-mode.

Which Windows is it?

With XP I had some success with booting from an install-media and then
going to repair existing after the install-process has detected the
already installed partition.

Afterwards all XP-patches had to be re-applied - though. But all
installed applications were still there.

You'd better try that procedure with cloned data...


Kind regards

Nils
 

 -Original Message-
 From: centos-virt-boun...@centos.org 
 [mailto:centos-virt-boun...@centos.org] On Behalf Of James Roman
 Sent: Thursday, July 30, 2009 3:24 PM
 To: Discussion about the virtualization on CentOS
 Subject: [CentOS-virt] Migrate windows VM from i386 Host to 
 x86_64 host
 
 Somehow one of our Xen servers ended up loaded with the i686 
 xen kernel, instead of the x86_64. The host has one windows 
 VM running on it. The OS partition is file-based, but it also 
 has a logical volume partition assigned for data. We would 
 like to migrate the host server to a 64-bit kernel, which 
 means moving the VM to one of our other 64-bit host servers. 
 We tried simply copying the OS partition and using dd to move 
 the LVM partition to a new host unsuccessfully. I'm pretty 
 sure that dd may not be appropriate when moving between 
 kernel architectures. 
 However, even without the LVM partition specified in the vm 
 config file, we are unable to boot the windows system. It 
 looks like it is blue screening immediately, since we never 
 get a console connection. Are there any instructions anywhere 
 for moving VMs from one host architecture to another?
 
 Current Host:
 Centos 5.3 i686 kernel 2.6.18-128.2.1.el5 Xen 3.0.3-80.el5_3.3
 
 Destination Host:
 Centos 5.3 x86_64 kernel 2.6.18-128.2.1.el5 Xen 3.0.3-80.el5_3.3
 
 
 
 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt
 
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS-virt] Cluster failover

2009-09-01 Thread Hildebrand, Nils, 232
Hi,

what cluster-software do you use?
Heartbeat with v2-syntax can do what you want - using weighted
priorities. 

Kind regards

Nils

 -Original Message-
 From: centos-virt-boun...@centos.org 
 [mailto:centos-virt-boun...@centos.org] On Behalf Of Paras pradhan
 Sent: Friday, July 17, 2009 10:15 PM
 To: linux clustering; Discussion about the virtualization on CentOS
 Subject: [CentOS-virt] Cluster failover
 
 hi,
 
 I have 3 nodes of CentOS 5.3 running xen virtual machines as 
 virtual machine service. This cluster is working fine. One 
 thing I would like to know that how to make failover only to  
 third node. What I mean to say is: I have 3 virtual machine  
 running on node 1 and 2 virtual machines running on node 2. 
 Now if node 1 fails I want my the node1 virtual machines  to 
 be stared only on node 3 but not on node2.
 Similary if node2 breaks, I want virtual machines to be started on
 node3 but never on node 1.
 
 Thanks !
 Paras.
 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 http://lists.centos.org/mailman/listinfo/centos-virt
 
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt


Re: [CentOS-virt] High CPU usage when running a CentOS guest inVirtualBox

2009-09-01 Thread Akemi Yagi
On Tue, Sep 1, 2009 at 5:33 AM, Hildebrand, Nils,
232nils.hildebr...@bamf.bund.de wrote:
 Hi,

 I just closed a service-request with sun.
 Topic: Why is Win32 slower running with two CPUs under VBox 3 than
 running with one CPU on VBox 2?

 I am running VBox on CentOS 5 64 bit (AMD Athlon Dual Core).

 The problem is - according to sun - the IO-APIC-emulation:
 On 32-bit-systems this io-apic-emulation (needed for passing interrupts
 between CPUs) has to use a full software-context-switching - making
 things slow.

 I tried recreating the problem with CentOS 5 64 Bit as VM, two CPUs: no
 problem
 With CentOS 5 32 Bit as VM: same problem.

 I guess some problems with multi-cpu-VMs using 32-bit-operating-systems
 on a 64-bit hardware are related to this - no matter if you are using
 xen (fully virtualized), VirtualBox or VMWare.

Interesting.  I do not have any 32-bit multi-cpu VMs myself, but I do
have access to such guests running on a host (64-bit) using kvm.  Both
CentOS-5 32-bit VM and CentOS-4 32-bit VM show normal load (near 100%
idle on all cpus).  They have the divider=10 option by the way.

Akemi
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt