similar to: Can't get PCI card visible in guest

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were

On 05/05/2017 12:57, Gianluca Cecchi wrote: grub-install /dev/vda2 didn't work ? > On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > >> On 5/5/2017 1:42 ??, Nikolaos Milas wrote: >> >> Hmm, it seems that the boot flag should be removed from /dev/vda2 >>> partition? >>> >> Actually, I tried this and left the boot

In XM toolchain, we use to put pci = [ ''0000:07:11.6=0@1a'' ] but looks like in XL toolchain there is no way to specify function in the guest. Kindly let me know. XM - pci = [ ''0000:07:11.6=0@1a'' ] XL - pci = [ ''0000:07:11.6@1a'' ] In the guest VM we see that PCI device is getting 0 function in both the cases however, it may not work the

Hello, This is my first post in this list. I''m running Debian Squeeze as Dom0 on a bi-xeon 64 bits : root@sd-29499:/etc/xen# uname -a Linux sd-29499 2.6.32-5-xen-amd64 #1 SMP Tue Mar 8 00:01:30 UTC 2011 x86_64 GNU/Linux I''m trying to install a Squeeze DomU but there is no network card, even during install wich doesn''t show any network card with lspci (but when I

On Thu, Jun 6, 2013 at 3:48 PM, upen <upendra.gandhi at gmail.com> wrote: > > > > On Thu, Jun 6, 2013 at 1:01 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> >> >> This is sounding like dropped/intercepted packets. Could we get some >> >>

Hello Am Friday 11 December 2015, 10:13:00 schrieb Gordon Messmer: > On 12/11/2015 06:04 AM, G?nther J. Niederwimmer wrote: > > I have 4 NIC on all my KVM Servers but the most time on a start (restart) > > I > > lost one NIC? It is not always the same, but this two are virtio NICs. > > > > with ifup eth0(1) the system say,I have no configured eth0 or eth1 file ?

hi xen 4.0.1 w/2.6.32.41 Last week dom0 experienced an hard crash and box need to be restarted manually (despite kernel.panic=20). Serial console was not setup, only netconsole. No relevant entries through netconsole, but analyzing logs I see some crashes twenty minutes before fatal hang. Dec 2 01:29:39 xenhost-rack1 kernel: [4437064.011963] Call Trace: Dec 2 01:29:39 xenhost-rack1 kernel:

On Thu, Jun 6, 2013 at 11:58 AM, upen <upendra.gandhi at gmail.com> wrote: >> This is sounding like dropped/intercepted packets. Could we get some >> details on the client (make/model of computer/motherboard, same for >> NIC, PXE OROM details)? Is it connected to the same physical switch >> as the DHCP/TFTP server? Any chance that the physical switch that the

Package: xcp-squeezed Version: 1.3.2-11 Followup-For: Bug #682202 ?I found race condtion between xcp-sqeezed and /etc/init.d/xen scripts. If sleep 10 added to xcp-sqeezed host (xcp-sqeezed and xapi) initialize normally, and if not with some probability sqeezed/xapi failed to start with message: Oct 9 16:45:57 xenhost-1 xapi: [ warn|xenhost-1|0 thread_zero|server_init D:1691a70e8b4a|startup]

On 07/13/2015 03:25 PM, Ruzsinszky Attila wrote: > - - cd ControlSet001 >> - - cd Control >> - - cd CriticalDeviceDatabase >> - - Check you have the following keys: primary_ide_channel, >> secondary_ide_channel, pci#ven_8086&dev_7010, pci#ven_8086&dev_7111 >> keys. Some will be missing (otherwise, you'd boot ;-)). >> > Here is my keys: > ...

Kip, Does the problem with Xen 3.1 in HVM/Intel manifest as those BTX halted errors (e.g. http://lists.xensource.com/archives/html/xen-users/2006-10/msg00014.html) ? If so, do you happen to know whether this problem has been solved in Xen 3.2 or 3.2.1? This message of yours was written this March, so I'm assuming that 3.2.1 will contain this fix? Can anybody confirm this? I'm having

Just thought I'd pass along that I have successfully installed FreeBSD 7.0 into a Xen 3.1 HVM. ?This one went as smooth as I expected, considering my experience with 6.3. ?Haven't done any benchmarking or stress testing or port installs or anything. ?But so far it's working nicely. Here's all the info. ?If you'd like to see anything else, let me know. Host hardware: ?

Hi, I am running Xen 3.3.1 built from Source with Debian Lenny as the dom0. Everything works fine so far except pyGRUB. So, what I did was install CentOS (latest version ... 5.3 or something) using qemu to a LVM logical volume and from within CentOS I installed the Xen Kernel. Now pyGRUB shows me 3 grub entries: 1) CentOS (2.6.18-128.1.10.el5xen) <= xen hypervisor 2) CentOS

Hi all! I have installed xen on fc6 with kernel 2.6.18-1.2798.fc6xen with rpm package; i have create 3 guest os (fully virtualization) with virt-manager tool, installed on separated partition: 1 fc6 guest, 1 centos 4.4, 1 windows xp pro; all work pretty fine until this point, i have linked the configuration file of the guests machines to /etc/xen/auto for autostart/autostop, but when

I am working on S5000VSA Intel Server Board with the following cpu spec. XEN-PEER-RHEL5 $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping : 7 cpu MHz : 2327.512 cache size : 4096 KB physical id : 0 siblings : 1 core id : 0

Hi, list.I''m new to xen. I follow this article http://www.virtuatopia.com/index.php/Installing_and_Running_Windows_7_as_a_Xen_HVM_domainU_Guest and install my first windows 7 xen guest. I just change a little to need my fits. And This is my xenwin7.cfg kernel ="/usr/lib/xen-4.1/boot/hvmloader" builder=''hvm'' memory = 1024 # Should be at least 2KB per MB of

Hi all heve been trying (in vain) to get a Solaris b44 DomU (dowloaded from Sun) running on a Linux Xenhost I followed exactly how, and it looked ok when it starts booting... But it never boots . adapted the configfile to boot with -v (that I can see at least something) and this is what I get ===SNIP=== root@Xen-VT02:/export/xc/xvm/solaris-b44# xm create solaris-b44-64.py -c Using config

Hey, I have a nighly build/test system that boots various machines with upstream Linux and randomly selects Xen 4.1, Xen 4.2, Xen 4.3 and unstable. After a bit of digging I found out that Xen 4.2 ''xl'' (but not ''xm'') has some badness in it. When "migrating" (''xl'' save followed by ''xl'' restore'') the PVHVM

Hi, One of the I noticed during migration from XM toolchain to XL in PCI Pass-through was that we used to specify target bdf in HVM guest as pci = [ ''0000:07:11.6=0@1a'' ] However with XL, it now seems like this is the correct syntax: pci = [ ''0000:07:11.6@1a'' ] Is that correct? I''ve verified that it works but what about zero in

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512