Displaying 20 results from an estimated 4000 matches similar to: "vhd format support failed on suse11 x86_64 sp2"
2011 Jul 28
2
problems with xen and hvm
Dear xen-users.
First of all, I''m not a linux-guru and a beginner with xen and
completly new in this mailinglist.
I''ve installed Xen on debian 6 and I was successful creating two
machines: one for tests and "fogserver" (to test speed of writing
computer images), both para-virtualisations.
2011 Jan 30
0
Stub domains broken in Xen 4.0?
When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes
almost immediately if I specify an emulated NIC (''vif='') in the guest
configuration file. If I don''t specify a vif, it works fine. If I use the
same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is
there some reason QEMU emulated networking doesn''t work with stub domains
2011 Jan 23
1
DRBD VBD script not working in squeeze ?
Hi,
since I upgraded from Lenny, DRBD VBD scripts not works at all.
This config works :
disk = [ 'phy:/dev/drbd/by-res/ads-disk,xvda,w' ]
But his one doesn't work at all :
disk = [ 'drbd:ads-disk,xvda,w' ]
I obtain this error :
# xm create ads.cfg
Using config file "/etc/xen/ads.cfg".
Error: Device 51712 (vbd) could not be connected. Hotplug scripts
2011 Jan 17
0
Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0
I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built
and installed the Xen binaries from source. The systems boot successfully
however I am having issues bring up DomUs. Here is config:
name = ''xyz''
memory = 256
vcpus = 1
pae = 1
vnc = 1
vncunused = 1
disk = [ ''phy:/dev/vg1/xyz,hda,w'' ]
vif = [
2010 Jun 06
3
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
Hi!
Please help me.
# xm create win7.hvm
Using config file "./win7.hvm".
Error: Device 768 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/9/768 state: 1
grep -v ^# /etc/xen/win7.hvm | grep -vx ''''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 2048
name = "win7"
vif = [
2010 Jul 22
1
HVM domain can not boot up with Qcow incremental image
Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM
2012 Jul 13
1
virt-install says ERROR POST operation failed: xend_post: error from xen daemon: <Fault 3: 'ubuntu-first-test'>
I was trying to install a guest OS with the following command.
$ virt-install -r 1024 --accelerate -n ubuntu-first-test -f
/var/lib/libvirt/images/guest.img --cdrom
/root/ubuntu-12.04-desktop-i386.iso --hvm
and it says the following.
Starting install...
ERROR POST operation failed: xend_post: error from xen daemon: <Fault 3:
''ubuntu-first-test''>
Domain installation
2011 Oct 29
0
Bug#644100: Boot loader didn't return any data! if reboot domU with disk DRBD
Package: xen-utils-4.0
Version: 4.0.1-2
If you reboot with the DomU disk DRBD domain destroy.
pygrub error when trying to run a image on DRBD device
My config DomU
------------------------------------------------------
bootloader = '/usr/lib/xen-default/bin/pygrub'
vcpus = '1'
memory = '256'
cpus="8-15"
root = '/dev/xvda2 ro'
#disk
2011 Aug 04
3
[Q] VmError: Disk isn''t accessible with tap2:tapdisk:vhd
I''m newbie Xen-4.1.1
I''m trying to boot DomU with the following configuration.
Sometime DomU boot, but sometime boot failed
I''m not sure what is the problem.
I can attach that image with tap-ctl on Dom0.
Does anybody advice me about this problem??
Sincerely
* Environment
OS : Scientific Linux 6.1 x86_64
Kernel : 2.6.32.43
2011 Jan 18
4
Error bringing up VMs with Xen 4.0.1 + 2.6.18-194.32.1.el5xen CentOS Dom0
I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built
and installed the Xen binaries from source. The systems boot successfully
however I am having issues bring up DomUs. Here is config:
name = ''xyz''
memory = 256
vcpus = 1
pae = 1
vnc = 1
vncunused = 1
disk = [ ''phy:/dev/vg1/xyz,hda,w'' ]
vif = [
2012 Mar 22
8
Windows 7 as guest on a physikal disk
Hallo,
I have an installed Windows 7 on one partition
and running Debain Squeeze on the other. Both are 64 bit.
I want to use Xen to run Windows as virtual guest from
a physical disk. Once I get this working the Window will
never be booted directly.
When I try to create the virtual machine by
"xm create -c win.xen"
it hangs.
The versions I use
Xen 4.0.1-4
Kernel 2.6.32-5-xen-amd64
2013 Jul 28
4
Fedora 19 installation with virt-install
Hello,
I want to install a DomU with Fedora 19 in a Debian Host Dom0 with the
following versions...
ii libc6-xen:i386 2.13-38
i386 Embedded GNU C Library: Shared libraries [Xen version]
ii libxen-4.1 4.1.4-3+deb7u1
i386 Public libs for Xen
ii libxenstore3.0 4.1.4-3+deb7u1
i386
2012 Aug 24
1
Problems with create VM
Hi,
I installed the xen in server with CentOS 6, but not create vm.
[root@localhost oracleteste]# xm create oracleteste.cfg
Using config file "./oracleteste.cfg".
Started domain oracleteste (id=9)
[root@localhost oracleteste]# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1024 1 r-----
2011 Jul 09
10
Starting basic HVM -- where am I going wrong?
I''ve been using Xen strictly for PV for a while now, but I recently upgraded to hardware capable of HVM domUs. I''m trying to get a really basic HVM instance going so I can get my hands around making them work, in anticipation of using one to run a BSD to act as a firewall for other domUs on the machine. (I like PF.) Also, I might need run windows at some point, I suppose.
2011 Oct 28
0
"reset requested in cpu_handle_ioreq" causes the wirtual machine crashed when using "xm create xp.hvm"
the contexts are as follows, looking forward to your reply, thanks
[1]enviromention : xen3.4.2+CentOS-5.5
[2]config file: xp.hvm, as follows
_s_name = 'xp-101'
_s_vnc_display = 5310
_s_vm_id = 101
_s_vm_mac = '00:16:3e:eb:ca:65'
_s_memory = 512
_s_allow_destroy = False
_s_use_vnc = True
# -*- mode: python; -*-
2009 Nov 20
5
XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi All,
I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs
for lennovo T400. I have installed all prerequisite component for running
xen and booted it.
while I am trying to create DomU I am getting error. I tried doing googling
but none of suggested solution is working for me. For more details please
see below, I have highlighted few details in bold color just for
2009 Nov 20
5
XM create issue: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi All,
I am new to xen community. I am trying to setup Xen3.4.2 +FC11 Dom0 environs
for lennovo T400. I have installed all prerequisite component for running
xen and booted it.
while I am trying to create DomU I am getting error. I tried doing googling
but none of suggested solution is working for me. For more details please
see below, I have highlighted few details in bold color just for
2008 Aug 05
2
Centos 5.2 using LVM -> DRBD 0.82 -> Xen Problems
Hi Everyone,
I''m trying to get Xen to use a native DRBD device but it seems it will
not create the virtual machine. It does not seem to like the DRBD device
type, any ideas on what might be wrong?
I''m pretty sure my xen config file is OK and the DRBD device looks fine
too.
Full details below.
xm create centostest
Using config file "./centostest".
2008 Aug 09
4
Upgrade 3.0.3 to 3.2.1
Hi,
i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit.
The old system:
Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel.
The new systen:
Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from
Debian 4.0 amd64.
My domUs have a self compiled kernel out of the dom0 kernel of the old system
(mainly the dom0 kernel but
2011 Aug 03
1
Bug#636552: xen-hypervisor-4.1-i386: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Package: xen-hypervisor-4.1-i386
Version: 4.1.1-1
Severity: important
Tags: wheezy
I cannot boot a domU with networking after installing the package.
root at topsail:~# xm create /etc/xen/udevtest.cfg -c
root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts
not working.
[2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2.
[2011-08-03