[Fedora-xen] Freeze with xen is relinquishing vga console

2008-04-20 Thread Maximilian Freisinger
Hello
i'm just testing f9 with xen but when i try to boot with xen kernel it freezes 
at xen is relinquishing vga console
Anyone an idea why?
My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset
thx, Felix
_
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


Re: [Fedora-xen] Freeze with xen is relinquishing vga console

2008-04-20 Thread Itamar - IspBrasil

are you trying to boot as dom0 or domu ?


Maximilian Freisinger wrote:

Hello
i'm just testing f9 with xen but when i try to boot with xen kernel it 
freezes at xen is relinquishing vga console

Anyone an idea why?
My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset
thx, Felix




--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


RE: [Fedora-xen] Freeze with xen is relinquishing vga console

2008-04-20 Thread Maximilian Freisinger
I'm trying to boot as dom0

 Date: Sun, 20 Apr 2008 12:49:36 -0300 From: [EMAIL PROTECTED] To: [EMAIL 
 PROTECTED] CC: fedora-xen@redhat.com Subject: Re: [Fedora-xen] Freeze with 
 xen is relinquishing vga console  are you trying to boot as dom0 or domu ? 
   Maximilian Freisinger wrote:  Hello  i'm just testing f9 with xen but 
 when i try to boot with xen kernel it   freezes at xen is relinquishing 
 vga console  Anyone an idea why?  My system is a AMD Athlon X2 with 
 Nvidia graphic and nvidia mc570 chipset  thx, Felix   
_
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


Re: [Fedora-xen] Freeze with xen is relinquishing vga console

2008-04-20 Thread Itamar - IspBrasil

fedora 9 kernel-xen package at this moment works only as domU

if you need dom0 try fedora 8



Maximilian Freisinger wrote:

I'm trying to boot as dom0




 Date: Sun, 20 Apr 2008 12:49:36 -0300
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 CC: fedora-xen@redhat.com
 Subject: Re: [Fedora-xen] Freeze with xen is relinquishing vga console

 are you trying to boot as dom0 or domu ?


 Maximilian Freisinger wrote:
  Hello
  i'm just testing f9 with xen but when i try to boot with xen 
kernel it

  freezes at xen is relinquishing vga console
  Anyone an idea why?
  My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 
chipset

  thx, Felix
 



--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


Re: [Fedora-xen] Unable to use multiple CPUs inside an HVM

2008-04-20 Thread Alroger L. Gomes F.

I have noticed that too.

David Levinger wrote:


Hey Guys,

I have a fully virtualized XP guest that is set to have 2 VCPUs and in 
the guest I see 2 CPUs but when it is under heavy load it only 
utilizes 1 of the physical cores.


Both xm and virsh show that the guest only has 1 CPU, but my config 
file and the guest show it should have 2.


What am I missing? How can I get this guest to have access to both cores?

Thanks!

David



--
Alroger Luiz Gomes Filho
SDEV - Smart Developments
http://www.sdev.com
http://cafe-ti.blog.br

So little time, so many systems . . .  


--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


Re: [Fedora-xen] Freeze with xen is relinquishing vga console

2008-04-20 Thread Alroger L. Gomes F.
Fedora9 does not work as a XEN Host (Dom0). I read that it will be back 
in Fedora10.

I sure would help if this was clearly specified in the Fedora9 wiki.

Maximilian Freisinger wrote:

Hello
i'm just testing f9 with xen but when i try to boot with xen kernel it 
freezes at xen is relinquishing vga console

Anyone an idea why?
My system is a AMD Athlon X2 with Nvidia graphic and nvidia mc570 chipset
thx, Felix

http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008

--
Alroger Luiz Gomes Filho
SDEV - Smart Developments
http://www.sdev.com
http://cafe-ti.blog.br

So little time, so many systems . . .  


--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen


Re: [Fedora-xen] no sda1 in DomU

2008-04-20 Thread Itamar - IspBrasil

create a initrd with xenblk module


Rainer Fuegenstein wrote:

hi,

I try to get the Centos.5-1.64 image from Jailtime.org running in a
Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the
DomU. I tried both file- and lvm-backed VBDs, but with no luck:

[...]
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device sda1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

configfile looks like this:

kernel = /boot/vmlinuz-2.6.18-53.1.14.el5xen
memory = 256
name = myzel
vif = [ '' ]
dhcp= dhcp
disk = ['phy:vg_virtual/lv_myzel_root,sda1,w',
'phy:vg_virtual/lv_myzel_swap,sda2,w']
# disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 
'tap:aio:/virtual/centos.swap,sda2,w']
root = /dev/sda1
extra = fastboot

(I also tried device name xvda, but to no avail)

Dom0 kernel:
Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 
x86_64 x86_64 GNU/Linux

any help appreciated. xend.log excerpt and DomU dmesg follows:

