Displaying 9 results from an estimated 9 matches for "tap10.0".
Did you mean:
tap1.0
2013 Mar 07
0
Bug#702428: log output
errors from /var/log/xcp-xapi.log:
652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi]
creating device emulator
652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops]
Device.Dm.start domid=10
661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops]
qemu-dm: should be running in the background (stdout redirected to syslog)
661Z|debug||1227 UNIX
2013 Mar 17
2
Bug#702428: HVM networking tap/vif bug (Debian bug 702428)
Hi,
I've been testing the Debian packages ahead of the Debian 7 release
(which is very imminent)
I believe this is a serious bug[1] in the package, as it appears that
HVM networking is broken, or at the very least, requires some
undocumented configuration step
Specifically:
- I can start the HVM domU without any vif
- if I attach a vif, the domU will not start
Looking at
2013 Mar 15
1
Bug#702428: raising to serious
My impression of this bug is that HVM networking is not possible with
XCP, or at least it is not possible without some undocumented
configuration setting or missing dependency package
If there is a workaround from upstream, I would propose lowering the
severity to important again. I am happy to test any proposed work
around and provide quick feedback.
The log output in my previous post suggests
2011 Jun 17
1
Failed to setup NAT network
I''m using Xen 4.1 and here''s what I did:
1.comment network-script and vif-script about bridge in
/etc/xen/xend-config.sxp, uncomment the lines about nat
2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11,
ip=10.0.0.1'' ]
3.set /etc/network/interfaces in domU, add lines as follows:
auto eth0
iface eth0 inet static
address 10.0.0.1
gateway
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 = [
2011 Jun 17
0
Failed to setup NAT
I''m using Xen 4.1 and here''s what I did:
1.comment network-script and vif-script about bridge in
/etc/xen/xend-config.sxp, uncomment the lines about nat
2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11,
ip=10.0.0.1'' ]
3.set /etc/network/interfaces in domU, add lines as follows:
auto eth0
iface eth0 inet static
address 10.0.0.1
gateway
2011 Mar 09
12
Can''t boot HVM Linux guests on Debian Squeeze Dom0
I just downloaded Debian Squeeze and installed Xen from packages, following
the instructions here: http://wiki.debian.org/Xen
I am able to get PV guests up and running easily, but HVM guests will not
even boot.
The HVM I am currently trying to run is Debian sarge, which I installed into
a disk image and configured using qemu.
I am running on an HP Proliant ML150G6, which has Intel-VT hardware
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.
2012 Sep 30
21
Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi,
I''m trying to get Windows Server 2008 R2 installation booting on Xen 4.0.4.
Using the following config:
kernel = "/usr/lib/xen/boot/hvmloader"
builder = "hvm"
shadow_memory = "8"
memory = "4096"
name = "ts"
vcpus = "8"
cpus = ["0", "1", "2", "3", "4", "5",