|
Hi Sam, FC5 release has some
known issue to play with VMX in x86_64, e.g. destroying IA32 VMX will hang Xen0
and creating x86_64 VMX will reboot Xen0. This bug will be fixed in the FC5
update. I am not sure if it is there now. Seemed not? A way is worthy to have a
try, if you don’t want to wait for FC5 update to test. Get the Xen source RPM
package from FC5 and only re-make xen (go into xen folder to do make, you don’t
need to remake xen0 and xenU). After making finishes, copy xen.gz to /boot and
replace the old hypervisor kernel. Reboot~. I didn’t find any error
in your config file. But the error info “it
can't find hard drive“ is very
strange. Did you try the FC5 or FC4 ISO to install? Have a look at
/var/log/xend.log to see if the disk option (hda) has been sent to qemu, such
like: /usr/lib64/xen/bin/qemu-dm',
'-d', '1’, '-m', '256', '-boot', 'c', '-serial', 'pty', '-vcpus', '1',
'-domain-name', 'ExampleHVMDomain', '-hda', '/xxx/xxx.img', '-hdb', '/xxx/yyy.img',
'-macaddr', '00:16:3e:00:00:11', '-bridge', 'xenbr0', '-nics', '1' BTW, you can find a lot
of OS installed disk image in http://free.oszoo.org/
. Best Regards, Yongkang (Kangkang) 永康 From:
fedora-xen-bounces@xxxxxxxxxx [mailto:fedora-xen-bounces@xxxxxxxxxx] On Behalf Of sxu1902 Hi, I am
testing Xen3 on FC5. My FC5 is x86_64. My box is using Pentium D 920
on Asus P5LD2-VM motherboard with 2G RAM. After
installation, "xm list" shows domain0 running ok. I
use: dd
if=/dev/zero of=/hdd_mnt/sda5/g_img/gl112/gl112.img bs=1M count=1 seek=10240 to
create iamge file. And
the paremeter file look like this: #
Automatically generated xen config file I tried
different linux distributions as VMX guest. It appears to me the guest machine
always reboot itself when loading the linux from CD images or CDs. Sometimes it
even freezes domain0. Occasionally it boots into the installation CD
(after reboot itself once) and tells me it can't find hard drive, so it can't
proceed with the installation... Anybody
tested VMX? Any similar problems? Any suggestions? Sam Xu
|
