[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Crash DomU and after it Dom0 is frozen.
- To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, eXeC001er <execooler@xxxxxxxxx>
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Sat, 23 May 2009 13:43:32 -0700 (PDT)
- Cc:
- Delivery-date: Sat, 23 May 2009 13:44:06 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=1gPbYeBMUm/s+vJ3QeBgTrSVqxMb8h0lm+TI9aKbb5SYoMDkUV9T9EiqjbrVUZ6uq6ct+glKfJLBmYjqVdy3SjlDqwt+VGHNwy6mcVUNH+gbo9btkz2Pfd6TZ80mts96Eu/K3jhCk2GJK4X9MWlRBuAENKLHQ+nGeiE48iWP0lk=;
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Ok. Please, take a look at http://www.howtoforge.com/linux_lvm
and remove LVM. Try partition of type 83 like /dev/sdb6 any size
you need.
For example my development box has second drive with partitions
for DomUs and 2 Ubuntu Server Instances
root@ServerXen331:~# fdisk /dev/sdb
The number of cylinders for this disk is set to 30401.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier:
0x000e7f99
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 3647 29294496 83 Linux
/dev/sdb2 3648 4133 3903795 82 Linux swap / Solaris
/dev/sdb3 4134 6134 16073032+ 83 Linux
/dev/sdb4 6135 30282 193968810 5
Extended
/dev/sdb5 6135 8135 16073001 83 Linux
/dev/sdb6 8136 10136 16073001 83 Linux
/dev/sdb7 10137 12137 16073001 83 Linux
/dev/sdb8 12138 14138 16073001 83 Linux
/dev/sdb9 14139 16139 16073001 83 Linux
/dev/sdb10
16140 18140 16073001 83 Linux
/dev/sdb11 18141 20141 16073001 83 Linux
/dev/sdb12 20142 22142 16073001 83 Linux
/dev/sdb13 22143 24143 16073001 83 Linux
/dev/sdb14 24144 29796 45407691 83 Linux
/dev/sdb15 29797 30282 3903763+ 82 Linux swap /
Solaris
To install DomU :-
# losetup -f /var/isos/f10.iso
# losetup -a
Entry into installation python profile:-
disk = ['phy:/dev/sdb6,xvda,w','phy:/dev/loop0,hdc:cdrom,r']
I am pretty sure similar profile would work you.
I guess it's Ubuntu issue with LVM.
Boris.
--- On Sat, 5/23/09, eXeC001er <execooler@xxxxxxxxx> wrote:
From: eXeC001er <execooler@xxxxxxxxx>
Subject: Re: [Xen-devel] Crash DomU and after it Dom0 is frozen.
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, May 23, 2009, 3:42 PM
I installed guest domain on disk_in_file (disk=['file:/path_to_file']). The problem disappeared. What is it? Xen have problem with LVM ? 2009/5/23 eXeC001er <execooler@xxxxxxxxx>
I'm not understood. Can you explain more?2009/5/23 Boris Derzhavets <bderzhavets@xxxxxxxxx>
Just a second , could you install on /dev/sda(X) , b(X) not LVM ?From: eXeC001er < execooler@xxxxxxxxx>
Subject: Re: [Xen-devel] Crash DomU and after it Dom0 is frozen.
Date: Saturday, May 23, 2009, 8:12 AMNo, Dom0 does not restart, it is frozen with blinking Caps and Scroll leds on keyboard.
I try another kernel from OpenSolaris.
2009/5/23 Boris Derzhavets <bderzhavets@xxxxxxxxx>
Do you mean, it reboots your Dom0 ?
If yes, try something like Nevada b113/b114 (for me better b106 or OS200811) DomU
with ZFS image. Would it cause the same to Dom0 ?
If yes, then something is wrong with Xen 3.4 or kernel. I have OS0811 and SNV (b106) running with no issues in same Xen-Kernel environment . Yes, shutdown is slow , some
services may be placed in maintenance mode, but no harm to Dom0.
If no, I am sorry about NexentaOS.Subject: Re: [Xen-devel] Crash DomU and after it Dom0 is frozen.Date: Saturday,
May 23, 2009, 6:53 AMBoot is ok. Work is ok. Reboot is crash. 2009/5/23 Boris Derzhavets <bderzhavets@xxxxxxxxx>
What's gonna happen if you try to load NexentaOS PV DomU again ?
Boris.
--- On Sat, 5/23/09, eXeC001er <execooler@xxxxxxxxx> wrote:
From: eXeC001er <execooler@xxxxxxxxx>
Subject: [Xen-devel] Crash DomU and after it Dom0 is frozen.
To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Saturday, May 23, 2009, 5:25 AM
Hello!
I installed NexentaOS (Opensolaris kernel b104+). First booting system is true. Before first rebooting system updates boot_archive. It's false. Computer is freeze and CapsLock and ScrollLock is blinking.
Helps only RESET button. My system is Ubuntu 8.10, kernel-2.6.30-rc3-tip, Xen-3.4-Stable with debug options enabled. My hardware: AMD Athlon64X2 5400+, RAM 4GB.
For DomU: mem=1024, LVM disk DomU loaded with the help of PYGRUB. In attach: my .config for kernel, debug log from Xen, and domain-builder log. Thanks.
|
-----Inline Attachment Follows----- |
-----Inline Attachment Follows-----
|
-----Inline Attachment Follows-----
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
