Hello, I''m trying to virtualize with xen a SLES11 SP1 (physical) in a SLESSP2 Dom0. When you start the domU, this is not the virtual disk. Modify fstab and menu.lst but sige without starting. The truth that I''m a little confused, can not see that I''m missing. The error is: mount: devpts already mounted or /dev/pts busy mount: according to mtab, devpts is already mounted on /dev/pts Boot logging started on /dev/ttyS0(/dev/console) at Tue Jul 30 18:34:10 2013 resume device not found (ignoring) Waiting for device /dev/hda2 to appear: [ 2.199923] ..............................Could not find /dev/hda2. Want me to fall back to /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993? (Y) Any suggestions to look at? domU.cfg name="bcs-bkp" memory=1024 maxmem=1024 vcpus=2 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" #boot = "ba" builder="hvm" device_model="/usr/lib/xen/bin/qemu-dm" kernel="/usr/lib/xen/boot/hvmloader" disk=[ ''file:/mnt/util/xen-images/bcs/disco1,hda,w''] vnc=1 vncunused=1 acpi=1 serial="pty Files fstab and menu.lst configuration - https://docs.google.com/file/d/0B8rk...it?usp=sharing Console error log - https://docs.google.com/file/d/0B8rk...it?usp=sharing Log debuger of Dumu - https://docs.google.com/file/d/0B8rk...it?usp=sharing hanks for reading
Hello. El 30/07/13 18:10, Flako escribió:> Hello, I''m trying to virtualize with xen a SLES11 SP1 (physical) in a > SLESSP2 Dom0. > When you start the domU, this is not the virtual disk. > Modify fstab and menu.lst but sige without starting. > The truth that I''m a little confused, can not see that I''m missing. > > The error is: > mount: devpts already mounted or /dev/pts busy > mount: according to mtab, devpts is already mounted on /dev/pts > Boot logging started on /dev/ttyS0(/dev/console) at Tue Jul 30 18:34:10 2013 > resume device not found (ignoring) > Waiting for device /dev/hda2 to appear: [ 2.199923] > ..............................Could not find /dev/hda2. > Want me to fall back to > /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993? (Y)Maybe the disk is seen within DomU as sda, not hda? Please show the config for grub and fstab. Did you generated those two configs, or the installer did?> Any suggestions to look at? > > > domU.cfg > name="bcs-bkp" > memory=1024 > maxmem=1024 > vcpus=2 > on_poweroff="destroy" > on_reboot="restart" > on_crash="destroy" > #boot = "ba" > builder="hvm" > device_model="/usr/lib/xen/bin/qemu-dm" > kernel="/usr/lib/xen/boot/hvmloader" > disk=[ ''file:/mnt/util/xen-images/bcs/disco1,hda,w''] > vnc=1 > vncunused=1 > acpi=1 > serial="pty > > > Files fstab and menu.lst configuration - > https://docs.google.com/file/d/0B8rk...it?usp=sharing > Console error log - https://docs.google.com/file/d/0B8rk...it?usp=sharing > Log debuger of Dumu - https://docs.google.com/file/d/0B8rk...it?usp=sharingAll this links are broken. The files content and the console output are still a mystery. -- Alexandre Kouznetsov
2013/7/31 Alexandre Kouznetsov <alk@ondore.com>:> Hello. > > El 30/07/13 18:10, Flako escribió: > >> Hello, I''m trying to virtualize with xen a SLES11 SP1 (physical) in a >> SLESSP2 Dom0. >> When you start the domU, this is not the virtual disk. >> Modify fstab and menu.lst but sige without starting. >> The truth that I''m a little confused, can not see that I''m missing. >> >> The error is: >> mount: devpts already mounted or /dev/pts busy >> mount: according to mtab, devpts is already mounted on /dev/pts >> Boot logging started on /dev/ttyS0(/dev/console) at Tue Jul 30 18:34:10 >> 2013 >> resume device not found (ignoring) >> Waiting for device /dev/hda2 to appear: [ 2.199923] >> ..............................Could not find /dev/hda2. >> Want me to fall back to >> /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993? (Y) > > > Maybe the disk is seen within DomU as sda, not hda? Please show the config > for grub and fstab. Did you generated those two configs, or the installer > did?Hi Alexandre, Sorry for the broken link (I thought that had revised) now revised so it should work. Files fstab and grub menu.lst configuration https://docs.google.com/file/d/0B8rkUchOnWAKbWlGTzFrNzFjZ1E/edit?usp=sharing Console error log - https://docs.google.com/file/d/0B8rkUchOnWAKb2N4TWE0d1NSMFU/edit?usp=sharing Log debuger of DomU - https://docs.google.com/file/d/0B8rkUchOnWAKNWpHQktINHRoNjg/edit?usp=sharing I think they are hda because SLES11SP1 installation cd shows them as hda. IF I define settings "disk = [''tap: aio :/ mnt/xendomain/bcs/disco1, sda, w''", the bios shows the eror: "xen boot from hard disk failed Could not read the boot disk" The settings I believe them (based on another HVM) and modify fstab and menu.lst.
El 31/07/13 15:30, Flako escribió:> 2013/7/31 Alexandre Kouznetsov <alk@ondore.com>: >> Hello. >> >> El 30/07/13 18:10, Flako escribió: >> >>> Hello, I''m trying to virtualize with xen a SLES11 SP1 (physical) in a >>> SLESSP2 Dom0. >>> When you start the domU, this is not the virtual disk. >>> Modify fstab and menu.lst but sige without starting. >>> The truth that I''m a little confused, can not see that I''m missing. >>> >>> The error is: >>> mount: devpts already mounted or /dev/pts busy >>> mount: according to mtab, devpts is already mounted on /dev/pts >>> Boot logging started on /dev/ttyS0(/dev/console) at Tue Jul 30 18:34:10 >>> 2013 >>> resume device not found (ignoring) >>> Waiting for device /dev/hda2 to appear: [ 2.199923] >>> ..............................Could not find /dev/hda2. >>> Want me to fall back to >>> /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993? (Y) >> >> >> Maybe the disk is seen within DomU as sda, not hda? Please show the config >> for grub and fstab. Did you generated those two configs, or the installer >> did? > > Hi Alexandre, > Sorry for the broken link (I thought that had revised) now revised so > it should work. > > Files fstab and grub menu.lst configuration > https://docs.google.com/file/d/0B8rkUchOnWAKbWlGTzFrNzFjZ1E/edit?usp=sharingmenu.lst and fstab always make reference to hda. If your disk is detected by the guest kernel under a different name, this won''t work. Find out how your disk is detected by your guest OS. hda, hdb, sda, whatever.> Console error log - > https://docs.google.com/file/d/0B8rkUchOnWAKb2N4TWE0d1NSMFU/edit?usp=sharingApparently, your DomU can see a disk, but it''s not called "hda" within DomU (not the same as in Dom0) or, at least, there is no "hda2". It also says that there is a promising device called /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993. Surely it''s a symbolic link to the real device. Another thing to check out, is that your DomU config does not have "ioemu" flag on the disk, that allows the guest OS to use paravirtualized driver and significantly boosts the IO speed. The message "FATAL: Module xen_vbd not found." suggests that there is some problem with this PV driver. You may try to set the flag up: disk=[ ''file:/mnt/util/xen-images/bcs/disco1,ioemu:hda,w''] This is not the recommended configuration for production, but at least it may tell you if the problem is related with this.> Log debuger of DomU - > https://docs.google.com/file/d/0B8rkUchOnWAKNWpHQktINHRoNjg/edit?usp=sharing > > I think they are hda because SLES11SP1 installation cd shows them as hda.Sometimes the disk is detected under a different name after the installation, that''s why the UUID is often used instead of the device name.> IF I define settings "disk = [''tap: aio :/ mnt/xendomain/bcs/disco1, > sda, w''", the bios shows the eror: "xen boot from hard disk failed > Could not read the boot disk"No, the disk settings in the DomU configuration was fine as "hda", do not modify them. Greetings. -- Alexandre Kouznetsov
Hello. El 01/08/13 15:31, Flako escribió:> Alexandre > Should not put the puck as if sdxx or hdxx, but it sure is the 2nd > partition (this is how you create the partitions and is as seen from > qemu-nbd) > > Believing the links (/dev/disk/by-uuid/) and mknod devices > accessing the disk via qemu-nbd (probe with hda2,hdb2,sda2,sdb2). But > then when you start the domU in the bash-like console do not appear. > :( > Then I did the same from the bash-like domU console and try to > mount the disk, the mount command shows the error ''is not a valid > block device'' > > $ mount -t reiserfs /dev/sdb2 /aa > mount: /dev/sdb2 is not a valid block deviceIf you can get into that back-like domU console again, try this: ls -al /dev/disk/by-uuid ls -al /dev/disk/by-uuid/fb5c6b0b-3688-43cd-8b20-d8fa3a0ba993> xen_vbd locate the module in the domU (SLES11SP1) and the module does not exist. > Looking in there dom0 (SLES11SP2) module, this in / > lib/modules/3.0.13-0.27-default/updates/blkfront/xen-vbd.ko (Package > xen-kmp-default-4.1.2_14_3.0.13_0.27-0.5.5.rpm)I did not understand if the file /lib/modules/3.0.13-0.27-default/updates/blkfront/xen-vbd.ko is present in your system or not. If not, reinstall package xen-kmp-default-4.1.2_14_3.0.13_0.27-0.5.5.rpm. Verify if the kernel you are running is indeed "3.0.13-0.27-default". It''s also possible, that the module is present in the system but not in the initrd (check that). In that case, rebuid your initrd. This reference should tell you how to add modules and rebuild initrd. ftp://ftp-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.2/suselinux-adminguide_en/ch10.html> I have already run out of ideas .. > Any idea where to look and read?Did you tried using ioemu flag? -- Alexandre Kouznetsov