WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] hardware virtualization AMD...

To: Steve Dobbelstein <steved@xxxxxxxxxx>
Subject: Re: [Xen-users] hardware virtualization AMD...
From: Yasir Assam <list1@xxxxxxxxxxxxxxx>
Date: Wed, 19 Jul 2006 11:49:09 +1000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 18 Jul 2006 18:49:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OF32452897.AD64179C-ON052571AF.00500044-052571AF.005344AE@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <OF32452897.AD64179C-ON052571AF.00500044-052571AF.005344AE@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Debian Thunderbird 1.0.7 (X11/20051017)
Steve,

You're right - I didn't try this. All I did was to create an empty unformatted partition using GParted running on dom0. I didn't try using an LVM volume  - just a normal partition.

Windows did install on it but when I rebooted, the 2nd stage of the install (from drive c, rather than drive d) was very slow. It did boot up off drive c, but it took a very long time to install. After about 2 hours I gave up and reinstalled on a file-backed VBD and it was quick.

Do you think the slow speed was due to not copying a boot loader and partition table? Doesn't the Windows install CD create these itself?

Thanks,
Yasir
Yasir Assam <list1@xxxxxxxxxxxxxxx> wrote on 07/17/2006 08:15:58 PM:

  
I also had problems using a physical partition as a VBD for the HVM
guest. I had to use a file-backed VBD which works fine.
    

I have not had any problem using a block device as a VBD for an HVM guest,
although I have seen others on the list report similar problems.  Granted,
my block devices are LVM volumes instead of partitions or disks (disk =
['phy:/dev/virt-blkdev-backend/hvm1,ioemu:hda,w']), but I don't see how
that would make a difference, since a block device is a block device.

My apologies if this is obvious an you tried it already, but my initial
thought is to make sure that the block device you use looks like a bootable
disk with a boot loader, partition tables, and a partition with a file
system.  PV guests only require a block device or file image that contains
a file system.  HVM guests require a block device or file image that looks
like a bootable disk.  It's easiest to just use a disk on which you
installed an OS, for example, disk = ['phy:/dev/sdb,ioemu:hda,w']  If you
are going to use a partition, the partition must contain a boot loader,
partition tables, etc.

In our test setup, the scripts create a bootable LVM volume by running
fdisk to create a partition on the volume, installing grub on the volume,
and then copying a root file system to the partition on the volume.

Steve D.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users



  

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>