On 14 November 2011 01:35, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:
>
> And
> again, your eth0 got an ipv4 address from the network - I assume you get
> addresses from dhcp?
Correct. The fact that the dhcp client works but the networking doesn't, seems
very strange even to me actually.
>
> None the less. post your dmesg for 3.1, and I'll compare it to the dmesg for
> 2.6.37 you previously posted. (Yeah, I remember - no network. Redirect it:
> dmesg > ~/something-in-your-homedir.)
Of course! ;-)
http://pastebin.com/ikKPe6n3
> See - there is a vmlinux *and* a vmlinuz xen kernel. You could try either
> spelling in your menu.lst. This goes back to when you were trying to boot
> kernel-xen as a pv domu. Your menu.lst stanza had no xen.gz entry - only
> 'kernel vmlinuz...' and 'initrd initrd...' lines. I was just suggesting
> testing whether the vmlinux has a more compatible executable format than the
> vmlinuz. (Although, since they are both ELF formats, there probably won't be
> any difference.)
OK, I did it. Anyway, as far as I can see, vmlinuz is only a symbolic link.
here's the ls -l /boot after the kernel-xen installation:
http://pastebin.com/E0EkKXZF
If I boot using these entries:
kernel /boot/vmlinux-2.6.37.6-0.9-xen
root=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part2
resume=/dev/disk/by-id/ata-QEMU_HARDDISK_QM00001-part1 splash=silent
quiet showopts vga=0x314
initrd /boot/initrd-2.6.37.6-0.9-xen
(I gunzipped the vmlinux file)
It still says: Error 13: Invalid or unsupported executable format.
Same thing if I use the .gz file of course.
> Again, there is no directory entry for a soft link called 'driver' pointing
> to a kernel module, such as cirrusfb, so vesa is probably still in charge. See
> if anything interesting comes from 'cat
> /sys/bus/pci/devices/0000:00:02.0/uevent'.
With the 2.6.37 kernel booted:
PCI_CLASS=30000
PCI_ID=1013:00B8
PCI_SUBSYS_ID=5853:0001
PCI_SLOT_NAME=0000:00:02.0
MODALIAS=pci:v00001013d000000B8sv00005853sd00000001bc03sc00i00
> No, I mean do you see lines that evdev loaded? 'grep evdev
> /var/log/Xorg.0.log'
Yes, I see those lines.
domU: http://pastebin.com/emieNZxy
dom0: http://pastebin.com/WxSdq74i
> I don't know what you mean by blocked. Did the installer load, and you got a
> menu, but you couldn't get it to start installing packages?
The package installation begins, but it's very slow and it blocks.
> Your link to the
> setup procedure mentioned setting up Apache to mount your cdrom. You could
> just as easily have used an nfs mount of the cdrom.
I mounted the ISO image as loop in /var/www/localhost/htdocs/suse11. Maybe
the memory is going to run out if I launch both the dom0 and the mount
-o loop and
also the domU start.
> The problem is you can get
> your dom0 to load a cd in a pv install, but once the installer is handed
> control, an inherent limitation of a pv domu or install, is it doesn't know
> about cd devices.
The installer got frozen. No possibility to go ahead. Sometime even my dom0
got blocked, so I have to use sysrq magic keys to reboot. Maybe it's
due to a memory
issue, even if the system is still accessible via ssh and is "alive".
It seems the
hypervisor die. Every xl command stucks without giving any reply in the console.
Thanks a lot again,
--
Flavio
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home