Hi, all,
I'm not seeing disks under CentOS 6 when trying to install. I'm using:
xen-4.0.2-1.fc14.x86_64 2.6.32.39-175.xendom0.fc13.x86_64
installing using:
virt-install --debug -n sully --mac=02:00:0A:01:01:10 -f /var/lib/xen/images/sully -s 12 -r 2048 --vcpus=2 --nographics -p --os-type=linux --os-variant=rhel6 --location http://librescu.bfccomputing.com/cobbler/ks_mirror/centos6-x86_64/
It sounded like:
https://bugzilla.redhat.com/show_bug.cgi?id=678374
so I tried dropping the --nonsparse option, but I'm using a newer version of python-virtinstall:
python-virtinst-0.500.6-1.fc14.noarch
than should be required, and I'm seeing this with and with the option anyway.
I do see the disk image is created, and attached to the DomU. e.g.:
[2011-07-26 01:01:47 18534] DEBUG (DevController:97) DevController: writing {'domain': 'sully', 'frontend': '/local/domain/18/device/vbd/51712', 'uuid': '3380cea8-a322-292d-cc5d-8bb084306976', 'bootable': '1', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/sully', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'tap'} to /local/domain/0/backend/tap/18/51712.
and I can see the disk image if I dump configuration from virsh.
I do see this in the DomU kernel messages:
XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0
but I see reports online that say not to worry about those, initrd will load the modules.
The initrd does have:
./kernel/drivers/xen ./kernel/drivers/xen/xenfs ./kernel/drivers/net/xen-netfront.ko.gz ./kernel/drivers/block/xen-blkfront.ko.gz
on it.
I tried adding:
xen_emul_unplug=never
to the kernel parameters per a previous thread here, but that didn't seem to change anything.
It seems like others are having success with CentOS 6 in general:
http://grantmcwilliams.com/tech/virtualization/xen-howtos/538-centos-6-virtu...
so I suspect it's got something to do with Xen 4.0.2, but I'm not sure where to look right now.
Any suggestions?
-Bill
On Tue, Jul 26, 2011 at 02:07:30AM -0400, Bill McGonigle wrote:
Hi, all,
I'm not seeing disks under CentOS 6 when trying to install. I'm using:
xen-4.0.2-1.fc14.x86_64 2.6.32.39-175.xendom0.fc13.x86_64
installing using:
virt-install --debug -n sully --mac=02:00:0A:01:01:10 -f /var/lib/xen/images/sully -s 12 -r 2048 --vcpus=2 --nographics -p --os-type=linux --os-variant=rhel6 --location http://librescu.bfccomputing.com/cobbler/ks_mirror/centos6-x86_64/
Did you try using a phy: backend? ie. lvm volume or a block device?
It sounded like:
https://bugzilla.redhat.com/show_bug.cgi?id=678374
so I tried dropping the --nonsparse option, but I'm using a newer version of python-virtinstall:
python-virtinst-0.500.6-1.fc14.noarch
than should be required, and I'm seeing this with and with the option anyway.
I do see the disk image is created, and attached to the DomU. e.g.:
[2011-07-26 01:01:47 18534] DEBUG (DevController:97) DevController: writing {'domain': 'sully', 'frontend': '/local/domain/18/device/vbd/51712', 'uuid': '3380cea8-a322-292d-cc5d-8bb084306976', 'bootable': '1', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/sully', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'tap'} to /local/domain/0/backend/tap/18/51712.
and I can see the disk image if I dump configuration from virsh.
I do see this in the DomU kernel messages:
XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0
but I see reports online that say not to worry about those, initrd will load the modules.
Can you post the full domU kernel messages? probably with "console=hvc0 earlyprintk=xen"
The initrd does have:
./kernel/drivers/xen ./kernel/drivers/xen/xenfs ./kernel/drivers/net/xen-netfront.ko.gz ./kernel/drivers/block/xen-blkfront.ko.gz
on it.
I tried adding:
xen_emul_unplug=never
xen_emul_unplug is only needed for HVM guests, not for PV.
to the kernel parameters per a previous thread here, but that didn't seem to change anything.
It seems like others are having success with CentOS 6 in general:
http://grantmcwilliams.com/tech/virtualization/xen-howtos/538-centos-6-virtu...
so I suspect it's got something to do with Xen 4.0.2, but I'm not sure where to look right now.
Any suggestions?
Did you see?: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
-- Pasi
-Bill
-- Bill McGonigle, Owner BFC Computing, LLC http://bfccomputing.com/ Telephone: +1.855.SW.LIBRE Email, IM, VOIP: bill@bfccomputing.com VCard: http://bfccomputing.com/vcard/bill.vcf Social networks: bill_mcgonigle/bill.mcgonigle -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Did you see?: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
It's not what he need. Mirror is probably broken.
What is official centos 6 installation URL ? I never cared using SL-6-Install.DVD , mounted loop on /var/www/rhel CentOS 6 Network installer behaves strange vs SL-6 Network Installer ISO.
Boris. P.S. Pickup SL 6 up. It's the same
--- On Tue, 7/26/11, Pasi Kärkkäinen pasik@iki.fi wrote:
From: Pasi Kärkkäinen pasik@iki.fi Subject: Re: [fedora-virt] [Fedora-xen] CentOS 6 install via virt-install - "No usable disks have been found." To: "Bill McGonigle" bill@bfccomputing.com Cc: xen@lists.fedoraproject.org, virt@lists.fedoraproject.org Date: Tuesday, July 26, 2011, 7:05 AM
On Tue, Jul 26, 2011 at 02:07:30AM -0400, Bill McGonigle wrote:
Hi, all,
I'm not seeing disks under CentOS 6 when trying to install. I'm using:
xen-4.0.2-1.fc14.x86_64 2.6.32.39-175.xendom0.fc13.x86_64
installing using:
virt-install --debug -n sully --mac=02:00:0A:01:01:10 -f /var/lib/xen/images/sully -s 12 -r 2048 --vcpus=2 --nographics -p --os-type=linux --os-variant=rhel6 --location http://librescu.bfccomputing.com/cobbler/ks_mirror/centos6-x86_64/
Did you try using a phy: backend? ie. lvm volume or a block device?
It sounded like:
https://bugzilla.redhat.com/show_bug.cgi?id=678374
so I tried dropping the --nonsparse option, but I'm using a newer version of python-virtinstall:
python-virtinst-0.500.6-1.fc14.noarch
than should be required, and I'm seeing this with and with the option anyway.
I do see the disk image is created, and attached to the DomU. e.g.:
[2011-07-26 01:01:47 18534] DEBUG (DevController:97) DevController: writing {'domain': 'sully', 'frontend': '/local/domain/18/device/vbd/51712', 'uuid': '3380cea8-a322-292d-cc5d-8bb084306976', 'bootable': '1', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/sully', 'mode': 'w', 'online': '1', 'frontend-id': '18', 'type': 'tap'} to /local/domain/0/backend/tap/18/51712.
and I can see the disk image if I dump configuration from virsh.
I do see this in the DomU kernel messages:
XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 XENBUS: Device with no driver: device/console/0
but I see reports online that say not to worry about those, initrd will load the modules.
Can you post the full domU kernel messages? probably with "console=hvc0 earlyprintk=xen"
The initrd does have:
./kernel/drivers/xen ./kernel/drivers/xen/xenfs ./kernel/drivers/net/xen-netfront.ko.gz ./kernel/drivers/block/xen-blkfront.ko.gz
on it.
I tried adding:
xen_emul_unplug=never
xen_emul_unplug is only needed for HVM guests, not for PV.
to the kernel parameters per a previous thread here, but that didn't seem to change anything.
It seems like others are having success with CentOS 6 in general:
http://grantmcwilliams.com/tech/virtualization/xen-howtos/538-centos-6-virtu...
so I suspect it's got something to do with Xen 4.0.2, but I'm not sure where to look right now.
Any suggestions?
Did you see?: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
-- Pasi
-Bill
-- Bill McGonigle, Owner BFC Computing, LLC http://bfccomputing.com/ Telephone: +1.855.SW.LIBRE Email, IM, VOIP: bill@bfccomputing.com VCard: http://bfccomputing.com/vcard/bill.vcf Social networks: bill_mcgonigle/bill.mcgonigle -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
_______________________________________________ virt mailing list virt@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/virt
On 07/26/2011 07:05 AM, Pasi Kärkkäinen wrote:
Did you try using a phy: backend? ie. lvm volume or a block device?
I just got back to trying this today. Switching to a phy: backend (a zfs zvol in this case) absolutely worked. I have to admit to trying it on a 2.6.40 kernel vs. 2.6.32 last time, so I'm changing multiple variables (I know, bad analysis!) but I don't have any reason to go back to 2.6.32 either.
Everything is noticeably peppier too (not just disk - VNC, etc.). Very nice.
-Bill
xen@lists.stg.fedoraproject.org