Quantcast

Kernel panic on Xen 4.0.1 + Debian Squeeze

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Kernel panic on Xen 4.0.1 + Debian Squeeze

Илья Козлов
Hi.

I'm trying to run Xen 4.0.1 with Debian Squeeze in Dom0
My grub config:
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e
echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
multiboot /boot/xen-4.0-amd64.gz placeholder iommu=off
module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=e719719a-35aa-4ada-8ab5-9b6c676bc89e ro  quiet
echo 'Loading initial ramdisk ...'
module /boot/initrd.img-2.6.32-5-xen-amd64

After boot i see in console:
Failed to execute /init
Kernel panic - not syncing: No init found. Try passing init= option to kernel
Pid: 1, comm: swapper Not tained 2.6.32-5-xen-amd64 #1

Initramfs unpacking failed: junk in compressed archve
registering netback
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Kernel vmlinuz-2.6.32-5-xen-amd64 without xen boots normaly.

My "trouble" server is IBM HS-22 (2x Xeon E5530, 36 GB RAM, LSI SAS).
The same configuration works correctrly on other machine (supermicro-based).
But this is not "bad hardware" trouble - i tried two different HS-22


--
WBR, Kozlov Ilya AKA unicast AKA Lin

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Mark Adams-7
What partition is root? I believe "set root='(hd0,msdos1)'" is wrong
(dependant on if you actually have the partition setup as msdos!?) --
should be more like "set root='(hd0,1)'"

On Fri, Sep 17, 2010 at 06:05:30PM +0400, Ilya Kozlov wrote:

