similar to: VFS: Unable to mount root fs via NFS, trying floppy.

Hi everyone I am a french student who try to use Xen sorry for my pore English and my ignorance about Xen. I try to install it on an old Compaq Proliant ML370 (as test). I have look at this howto: http://howtoforge.com/debian_etch_xen_3.1_p2 but at the first boot on the Xen Kernel: VFS: Cannot open root device "ida/c0d0p1" or unknown-block(0,0) Please append a correct "root="

I have several xen domu''s running in LVM partitions on the local hard drive. I have added a USB drive and tried to boot a domu from it but it failed. I assumed it was a SCSI device name conflict so I created a LVM on the USB drive but there is still a kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1) My config: 1 name = "samba"

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: important Tags: patch, squeeze We have several recent hardware systems from IBM which have the following problem when booting into hypervisor mode on squeeze (amd64, didn't check i386): [ 8.184733] pci 0000:01:00.0: BAR 6: no parent found for of device [0xfffe0000-0xffffffff] [ 8.213235] Initramfs unpacking failed: junk in

google yields nothing except for indicating that it is a boot loader problem. my dom0 partition is on a 9 GB SCSI disk drive. I have a raid1 device (md0) which I have created a series of partitions via lvm2. on boot, xm create /etc/xen/xm-single -c I get what looks like a normal boot until TCP: Hash tables configured (established 4096 bind 8192) NET: Registered protocol family 1 NET:

> I have my disk file stored on a NFS server. > I have tried these two approaches: > > A) Mounting the NFS directory in RW mode on a local directory > and specifying in my config file the complete path of my disk file. > > xm create configFile returned with this error: > Error: Error creating domain: vbd: Segment not found: > uname=file:/MountPoint/diskfile

Hi there. I have installed Xen successfully on Debian on i386 machines but I am having problems with an amd64 Opteron on a Sun X2100. Upon attempting to boot into dom0 I get the following: Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Insert root floppy and press ENTER Not having a floppy I press enter and it reboots. I have checked

Hello. =) I''m having a bit of trouble with my nfs xen installation and have spent much time trying to research/figure out this problem with no luck, so I''m hoping someone might be able to help me here. =) I''ve successfully installed xen 3.02 on Linux RH4 on my Sun single proc opteron v20z server. I''ve installed what I believe to be a base Linux OS on a

Hey All, I've an issue where libvirtd tries to access an NFS mount but errors out with: can't canonicalize path '/var/lib/one//datastores/0 . The unprevilidged user is able to read/write fine to the share. root_squash is used and for security reasons no_root_squash cannot be used. On the controller and node SELinux is disabled. [oneadmin@mdskvm-p01 ~]$ virsh -d 1 --connect

Hey All, Wondering if anyone had any suggestions on this topic? Cheers, Tom K. ------------------------------------------------------------------------------------- Living on earth is expensive, but it includes a free trip around the sun. On 4/9/2016 11:08 AM, TomK wrote: > Adding in libvir-list. > > Cheers, > Tom K. >

On Tue, Apr 12, 2016 at 10:29:29PM +0200, Martin Kletzander wrote: >On Tue, Apr 12, 2016 at 03:55:45PM -0400, TomK wrote: >>On 4/12/2016 3:40 PM, Martin Kletzander wrote: >>> [ I would be way easier to reply if you didn't top-post ] >>> >>> On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >>>> On 4/12/2016 11:45 AM, John Ferlan wrote:

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

Dear Sir, I have everything set up on my red hat Linux 7.1 linux box. For sometime I could mount cd's and floppies automatically, but now something seems to have gone wrong. I can't mount my floppy(/dev/fd0) and cdrom(/dev/cdrom) manually or automatically. At startup it says ... /dev/fd0 is not a valid block device. /dev/cdrom is write protected...mounting read only! mount: No

On Tue, Apr 12, 2016 at 03:55:45PM -0400, TomK wrote: >On 4/12/2016 3:40 PM, Martin Kletzander wrote: >> [ I would be way easier to reply if you didn't top-post ] >> >> On Tue, Apr 12, 2016 at 12:07:50PM -0400, TomK wrote: >>> On 4/12/2016 11:45 AM, John Ferlan wrote: >>>> What got my attention was the error message "initializing FS storage

Hi as described on the syslinux pxe webpage: A multi-hardware boot floppy is included with Windows Server 2000 and 2003. A company called Argon Technology used to offer a free-as-in-beer updated version, but is seems to have gone fully commercial. This floppy (which can also be burned to a CD using El Torito in floppy-emulation mode), is known to work with PXELINUX 2.03 or later only I'm

On bootup, it seems CentOS automatically mounts the floppy drive to /media/floppy. Is there a way to stop this from happening, short of removing the floppy drive from the system (as I don't use it)? Thanks, Ash Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi This is a PXELinux problem that I'm facing. The problem, in brief, is that I have a set of diskless nodes (AMD Athlon XP 1800+ with 256MB RAM) connected via an internal 172.20.0.0/24 network to a dual AMD Opteron running SuSE Linux 8.3 for AMD64. I want the remote machines to diskless boot off the main server and run independently. The diskless machines have a PXE-compliant BIOS for

hi there, some problem: -setup dhcp -setup tftp -setup pxelinux (?!) -dhcp: ok, client get correkt ip and so on -tftp: ok, client downloads pxelinux.0 -pxelinunx: seemed to be ok bootscreen: <snip> boot: loading memdisk... loading xyz.img Ready. the problem is, the image do not start. after the "ready" prompt nothing happens. the image file has generated from a bootable floppy