search for: xenfv

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave Justification: renders package unusable qemu-dm sends out this: - supported machines are: pc Standard PC (default) isapc ISA-only PC - instead of: - Supported machines are: xenfv Xen Fully-virtualized PC (default) xenpv Xen Para-virtualized PC - this renders any tries to use HVM fail. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-xen-amd64 (SMP w/4 CP...

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

...081 4.7 76.1 4917256 3872708 ? SLl mar16 209:48 /usr/lib/xen-4.1/bin/qemu-dm -d 8 -domain-name sms -videoram 4 -nographic -vcpus 1 -vcpu_avail 0x1 -boot c -acpi -usb -usbdevice host:12d1:1003 -net nic,vlan=1,macaddr=00:16:3E:xx:xx:xx,model=e1000 -net tap,vlan=1,ifname=vif8.0-emu,bridge=br0 -M xenfv Normal domU state: root 8128 4.5 0.0 82052 3988 ? SLl 14:38 0:16 /usr/lib/xen-4.1/bin/qemu-dm -d 9 -domain-name sms -videoram 4 -nographic -vcpus 1 -vcpu_avail 0x1 -boot c -acpi -usb -usbdevice host:12d1:1003 -net nic,vlan=1,macaddr=00:16:3E:xx:xx:xx,model=e1000 -net tap,vlan=1,...

Hi all, I try xen 4.1, but in my domU''s HVM don''t appear vnc port. I used in my domU.cfg the parameter ''vncunused=1''. How to get vnc port specified domU? In another Xen (4.0.2), I get vnc port with ''xm list --long domU''. (vfb (vncunused 1) (vnc 1) (uuid cb20995f-55ae-55ce-143d-dd6a2ecc5969)

...d>cc5b436b-a04b-4fc3-b145-e91df494fd26</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader>/usr/local/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <pae/> <acpi/> <apic/> <clock offset='variable' adjustment='0' basis='localtime'/> <on_poweroff>d...

...39;, 'xen', 0 ], - [ '/domain/devices/input/@bus', 'xen', 1 ], - [ '/domain/devices/interface/script/@path', 'vif-bridge', 0], - [ '/domain/os/loader', 'xen', 0 ], - [ '/domain/os/type/@machine', '(xenpv|xenfv|xenner)', 0 ], - [ '/domain/devices/disk/target/@bus', 'xen', 0 ], - [ '/domain/bootloader', undef, 0], - [ '/domain/bootloader_args', undef, 0] - ); + my ($dom, $default_dom) = @_; + + # The list of target xen-specific nodes is most...

Signed-off-by: Paul Durrant <paul.durrant@citrix.com> --- xen/include/public/hvm/pvdrivers.h | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/xen/include/public/hvm/pvdrivers.h b/xen/include/public/hvm/pvdrivers.h index 4c6b705..77994d2 100644 --- a/xen/include/public/hvm/pvdrivers.h +++ b/xen/include/public/hvm/pvdrivers.h @@ -38,10 +38,12 @@ * indicate

...#39;', ''-usb'', ''-usbdevice'', ''tablet'', ''-net'', ''nic,vlan=1,macaddr=00:50:56:00:00:36,model=rtl8139'', ''-net'', ''tap,vlan=1,bridge=xenbr'', ''-M'', ''xenfv'', ''-loadvm'', ''/var/lib/xen/qemu-save.186''] [2008-05-07 22:40:35 3314] INFO (image:293) device model pid: 27287 [2008-05-07 22:40:35 3314] DEBUG (XendDomainInfo:1008) Storing domain details: {''console/port'': ''3'', '&...

...t;/uuid> >>    <memory unit='GiB'>32</memory> >>    <currentMemory unit='GiB'>32</currentMemory> >>    <vcpu placement='static'>16</vcpu> >>    <os> >>      <type arch='x86_64' machine='xenfv'>hvm</type> >>      <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> >>      <boot dev='hd'/> >>    </os> >>    <features> >>      <acpi/> >>      <apic/> >>      <pae/> &gt...

...un/xen/qmp-libxl-6,server,nowait -mon chardev=libxl-cmd,mode=control -name InitialName -vnc 0.0.0.0:0,password -serial pty -vga cirrus -boot order=cda -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3e:e9:96:a8 -netdev type=tap,id=net0,ifname=vif6.0-emu,script=no,downscript=no -M xenfv -m 3064 -drive file=/root/test.qcow2,if=ide,index=0,media=disk,format=qcow2,cache=writeback root@ubuntu:~# xl rename 6 NewName root@ubuntu:~# xl list Name                                        ID   Mem VCPUs State Time(s) Domain-0                                     0  5049     2     r-----...

...;21'> <name>testVM</name> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> <boot dev='network'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='variable' a...

Hello Community, I successfully installed and run xen (xm list and xm info can output appropriately). However, while I was installing domU image by using virt-install -p at domU OS. I encountered an error information" Host does not support virtualization type ''xen'' ". I built xen from source. Some of my friends have the same issue, but if they use pre-build xen, the

Processing commands for control at bugs.debian.org: > close 509890 Bug #509890 [src:xen] xen-utils-3.2-1: qemu-dm is on amd64 not built for xenfv and xenpv Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 509890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509890 Debian Bug Tracking System Contact owner at bugs.debian.org with problems

...edcd03-54e8-4055-8d1b-37dd34194859</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> <kernel>/usr/lib64/xen/boot/hvmloader</kernel> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/>...

...f7f16c-50e1-4541-b5b1-a91ff675a7c2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>8</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib64/xen/boot/hvmloader</loader> <boot dev='cdrom'/> </os> <features> <acpi/> <apic/> <pae/> <viridian/> </features> <clock offs...

...;, '-boot', 'dc', '-localtime', '-serial', 'pty', '-acpi', '-usbdevice', 'tablet', '- net', 'nic,vlan=1,macaddr=00:16:3e:64:bd:33,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-M', 'xenfv', '-loadvm', '/var/lib/xen/qemu-save.6', '-vncviewer'] That path is not a part of any configuration, but hard-coded at several points under /usr/lib/xen-3.2-1 : lib/python/xen/xend/XendCheckpoint.py:115: if os.path.exists("/ var/lib/xen/qemu-save.%d&quo...

...uid>72f8f7cf-d538-41cd-828a-9945b9157719</uuid> <memory unit='GiB'>32</memory> <currentMemory unit='GiB'>32</currentMemory> <vcpu placement='static'>16</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='localtime'/>...

...gt;feef6cac-8148-4040-a7cb-ad1f82d8d68a</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>4</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm</type> <loader type='rom'>/usr/lib64/xen/boot/hvmloader</loader> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_powe...

...gt;testVM</name> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <vcpu placement='static'>1</vcpu> > <os> > <type arch='x86_64' machine='xenfv'>hvm</type> > <loader type='rom'>/usr/lib/xen/boot/hvmloader</loader> > <boot dev='network'/> > </os> > <features> > <acpi/> > <apic/> > <pae/> > </features>...