Hi, As a previous thread in http://lists.xensource.com/archives/html/xen-users/2006-06/msg01111.html tells, it should be possible tun run hvm domains with a physical disk. There where other threads about this, but no solution for my current problem. When I try to use a disk defined as disk = [ ''phy:data/faitest-client-generic-hvm-disk,ioemu:hda,w''] (The device is a lvm volume) in my hvm domU, I get the message: Error: hvm: for qemu vbd type=file&dev=hda~hdd It seems qemu is expecting to get a file-based disk. What do I need to do to get hvm use a physical disk? I built Xen-3.0-testing from sources, so it might be that I am missing a dependency (no idea where they are documented, I figured the necessary dependenices for hvm myself). Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
"Henning Sprang" <henning_sprang@gmx.de> wrote on 08/13/2006 02:49:37 PM:> Hi, > As a previous thread in > http://lists.xensource.com/archives/html/xen-users/2006-06/msg01111.html > tells, it should be possible tun run hvm domains with a physical disk. > There where other threads about this, but no solution for my current > problem. > When I try to use a disk defined as > > disk = [ ''phy:data/faitest-client-generic-hvm-disk,ioemu:hda,w''] > > (The device is a lvm volume) in my hvm domU, I get the message: > > Error: hvm: for qemu vbd type=file&dev=hda~hdd > > It seems qemu is expecting to get a file-based disk. What do I need to > do to get hvm use a physical disk?I''m using LVM volumes for my HVM disks just fine. Did you try specifying the full name of the device with the "/dev/" prefix? For example: disk = [ ''phy:/dev/data/faitest-client-generic-hvm-disk,ioemu:hda,w''] My HVM domU config file has: disk = [''phy:/dev/virt-blkdev-backend/hvm1,ioemu:hda,w'', ''phy:/dev/virt-blkdev-backend/usr,ioemu:hdb,r'',''phy:/dev/virt-blkdev-disk_io_test/hvm1,ioemu:hdd,w''] and it works fine. The first entry is the domU boot disk with the root file system partition, the second entry is the read-only /usr file system, the third entry is a blank disk for testing disk I/O. Steve D. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On 8/14/06, Steve Dobbelstein <steved@us.ibm.com> wrote:> [...] > > It seems qemu is expecting to get a file-based disk. What do I need to > > do to get hvm use a physical disk? > > I''m using LVM volumes for my HVM disks just fine. Did you try specifying > the full name of the device with the "/dev/" prefix? For example: > disk = [ ''phy:/dev/data/faitest-client-generic-hvm-disk,ioemu:hda,w'']I just tried that out, and just reused the config file that didn''t work yesterday, but today it just worked, also with the relative path. No idea what was wrong yesterday, in the meantime the machine was turned of for the night, but nothing else changed that I can think of. Maybe some sepcific kernel modules must be loaded, or something else that can make qemu fail with the given error message? Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
"Henning Sprang" <henning_sprang@gmx.de> wrote on 08/14/2006 11:58:18 AM:> Hi, > > On 8/14/06, Steve Dobbelstein <steved@us.ibm.com> wrote: > > [...] > > > It seems qemu is expecting to get a file-based disk. What do I needto> > > do to get hvm use a physical disk? > > > > I''m using LVM volumes for my HVM disks just fine. Did you tryspecifying> > the full name of the device with the "/dev/" prefix? For example: > > disk = [''phy:/dev/data/faitest-client-generic-hvm-disk,ioemu:hda,w'']> > I just tried that out, and just reused the config file that didn''t > work yesterday, but today it just worked, also with the relative path.Glad it''s working for you.> No idea what was wrong yesterday, in the meantime the machine was > turned of for the night, but nothing else changed that I can think of. > > Maybe some sepcific kernel modules must be loaded, or something else > that can make qemu fail with the given error message?Not having seen this problem myself I can only guess what might be going wrong. I doubt it''s a kernel module since you said nothing changed with the setup. I''m guessing that perhaps qemu has a bug in setting up the disk or that the Xen domain creation tools have a bug in generating the appropriate parameters for invoking qemu. But those are just guesses. Steve D. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 8/16/06, Steve Dobbelstein <steved@us.ibm.com> wrote:> [...] > > I just tried that out, and just reused the config file that didn''t > > work yesterday, but today it just worked, also with the relative path. > > Glad it''s working for you.Strange enough, now I am at a point to see that I have again booting problems with hvm, but without any error message(in no log file, nor xm dmesg), and they go away when adding the full path to the disk. But defintely not the qemu error message I had before. I''ve been trying out and testing a lot other things, so I can''t tell what exactly I changed in the meantime.> > Not having seen this problem myself I can only guess what might be going > wrong. I doubt it''s a kernel module since you said nothing changed with > the setup. I''m guessing that perhaps qemu has a bug in setting up the disk > or that the Xen domain creation tools have a bug in generating the > appropriate parameters for invoking qemu. But those are just guesses.I''ll have an eye on it and try to figure out if I get more reproducable results to track what is going on there. Unfortunately I didn''t version control my configs... Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users