*** xend.log excerpt:

[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) 
XendDomainInfo.construct: None
[2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; 
need 2048; done.
[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) 
XendDomainInfo.initDomain: 18 1.0
[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) 
_initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100.
[2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; 
need 262144; done.
[2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 
vcpus=1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid  = 18
[2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize= 256
[2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image  = 
/boot/vmlinuz-2.6.18-53.1.14.el5xen
[2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn   = 1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2
[2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline=  
ip=:1.2.3.4eth0:dhcp root=/dev/sda1 fastboot
[2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk=
[2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus  = 1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features   =
[2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 
'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 
'online': '1', 'frontend-id': '18', 'type': 'phy'} to 
/local/domain/0/backend/vbd/18/2049.
[2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
number for sda2: [Errno 2] No such file or directory: '/dev/sda2'
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 
'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 
'online': '1', 'frontend-id': '18', 'type': 'phy'} to 
/local/domain/0/backend/vbd/18/2050.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 
'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/18/0'} 
to /local/domain/18/device/vif/0.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'handle': '0', 'script': 
'/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': 
'/local/domain/18/device/vif/0', 'mac': '00:16:3e:31:5d:55', 'online': '1', 
'frontend-id': '18'} to /local/domain/0/backend/vif/18/0.
[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:756) 
Storing VM details: {'shadow_memory': '0', 'uuid': 
'8772f05d-7d2b-fd71-dbcb-cfef1870e83c', 'on_reboot': 'restart', 'start_time': 

Re: [Fedora-xen] no sda1 in DomU

2008-04-20 Thread Alroger L. Gomes F.

Well, I suspect your disk parameters are simply wrong...

disk = 
['phy:vg_virtual/lv_myzel_root,sda1,w','phy:vg_virtual/lv_myzel_swap,sda2,w']
-This one seems to be messing / or /dev before vg_virtual.

disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 
'tap:aio:/virtual/centos.swap,sda2,w']
-This one I'm not sure, but I use file:/, have you tried it like below?

disk = ['file:/virtual/centos.5-1.64.img,sda1,w', 
'file:/virtual/centos.swap,sda2,w']


Rainer Fuegenstein wrote:

hi,

I try to get the Centos.5-1.64 image from Jailtime.org running in a
Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the
DomU. I tried both file- and lvm-backed VBDs, but with no luck:

[...]
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device sda1 or unknown-block(0,0)
Please append a correct root= boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

configfile looks like this:

kernel = /boot/vmlinuz-2.6.18-53.1.14.el5xen
memory = 256
name = myzel
vif = [ '' ]
dhcp= dhcp
disk = ['phy:vg_virtual/lv_myzel_root,sda1,w',
'phy:vg_virtual/lv_myzel_swap,sda2,w']
# disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 
'tap:aio:/virtual/centos.swap,sda2,w']
root = /dev/sda1
extra = fastboot

(I also tried device name xvda, but to no avail)

Dom0 kernel:
Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 x86_64 
x86_64 x86_64 GNU/Linux

any help appreciated. xend.log excerpt and DomU dmesg follows:

*** xend.log excerpt:

[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) 
XendDomainInfo.construct: None
[2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB free; 
need 2048; done.
[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) 
XendDomainInfo.initDomain: 18 1.0
[2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) 
_initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100.
[2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB free; 
need 262144; done.
[2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 
vcpus=1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid  = 18
[2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize= 256
[2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image  = 
/boot/vmlinuz-2.6.18-53.1.14.el5xen
[2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn   = 1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2
[2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline=  
ip=:1.2.3.4eth0:dhcp root=/dev/sda1 fastboot
[2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk=
[2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus  = 1
[2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features   =
[2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/18/2049'} to /local/domain/18/device/vbd/2049.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 
'dev': 'sda1', 'state': '1', 'params': 'vg_virtual/lv_myzel_root', 'mode': 'w', 
'online': '1', 'frontend-id': '18', 'type': 'phy'} to 
/local/domain/0/backend/vbd/18/2049.
[2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
number for sda2: [Errno 2] No such file or directory: '/dev/sda2'
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 
'x86_64-abi', 'backend-id': '0', 'state': '1', 'backend': 
'/local/domain/0/backend/vbd/18/2050'} to /local/domain/18/device/vbd/2050.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2050', 
'dev': 'sda2', 'state': '1', 'params': 'vg_virtual/lv_myzel_swap', 'mode': 'w', 
'online': '1', 'frontend-id': '18', 'type': 'phy'} to 
/local/domain/0/backend/vbd/18/2050.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
writing {'mac': '00:16:3e:31:5d:55', 'handle': '0', 'protocol': 'x86_64-abi', 
'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/18/0'} 
to /local/domain/18/device/vif/0.
[2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
writing {'domain': 'myzel', 'handle': '0', 

Re[2]: [Fedora-xen] no sda1 in DomU

2008-04-20 Thread Rainer Fuegenstein
hi,

II create a initrd with xenblk module

big thanks for the hint - I created the initrd by using

mkinitrd -v -f --preload=ext3 --preload=xenblk --preload=xennet 
--omit-raid-modules --omit-lvm-modules --omit-scsi-modules  
/boot/initrd-2.6.18.xenU.img  `uname -r`

the VM boots now, but hangs after starting the crond:

[...]
Press 'I' to enter interactive startup.
Setting clock : Sun Apr 20 18:15:04 EDT 2008 [  OK  ]
Starting udev: [  OK  ]
Setting hostname myzel:  [  OK  ]
No devices found
Setting up Logical Volume Management:   No volume groups found
[  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/dev/sda1: clean, 26084/1310720 files, 269769/2621440 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting sshd: [  OK  ]
Starting crond: [  OK  ]
... hangs here ...

also, although the network is configured properly, the interface can't
be pinged.

a xm shutdown myzel shuts down the VM properly (vm console shows
shutdown messages and finally terminates).

do I need to put any additional modules into the initrd ?

tnx in advance.

II Rainer Fuegenstein wrote:
 hi,

 I try to get the Centos.5-1.64 image from Jailtime.org running in a
 Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the
 DomU. I tried both file- and lvm-backed VBDs, but with no luck:

 [...]
 Initializing IPsec netlink socket
 NET: Registered protocol family 1
 NET: Registered protocol family 17
 XENBUS: Device with no driver: device/vbd/2049
 XENBUS: Device with no driver: device/vbd/2050
 XENBUS: Device with no driver: device/vif/0
 md: Autodetecting RAID arrays.
 md: autorun ...
 md: ... autorun DONE.
 VFS: Cannot open root device sda1 or unknown-block(0,0)
 Please append a correct root= boot option
 Kernel panic - not syncing: VFS: Unable to mount root fs on 
 unknown-block(0,0)

 configfile looks like this:

 kernel = /boot/vmlinuz-2.6.18-53.1.14.el5xen
 memory = 256
 name = myzel
 vif = [ '' ]
 dhcp= dhcp
 disk = ['phy:vg_virtual/lv_myzel_root,sda1,w',
 'phy:vg_virtual/lv_myzel_swap,sda2,w']
 # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 
 'tap:aio:/virtual/centos.swap,sda2,w']
 root = /dev/sda1
 extra = fastboot

 (I also tried device name xvda, but to no avail)

 Dom0 kernel:
 Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 
 x86_64 x86_64 x86_64 GNU/Linux

 any help appreciated. xend.log excerpt and DomU dmesg follows:

 *** xend.log excerpt:

 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) 
 XendDomainInfo.construct: None
 [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB 
 free; need 2048; done.
 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) 
 XendDomainInfo.initDomain: 18 1.0
 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) 
 _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100.
 [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB 
 free; need 262144; done.
 [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux dom=18 
 vcpus=1
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid  = 18
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize= 256
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image  = 
 /boot/vmlinuz-2.6.18-53.1.14.el5xen
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn   = 1
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:206) cmdline=  
 ip=:1.2.3.4eth0:dhcp root=/dev/sda1 fastboot
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:207) ramdisk=
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:208) vcpus  = 1
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:209) features   =
 [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
 number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
 [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:110) DevController: 
 writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 
 'x86_64-abi', 'backend-id': '0', 'state': '1',
 'backend': '/local/domain/0/backend/vbd/18/2049'} to 
 /local/domain/18/device/vbd/2049.
 [2008-04-20 21:17:10 xend 2627] DEBUG (DevController:112) DevController: 
 writing {'domain': 'myzel', 'frontend': '/local/domain/18/device/vbd/2049', 
 'dev': 'sda1', 'state': '1', 'params':
 'vg_virtual/lv_myzel_root', 'mode': 'w', 'online': '1', 'frontend-id': '18', 
 'type': 'phy'} to /local/domain/0/backend/vbd/18/2049.
 [2008-04-20 21:17:10 xend 2627] DEBUG (blkif:24) exception looking up device 
 number 

Re[2]: [Fedora-xen] no sda1 in DomU

2008-04-20 Thread Rainer Fuegenstein

II boot in single user mode, start network and update your linux with yum

ok, I'm now one step further:

- can boot into single user mode
- all block devices are mounted in the VM
- network starts properly, yum update loaded  applied some updates
- sshd starts, I can ssh into the vm from outside.

dmesg shows some strange messages:
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
Failed to obtain physical IRQ 6
floppy0: no floppy controllers found
lp: driver loaded but no devices found

my assumption: the VM can't connect to the console or some tty or
whatever because of the missing drivers what means that the login prompt 
doesn't show.

I exaleaded for the messages and found some threads with the same
problem, but without solution:
http://www.mail-archive.com/fedora-xen@redhat.com/msg00076.html
http://lists.xensource.com/archives/html/xen-users/2006-08/msg00064.html


II Rainer Fuegenstein wrote:
 hi,

 II  create a initrd with xenblk module

 big thanks for the hint - I created the initrd by using

 mkinitrd -v -f --preload=ext3 --preload=xenblk --preload=xennet 
 --omit-raid-modules --omit-lvm-modules --omit-scsi-modules  
 /boot/initrd-2.6.18.xenU.img  `uname -r`

 the VM boots now, but hangs after starting the crond:

 [...]
  Press 'I' to enter interactive startup.
 Setting clock : Sun Apr 20 18:15:04 EDT 2008 [  OK  ]
 Starting udev: [  OK  ]
 Setting hostname myzel:  [  OK  ]
 No devices found
 Setting up Logical Volume Management:   No volume groups found
 [  OK  ]
 Checking filesystems
 Checking all file systems.
 [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
 /dev/sda1: clean, 26084/1310720 files, 269769/2621440 blocks
 [  OK  ]
 Remounting root filesystem in read-write mode:  [  OK  ]
 Mounting local filesystems:  [  OK  ]
 Enabling /etc/fstab swaps:  [  OK  ]
 INIT: Entering runlevel: 3
 Entering non-interactive startup
 Bringing up loopback interface:  [  OK  ]
 Bringing up interface eth0:  [  OK  ]
 Starting system logger: [  OK  ]
 Starting kernel logger: [  OK  ]
 Starting sshd: [  OK  ]
 Starting crond: [  OK  ]
 ... hangs here ...

 also, although the network is configured properly, the interface can't
 be pinged.

 a xm shutdown myzel shuts down the VM properly (vm console shows
 shutdown messages and finally terminates).

 do I need to put any additional modules into the initrd ?

 tnx in advance.

 II  Rainer Fuegenstein wrote:

 hi,

 I try to get the Centos.5-1.64 image from Jailtime.org running in a
 Centos5 / Fedora8 Dom0, but it complains that there's no sda1 in the
 DomU. I tried both file- and lvm-backed VBDs, but with no luck:

 [...]
 Initializing IPsec netlink socket
 NET: Registered protocol family 1
 NET: Registered protocol family 17
 XENBUS: Device with no driver: device/vbd/2049
 XENBUS: Device with no driver: device/vbd/2050
 XENBUS: Device with no driver: device/vif/0
 md: Autodetecting RAID arrays.
 md: autorun ...
 md: ... autorun DONE.
 VFS: Cannot open root device sda1 or unknown-block(0,0)
 Please append a correct root= boot option
 Kernel panic - not syncing: VFS: Unable to mount root fs on 
 unknown-block(0,0)

 configfile looks like this:

 kernel = /boot/vmlinuz-2.6.18-53.1.14.el5xen
 memory = 256
 name = myzel
 vif = [ '' ]
 dhcp= dhcp
 disk = ['phy:vg_virtual/lv_myzel_root,sda1,w',
 'phy:vg_virtual/lv_myzel_swap,sda2,w']
 # disk = ['tap:aio:/virtual/centos.5-1.64.img,sda1,w', 
 'tap:aio:/virtual/centos.swap,sda2,w']
 root = /dev/sda1
 extra = fastboot

 (I also tried device name xvda, but to no avail)

 Dom0 kernel:
 Linux xenserv 2.6.18-53.1.14.el5xen #1 SMP Wed Mar 5 12:08:17 EST 2008 
 x86_64 x86_64 x86_64 GNU/Linux

 any help appreciated. xend.log excerpt and DomU dmesg follows:

 *** xend.log excerpt:

 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1349) 
 XendDomainInfo.construct: None
 [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262744 KiB 
 free; need 2048; done.
 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1397) 
 XendDomainInfo.initDomain: 18 1.0
 [2008-04-20 21:17:10 xend.XendDomainInfo 2627] DEBUG (XendDomainInfo:1436) 
 _initDomain:shadow_memory=0x0, maxmem=0x100, memory=0x100.
 [2008-04-20 21:17:10 xend 2627] DEBUG (balloon:127) Balloon: 262736 KiB 
 free; need 262144; done.
 [2008-04-20 21:17:10 xend 2627] INFO (image:136) buildDomain os=linux 
 dom=18 vcpus=1
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:201) domid  = 18
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:202) memsize= 256
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:203) image  = 
 /boot/vmlinuz-2.6.18-53.1.14.el5xen
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:204) store_evtchn   = 1
 [2008-04-20 21:17:10 xend 2627] DEBUG (image:205) console_evtchn = 2
 [2008-04-20 21:17:10 xend 2627] DEBUG