> Hi.
>
> I'm trying to run Xen 4.0.1 with Debian Squeeze in Dom0
> My grub config:
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
> xen {
>  insmod part_msdos
> insmod ext2
> set root='(hd0,msdos1)'
>  search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e
> echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
>  multiboot /boot/xen-4.0-amd64.gz placeholder iommu=off
> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
> root=UUID=e719719a-35aa-4ada-8ab5-9b6c676bc89e ro  quiet
>  echo 'Loading initial ramdisk ...'
> module /boot/initrd.img-2.6.32-5-xen-amd64
>
> After boot i see in console:
> Failed to execute /init
> Kernel panic - not syncing: No init found. Try passing init= option to
> kernel
> Pid: 1, comm: swapper Not tained 2.6.32-5-xen-amd64 #1
>
> Initramfs unpacking failed: junk in compressed archve
> registering netback
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> Kernel vmlinuz-2.6.32-5-xen-amd64 without xen boots normaly.
>
> My "trouble" server is IBM HS-22 (2x Xeon E5530, 36 GB RAM, LSI SAS).
> The same configuration works correctrly on other machine (supermicro-based).
> But this is not "bad hardware" trouble - i tried two different HS-22
>
>
> --
> WBR, Kozlov Ilya AKA unicast AKA Lin

> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Kernel panic on Xen 4.0.1 + Debian Squeeze

Mike Viau

> On Date: Fri, 17 Sep 2010 17:55:15 +0100 <[hidden email]> wrote:
>
> What partition is root? I believe "set root='(hd0,msdos1)'" is wrong
> (dependant on if you actually have the partition setup as msdos!?) --
> should be more like "set root='(hd0,1)'"

It seems to work out of the box with msdos based entries in squeeze.

I am running a grub similar to this and it works.

The only un standard part is " iommu=off "


-M

>
> On Fri, Sep 17, 2010 at 06:05:30PM +0400, Ilya Kozlov wrote:
>> Hi.
>>
>> I'm trying to run Xen 4.0.1 with Debian Squeeze in Dom0
>> My grub config:
>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
>> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
>> xen {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos1)'
>> search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e
>> echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
>> multiboot /boot/xen-4.0-amd64.gz placeholder iommu=off
>> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
>> root=UUID=e719719a-35aa-4ada-8ab5-9b6c676bc89e ro quiet
>> echo 'Loading initial ramdisk ...'
>> module /boot/initrd.img-2.6.32-5-xen-amd64
>>
>> After boot i see in console:
>> Failed to execute /init
>> Kernel panic - not syncing: No init found. Try passing init= option to
>> kernel
>> Pid: 1, comm: swapper Not tained 2.6.32-5-xen-amd64 #1
>>
>> Initramfs unpacking failed: junk in compressed archve
>> registering netback
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>>
>> Kernel vmlinuz-2.6.32-5-xen-amd64 without xen boots normaly.
>>
>> My "trouble" server is IBM HS-22 (2x Xeon E5530, 36 GB RAM, LSI SAS).
>> The same configuration works correctrly on other machine (supermicro-based).
>> But this is not "bad hardware" trouble - i tried two different HS-22
>>
>>
>> --
>> WBR, Kozlov Ilya AKA unicast AKA Lin
>
>> _______________________________________________
>> Xen-users mailing list
>> [hidden email]
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users
     
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Илья Козлов
I added option "iommu=off", becouse without it system show black screen and reboots.

> What partition is root? I believe "set root='(hd0,msdos1)'" is wrong
> (dependant on if you actually have the partition setup as msdos!?) --
> should be more like "set root='(hd0,1)"
I tried this option with the same result

2010/9/18 Mike Viau <[hidden email]>

> On Date: Fri, 17 Sep 2010 17:55:15 +0100 <[hidden email]> wrote:
>
> What partition is root? I believe "set root='(hd0,msdos1)'" is wrong
> (dependant on if you actually have the partition setup as msdos!?) --
> should be more like "set root='(hd0,1)'"

It seems to work out of the box with msdos based entries in squeeze.

I am running a grub similar to this and it works.

The only un standard part is " iommu=off "


-M

>
> On Fri, Sep 17, 2010 at 06:05:30PM +0400, Ilya Kozlov wrote:
>> Hi.
>>
>> I'm trying to run Xen 4.0.1 with Debian Squeeze in Dom0
>> My grub config:
>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
>> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
>> xen {
>> insmod part_msdos
>> insmod ext2
>> set root='(hd0,msdos1)'
>> search --no-floppy --fs-uuid --set e719719a-35aa-4ada-8ab5-9b6c676bc89e
>> echo 'Loading Linux 2.6.32-5-xen-amd64 ...'
>> multiboot /boot/xen-4.0-amd64.gz placeholder iommu=off
>> module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder
>> root=UUID=e719719a-35aa-4ada-8ab5-9b6c676bc89e ro quiet
>> echo 'Loading initial ramdisk ...'
>> module /boot/initrd.img-2.6.32-5-xen-amd64
>>
>> After boot i see in console:
>> Failed to execute /init
>> Kernel panic - not syncing: No init found. Try passing init= option to
>> kernel
>> Pid: 1, comm: swapper Not tained 2.6.32-5-xen-amd64 #1
>>
>> Initramfs unpacking failed: junk in compressed archve
>> registering netback
>> Kernel panic - not syncing: VFS: Unable to mount root fs on
>> unknown-block(0,0)
>>
>> Kernel vmlinuz-2.6.32-5-xen-amd64 without xen boots normaly.
>>
>> My "trouble" server is IBM HS-22 (2x Xeon E5530, 36 GB RAM, LSI SAS).
>> The same configuration works correctrly on other machine (supermicro-based).
>> But this is not "bad hardware" trouble - i tried two different HS-22
>>
>>
>> --
>> WBR, Kozlov Ilya AKA unicast AKA Lin
>
>> _______________________________________________
>> Xen-users mailing list
>> [hidden email]
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users



--
WBR, Kozlov Ilya AKA unicast AKA Lin


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Kernel panic on Xen 4.0.1 + Debian Squeeze

Mike Viau

> On Tue, 21 Sep 2010 20:45:22 +0400 <[hidden email]> wrote:
>
> I added option "iommu=off", becouse without it system show black screen
> and reboots.
>

Does this black screen come up right after the kernel begins loading or just before the X windows system starts, like gdm3 in case of Debian systems running the Gnome DE.

On my system the black screen issue was resolved by adding "nomodeset" instead of "iommu=off" (but I do not recall the system rebooting).

Anyways, I hope that help!


-M
     
_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Илья Козлов
Black screen came up after the xen begins loading, and after "loading dom0" server goes reboot. This issue was solved by adding "iommu=off", but there was another described in first letter :-(

2010/9/21 Mike Viau <[hidden email]>

> On Tue, 21 Sep 2010 20:45:22 +0400 <unicast.ru@gmail.com> wrote:
>
> I added option "iommu=off", becouse without it system show black screen
> and reboots.
>

Does this black screen come up right after the kernel begins loading or just before the X windows system starts, like gdm3 in case of Debian systems running the Gnome DE.

On my system the black screen issue was resolved by adding "nomodeset" instead of "iommu=off" (but I do not recall the system rebooting).

Anyways, I hope that help!


-M

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users



--
WBR, Kozlov Ilya AKA unicast AKA Lin


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Илья Козлов
Hm, the problem is in grub2, with grub1 system boots successfully.

My currently grub2 menu entry is:
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod ext2
set root=(hd0,1)
multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1 ro
module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64

grub1 menu entry is:
title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
root (hd0,0)
kernel /boot/xen-4.0-amd64.gz iommu=off
module /boot/vmlinuz-2.6.32-5-xen-amd64 root=/dev/sda1 ro console=tty0
module /boot/initrd.img-2.6.32-5-xen-amd64

What's wrong in my configuration?

2010/9/22 Ilya Kozlov <unicast.ru@gmail.com>
Black screen came up after the xen begins loading, and after "loading dom0" server goes reboot. This issue was solved by adding "iommu=off", but there was another described in first letter :-(

2010/9/21 Mike Viau <[hidden email]>


> On Tue, 21 Sep 2010 20:45:22 +0400 <unicast.ru@gmail.com> wrote:
>
> I added option "iommu=off", becouse without it system show black screen
> and reboots.
>

Does this black screen come up right after the kernel begins loading or just before the X windows system starts, like gdm3 in case of Debian systems running the Gnome DE.

On my system the black screen issue was resolved by adding "nomodeset" instead of "iommu=off" (but I do not recall the system rebooting).

Anyways, I hope that help!


-M

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users



--
WBR, Kozlov Ilya AKA unicast AKA Lin




--
WBR, Kozlov Ilya AKA unicast AKA Lin


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Mark Adams-7
your root partition is hd0,0 not hd0,1.

On Wed, Sep 22, 2010 at 11:35:21PM +0400, Ilya Kozlov wrote:

> Hm, the problem is in grub2, with grub1 system boots successfully.
>
> My currently grub2 menu entry is:
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
> xen {
>  insmod ext2
> set root=(hd0,1)
> multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
>  module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1
> ro
> module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64
>
> grub1 menu entry is:
> title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
> root (hd0,0)
> kernel /boot/xen-4.0-amd64.gz iommu=off
> module /boot/vmlinuz-2.6.32-5-xen-amd64 root=/dev/sda1 ro console=tty0
> module /boot/initrd.img-2.6.32-5-xen-amd64
>
> What's wrong in my configuration?
>
> 2010/9/22 Ilya Kozlov <[hidden email]>
>
> > Black screen came up after the xen begins loading, and after "loading dom0"
> > server goes reboot. This issue was solved by adding "iommu=off", but there
> > was another described in first letter :-(
> >
> > 2010/9/21 Mike Viau <[hidden email]>
> >
> >
> >> > On Tue, 21 Sep 2010 20:45:22 +0400 <[hidden email]> wrote:
> >> >
> >> > I added option "iommu=off", becouse without it system show black screen
> >> > and reboots.
> >> >
> >>
> >> Does this black screen come up right after the kernel begins loading or
> >> just before the X windows system starts, like gdm3 in case of Debian systems
> >> running the Gnome DE.
> >>
> >> On my system the black screen issue was resolved by adding "nomodeset"
> >> instead of "iommu=off" (but I do not recall the system rebooting).
> >>
> >> Anyways, I hope that help!
> >>
> >>
> >> -M
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> [hidden email]
> >> http://lists.xensource.com/xen-users
> >>
> >
> >
> >
> > --
> > WBR, Kozlov Ilya AKA unicast AKA Lin
> >
> >
>
>
> --
> WBR, Kozlov Ilya AKA unicast AKA Lin

> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Markus Schönhaber-19
23.09.2010 16:19, Mark Adams:

> your root partition is hd0,0 not hd0,1.

No. Grub2 partition numbers start at 1.

> On Wed, Sep 22, 2010 at 11:35:21PM +0400, Ilya Kozlov wrote:
>> Hm, the problem is in grub2, with grub1 system boots successfully.
>>
>> My currently grub2 menu entry is:
>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
>> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
>> xen {
>>  insmod ext2
>> set root=(hd0,1)
>> multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
>>  module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1
>> ro
>> module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64
>>
>> grub1 menu entry is:
>> title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
>> root (hd0,0)

--
Regards
  mks

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Mark Adams-7
Good point! Still haven't got my head around grub2 yet. checked one of mine
Ilya and it also has msdos used (must be default). This works for me
(Your device ID's should match yours..)

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set 76b3f0ee-34d8-4a13-8a6e-44bd9366cd8c
        echo    'Loading Linux 2.6.32-5-xen-amd64 ...'
        multiboot       /xen-4.0-amd64.gz dom0_mem=2048M  
        module  /vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=25c3ac79-6850-498d-afcf-ea42970e94fd ro  quiet
        echo    'Loading initial ramdisk ...'
        module  /initrd.img-2.6.32-5-xen-amd64
}

Regards,
Mark

On Thu, Sep 23, 2010 at 04:49:49PM +0200, Markus Schönhaber wrote:

> 23.09.2010 16:19, Mark Adams:
>
> > your root partition is hd0,0 not hd0,1.
>
> No. Grub2 partition numbers start at 1.
>
> > On Wed, Sep 22, 2010 at 11:35:21PM +0400, Ilya Kozlov wrote:
> >> Hm, the problem is in grub2, with grub1 system boots successfully.
> >>
> >> My currently grub2 menu entry is:
> >> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
> >> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
> >> xen {
> >>  insmod ext2
> >> set root=(hd0,1)
> >> multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
> >>  module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1
> >> ro
> >> module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64
> >>
> >> grub1 menu entry is:
> >> title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
> >> root (hd0,0)
>
> --
> Regards
>   mks
>
> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic on Xen 4.0.1 + Debian Squeeze

Adrian Perez
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/23/2010 12:29 PM, Mark Adams wrote:

> Good point! Still haven't got my head around grub2 yet. checked one of mine
> Ilya and it also has msdos used (must be default). This works for me
> (Your device ID's should match yours..)
>
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class xen {
>         insmod part_msdos
>         insmod ext2
>         set root='(hd0,msdos1)'
>         search --no-floppy --fs-uuid --set 76b3f0ee-34d8-4a13-8a6e-44bd9366cd8c
>         echo    'Loading Linux 2.6.32-5-xen-amd64 ...'
>         multiboot       /xen-4.0-amd64.gz dom0_mem=2048M  
>         module  /vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=25c3ac79-6850-498d-afcf-ea42970e94fd ro  quiet
>         echo    'Loading initial ramdisk ...'
>         module  /initrd.img-2.6.32-5-xen-amd64
> }
>
> Regards,
> Mark
>
> On Thu, Sep 23, 2010 at 04:49:49PM +0200, Markus Schönhaber wrote:
>> 23.09.2010 16:19, Mark Adams:
>>
>>> your root partition is hd0,0 not hd0,1.
>>
>> No. Grub2 partition numbers start at 1.
>>
>>> On Wed, Sep 22, 2010 at 11:35:21PM +0400, Ilya Kozlov wrote:
>>>> Hm, the problem is in grub2, with grub1 system boots successfully.
>>>>
>>>> My currently grub2 menu entry is:
>>>> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN
>>>> 4.0-amd64' --class debian --class gnu-linux --class gnu --class os --class
>>>> xen {
>>>>  insmod ext2
>>>> set root=(hd0,1)
>>>> multiboot (hd0,1)/boot/xen-4.0-amd64.gz dummy=dummy iommu=off
>>>>  module (hd0,1)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy root=/dev/sda1
>>>> ro
>>>> module (hd0,1)/boot/initrd.img-2.6.32-5-xen-amd64
>>>>
>>>> grub1 menu entry is:
>>>> title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
>>>> root (hd0,0)
>>
>> --
>> Regards
>>   mks
>>
>> _______________________________________________
>> Xen-users mailing list
>> [hidden email]
>> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> [hidden email]
> http://lists.xensource.com/xen-users
Have you managed to get xen running on squeeze. I have lot of IOAPIC and
ACPI problems which prevent me from starting it.

- --
Best Regards,

Adrian Perez <[hidden email]>,
             <[hidden email]>,
             <[hidden email]>

+ Ubuntu Developer. http://www.ubuntu.com
+ Debian Developer. http://www.debian.org
+ GigaTux VPS hosting user. http://www.gigatux.com
+ Certified Ruby on Rails Developer. http://www.rubyonrails.org
+ Certified Java Developer. http://java.sun.com
+ Certified Python Developer. http://python.org
+ Certified Ajax Developer.
+ Certified RedHat User. http://www.redhat.com
+ Certified Linux/Unix User.

GPG Key ID: 8A9A3084
GPG Key Fingerprint: 99E8 E74E 7B4F 93AE F32A
                     5523 9973 0D5C 8A9A 3084

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkyc0vUACgkQmXMNXIqaMIQECwCeLPbT+Y7u0UWQZNG0p2vRlua8
DSkAn3apz4ytjbOaCabr8Ieaq+OYBoma
=naS5
-----END PGP SIGNATURE-----

_______________________________________________
Xen-users mailing list
[hidden email]
http://lists.xensource.com/xen-users
Loading...